Looking for some guidance for using Alpha with Git with a team on a single large project.
1) I open the Alpha project and enable git using the "git" button on the Alpha web projects control panel. This creates the .git folder within the "workspace" folder for the workspace I have selected. This happens to be my "default" workspace and currently the only workspace I have in this project.
2) I created a git folder on a network share and added a sub-folder with the same name as my project I use this as my shared remote repository. No workspace files, just the git tracking folders. I don't want to use github/bitbucket, I'd rather keep this all on our internal servers. Creating this folder, I then initialize it from the local repository (i.e. the default.webproject folder of my Alpha project)
3) Now I want to allow developers to work on this project, so I plan on using branches where each developer will get their own branch.
Here's where I need some guidance.....
1) Are all of us opening the same project on a network folder or should each developer make a local copy of the project and each have their own local project?
If we share a common project I think it will get confusing to see the untracked/modified file counts changing in the project as we all work on things throughout the day, but it seems wasteful to make local copies of the entire project for each developer. It also seems more error prone to have multiple copies of the project that need to be updated from the remote repository as opposed to a single shared project kept in sync with the remote repository.
If I have each developer do a clone to clone the remote repository to a local repository, this doesn't contain all the files needed to work on the project locally. For example, based on where Alpha places the .git folder in a single workspace of the project the only folder tracked is that single workspace folder. So cloning, clones the shared remote repository to a local copy but that clone does not contain the alpha project file and so you can't open the local copy of the cloned remote repository based on this. If I move the .git folder to the root of the folder alpha creates when you generate a new project will this cause other issues if it tries to sync the project file or other files contained in the root folder as opposed to a single workspace folder?
Thanks for any ideas on how to best implement this
Jeremy
1) I open the Alpha project and enable git using the "git" button on the Alpha web projects control panel. This creates the .git folder within the "workspace" folder for the workspace I have selected. This happens to be my "default" workspace and currently the only workspace I have in this project.
2) I created a git folder on a network share and added a sub-folder with the same name as my project I use this as my shared remote repository. No workspace files, just the git tracking folders. I don't want to use github/bitbucket, I'd rather keep this all on our internal servers. Creating this folder, I then initialize it from the local repository (i.e. the default.webproject folder of my Alpha project)
3) Now I want to allow developers to work on this project, so I plan on using branches where each developer will get their own branch.
Here's where I need some guidance.....
1) Are all of us opening the same project on a network folder or should each developer make a local copy of the project and each have their own local project?
If we share a common project I think it will get confusing to see the untracked/modified file counts changing in the project as we all work on things throughout the day, but it seems wasteful to make local copies of the entire project for each developer. It also seems more error prone to have multiple copies of the project that need to be updated from the remote repository as opposed to a single shared project kept in sync with the remote repository.
If I have each developer do a clone to clone the remote repository to a local repository, this doesn't contain all the files needed to work on the project locally. For example, based on where Alpha places the .git folder in a single workspace of the project the only folder tracked is that single workspace folder. So cloning, clones the shared remote repository to a local copy but that clone does not contain the alpha project file and so you can't open the local copy of the cloned remote repository based on this. If I move the .git folder to the root of the folder alpha creates when you generate a new project will this cause other issues if it tries to sync the project file or other files contained in the root folder as opposed to a single workspace folder?
Thanks for any ideas on how to best implement this
Jeremy
Comment