Still in decision-making if for a new project whether TYPO3 FLOW or TYPO3 NEOS.
What's if I realize as a FLOW project.
Is it possible and when how to migrate to Neos afterwards?
Thanks in advance!
TYPO3 Neos is a TYPO3 Flow project. That means that TYPO3 Neos contains of several TYPO3 Flow packages that provide the TYPO3 Neos functionality.
That means you can safely start with TYPO3 Flow and add the TYPO3 Neospackages any time.
Please take a look at the composer file to understand this better: https://git.typo3.org/Neos/Distributions/Base.git/blob/HEAD:/composer.json
Therefore, adding the packages typo3/neos and typo3/neos-nodetypes should do the trick.
Tell your boss that TYPO3 Flow is the right decision ;)
Actually it is the concept of TYPO3 Neos that it sits on top of TYPO3 Flow such that it can be added any time a CMS functionality is needed.
Enjoy the flow ;-)
Related
I want to develop a Umbraco package. Where do I have to start and Where do I have to end?
I have knowledge on Asp.net MVC 4 and using the Umbraco cms as a user
A package is quite a broad definition. A package can for example be an extension to Umbracos back office, but can also simply consist of nodes.
There is plenty of guides and documentation on Umbracos website.
Read more here, for example https://our.umbraco.com/documentation/extending/
This should definitely be where you have to start. Where you have to end is hard to say, because it depends on the package you want to create.
I have a project I was brought onto a few years ago and the original developer is no longer available. We have an Umbraco 6 based website. The solution has two projects, a Web Site and a class library call Umbraco.Extensions. I believe I read some conventional wisdom pertaining to Umbraco at some point where it is recommended to split it up like this but I am looking for more information about this particular style of setup and how it is supposed to work. For example right now I am dealing with a missing assembly issue, and i fixed it by copying a dll from the bin of Extensions to the bin of the Web Site. How is this handled regularly?
it's generally a good idea to keep the projects separated. You should have some kind of automation (maybe a post-build action) to copy the dll of the class library to the bin of the umbraco project. Or maybe rebuild the umbraco project with the correct references, but I dont usually do that.
I'm in the research/planning phase of a project (.Net c#, mvc or silverlight). It's a web project that offers certain services bundled into packages. The client can sign up for one of the different packages.
I'm looking for any suggestions on which architecture/framework to use for this kind of project. I want the ability to load or unload modules depending on the package. I also want to be able to enable and disable features within the packages themselves.
The modules have to be highly portable and plug-able into different clients. I know there are MEF and Prism but I haven't really worked with both. I also read about MVC and Areas. I would rather design everything from scratch and not depend on a third party if the task is simple enough. I just don't know where or how to start.
I appreciate the suggestions.
MG
You can forget about unloading. You have to use seperate appdomsins to be able to unload modules. And that's nothing that I would ever try with a ASP.NET website.
You have to get used to the thought that all modules are loaded at all times. You can use role based security to control if a user can use a module or not (one or more roles per plugin).
As for loading things dynamically: I've written an article about how you can create a plugin system using my Griffin.MvcContrib: http://www.codeproject.com/Articles/386674/ASP-NET-MVC-3-plug-in-architecture-using-Griffin-M
Upgrading MVC apps done with VS 2010 has been the biggest issue for me. I have an application that I use to run various websites and I maintain and develop this application separetely then upgrade the sites based on it. A lot of things might change during development of a new version - new Views, new Controllers, stuff added into JS files, updated stylesheets etc.
I've searched around the web but nothing useful came up besides this Haack's article but no source code is available.
I also tried making a Nuget package for the entire MVC app and while this works, it doesn't package up the resource files (an issue within Nuget itself) and my apps rely on those so until this is fixed I cannot use this method.
I checked how others do it and this pretty much summarizes Umbraco's way and it's the same painful way of a dozen of steps like I do it now.
Do you have any good advice on it?
You don't specify the target OS, but I create native packages, i.e. .deb for Ubuntu servers.
However this still means you need to specify all files, manage configuration, upgrade database schemes. But if you test this on a CI server it becomes more reliable, and you can do it iteratively. This is all part of good deployment practice. I can recommend the Continuous Delivery book.
I'm about to begin building a website using the ASP.NET MVC framework and I'm trying to find a good solution to 1)Source Control Management and 2)Deployment. For the SCM, I'm probably going to use SourceGear since it integrates into Visual Studio nicely, but for deployment, I don't even know where to start. Up until know, most websites that I've built were very static and every time I had to update the site, I would use an FTP program and just drag and drop the files to the server. But now that I'm going to be building a much more dynamic web application, this approach feels dangerous (which, oddly enough, is also my middle name).
Does there exist some kind of idiots guide or tutorial that explains a good way to deploy an update to your website?
Thanks so much in advance for all your help!
Source Control
For source control, I like to use SubVersion at home. I would recommend using VisualSVN Server to install the server - it's free and ridiculously easy to use.
On the client side of things, I use TortoiseSVN (for shell integration) and VisualSVN (for Visual Studio integration). The small ammount of money for VisualSVN is well worth it, but there is a free open source equivilent AnkhSVN.
That's just what I use and there are many alternatives out there.
Deployment
I would definitely recommend using Microsoft Web Deploy.
Scott Gu just blogged today about it - Automating Deploy with Microsoft Web Deploy. There there is also Scott Hanselman's guide - Web Deployment Made Awesome: If You're Using XCopy, You're Doing It Wrong.
I recently came across a couple of posts by Jon Torresdal using Team Foundation Server (SCM), TeamCity (CI), and Web Deploy to implement a 'no-click' web deployment. They make for very interesting reading but they're definitely not what you'd consider idiots guide material.
No-Click Web Deployment – Part 1
No-Click Web Deployment – Part 2 – Web Deploy (a.k.a. msdeploy)
HTHs,
Charles