planning a Git workflow

gazhopkins
gazhopkins
Hopefully someone can shed some light on how I can achieve something which I think is easy but for the life of me cannot work out. I have built a CRM portal which has different modules: [CODE] -Secure -Module1 (module 1's back end) -Module2 (module 2's back end) -Module3 (module 3's back end) -web -Module1 (module 1's back end) -Module2 (module 2's front end) -Module3 (module 3's front end) -core -classes -css -js etc.... [/CODE] I want to achieve the following: [LIST] [*]Each module to be separated into it's own repo (Module 1 front end and Module 1 back end, Module 2...) [*]The core files to in its own repo [/LIST] This is so one of the three developers here can work on their own module without having to constantly pull/push (at the moment someone has set the entire site as one big repo!). Can anyone suggest a solution?

Last updated

gazhopkins
gazhopkins
Thank you, you have saved a lot of hair-pulling!
gazhopkins
gazhopkins
Can this be done using the Dev site? The dev site already has the folder structure and it is what we use to view the site before we make aspects live. I suppose Im asking if I wanted to checkout Module 1 (see below) it will omit the other directories: [CODE] -var -www -secure -Module1 (gets checked out) -Module 2 (gets ignored) -Module 3 (gets ignored) ... -web -Module1 Frontend (gets checked out) -Module 2 Frontend (gets ignored) -Module 3 Frontend (gets ignored) ... -core -js ... [/CODE]
gazhopkins
gazhopkins
The dev is just a separate server (exact copy of live)
gazhopkins
gazhopkins
At the moment we only have one git repository - Dev, this is the entire site. It's not a problem starting [Git] from scratch, I just want each module be separate but still be able to view the dev-site (retain it's current directory structure)
gazhopkins
gazhopkins
At the moment, someone has initiated git in the root directory of the site (/var/www/vhosts/sitename/). This reflects any changes made via Git. I reckon this is the wrong thing to do, so I want to overhaul it so each developer can work on the dev site using each module's repo (frontend and backend) push their changes and see the results. I was also looking at branching off the main repo and creating instances of the site for each branch created, but that seemed overly difficult and overkill for what is needed. I just want each developer to be able to work on a module (using any core files like CSS, JS, etc) and see what happens on the dev site before they sign it over to be put on the live site (separate server). The process I envisage is: [CODE] 1. Developer 1 checks out Module 1 (/var/www/vhosts/sitename/secure/module1 and /var/www/vhosts/sitename/web/module1 and core) -> 2. Developer 2 checks out Module 2 (/var/www/vhosts/sitename/secure/module2 and /var/www/vhosts/sitename/web/module2 and core) -> 3. Developer 1 finishes changes - commits - pushes and tests via dev.sitename.com 4. Developer 1 finished work on Module 1 5. Developer 2 finishes changes - commits - pushes and tests via dev.sitename.com 6. Developer 2 finished work on Module 2 7. Manager tests all changes and uploads to live website [/CODE]

1-11 of 11

Reply to this discussion

You cannot edit posts or make replies: You should be logged in before you can post.

Post a reply
639 views