I have a wish for finding a good solution on how to have multiple developers working on one umbraco project.
Each developer should have an instance of the umbraco site on their machine which is connected to a shared database.
My current challenge is that when one of the developers install a package from the Umbraco Repo. should all the other developers install the same package on their instance with the shared database in mind or how do you and your team manage this situation?
If you are sharing the same database then you will need to make sure that each developer has the same packages etc. The database will store the information about a package, but your developers individual projects won't have the files and folders that the database will refer to, which may cause errors.
By ensuring everyone has the same packages you won't cause problems further down the line if one of your developers creates something that conflicts with a package another developer is creating/using (which is unlikely, but worth bearing in mind).
Your ideal solution would be to set up source control so that each developer can start from the same basic installation and submit/merge their finished work into your final product.
This is something we are also looking into at the moment, and will using Courier to handle our dev > staging > live processes, and potentially tying all our code into SVN at a later date.
Multiple developers setup
Hi Umbracians
I have a wish for finding a good solution on how to have multiple developers working on one umbraco project.
Each developer should have an instance of the umbraco site on their machine which is connected to a shared database.
My current challenge is that when one of the developers install a package from the Umbraco Repo. should all the other developers install the same package on their instance with the shared database in mind or how do you and your team manage this situation?
Hi Ole,
If you are sharing the same database then you will need to make sure that each developer has the same packages etc. The database will store the information about a package, but your developers individual projects won't have the files and folders that the database will refer to, which may cause errors.
By ensuring everyone has the same packages you won't cause problems further down the line if one of your developers creates something that conflicts with a package another developer is creating/using (which is unlikely, but worth bearing in mind).
Your ideal solution would be to set up source control so that each developer can start from the same basic installation and submit/merge their finished work into your final product.
This is something we are also looking into at the moment, and will using Courier to handle our dev > staging > live processes, and potentially tying all our code into SVN at a later date.
is working on a reply...