Developer Websites
In your how directory you will see a new directory epro, this is the base directory
with the code base living in /home/mark.gregory@mbpa.com
All of your work should take place in this environment using the branches as defined above
you can switch your own environment with git checkout complete you work and then merge
into the develop branch and switch back to complete testing. its wise also to do a git pull origin develop
to collect other developer changes, if at this stage you get merge conflicts you must resolve these and push back to
develop. and merge back into your own issue, feature or hotfix branch.
This will eliminate all of the code overwrites suffered to date
Defined Hosts
192.168.0.81:10020 Mark Gregory 192.168.0.81:10021 Tomasz 192.168.0.81:10022 Malak 192.168.0.81:10023 Brad 192.168.0.81:10024 Karl
When we have defined the firewall exclusions you will be able to substitute 192.168.0.81 for 164.39.2.139 we will expand this list as require when new developers are provisioned.
The current MPBA testing URL is http://164.39.2.139:10008/admin
and a backup on http://164.39.2.139:10011/admin
Production Deployment Process
- Prior to release day a code freeze takes place
- A new branch is created release/version-date
- UAT servers are switched to this branch and retested
- RELEASE DAY, merge release/version-date into master
- Seek release approval via slack.
- Deploy master and then test release and perform any hotfixes as require
- Push any hot fixes back and merge release/version-date into develop
- Release complete - alert team and then code freeze removed.
- Release issues revert the comment and liaise with team.
The release should take place by the selected developer and on a rota if possible so all developers are upto date with how to release the system.
Basic System Information
PHP Version: 8.0 Node Version: 16.20.2 Laravel Version: 8.X
Git Branch Structure
- MPBA Server /develop
- MediaDev /stage
- MediaUat /qa
- Production /master