Preferred setup for development with Umbraco

We are starting the development of a new website with Umbraco and have some difficulties with the optimal setup for several developers.

Now we have a complete installation of umbraco in the code directory, indicating IIS, as well as a local database for each developer. We plan to use the Courier package to modify / modify content and Git for the source code.

This setting allows you to debug from Visual Studio (using F5) rather than join w3p, which is annoying. A separate db is the part that I don’t really like, I would prefer the general one, but with the Umbraco caching model (in the xml file) this is also not optimal - changes in data types, etc. Not reflected in other developer environments. This means, however, that sharing changes between developers is a two-step process - Git + Courier.

I would suggest that people have already come up with some recommendations on setting up umbraco for team development - it would be nice to hear about them.

Thanks!

+4
source share
1 answer

We use a central source code management system for code and share the same database with all developers. This works pretty well, but after changing or updating the source control repository, the only thing you need to keep in mind is that you need to update the cache (right-click the root of the content node in Umbraco and “republish the whole site”).

With this setting, we all share the code and the database at the development stage. The courier can then be used to transfer umbraco contents back and forth to a test and production environment.

+4
source

Source: https://habr.com/ru/post/1379703/


All Articles