...
- Production
- nc-nginx docker service on s14
/usr/share/nginx/html/tssgTech
Endpoint is https://technologynursery.org/tssgTech
- Deployment to production
Performed by alias tssgTech.update
Executed manually by Joel
- Git repo tssgTechMVP master branch
copied to nc-nginx web server
- Git repo tssgTechMVP master branch
- nc-nginx docker service on s14
- Staging
- nc-nginx docker service on s14
/usr/share/nginx/html/tssgTechMVP
Endpoint is https://technologynursery.org/tssgTechMVP
Represents tssgTechMVP master branch
- nc-nginx docker service on s14
/usr/share/nginx/html/tssgTechMultipage
Endpoint is https://technologynursery.org/tssgTechMultipage
Represents tssgTechMVP multipage branch
- Deployment to staging
Performed by root@s14:bin/tssgTechMVP.deploy
Executed every 5 minutes.
- Git repo tssgTechMVP multipage branch
copied to nc-nginx web server
- Git repo tssgTechMVP master branch
copied to nc-nginx web server
- Git repo tssgTechMVP multipage branch
- nc-nginx docker service on s14
- Git Repository
- tssgTechMVP
- master branch
- This must always represent a clean, bug free source of the web site.
- Gets deployed manually to nc-nginx web server as production
- Gets deployed every 5 minutes to nc-nginx web server as staging tssgTechMVP
- multipage branch
- This is the web site's new implementation
- Gets deployed to nc-nginx web server as staging tssgTechMultipage
deployed every 5 minutes
- master branch
- tssgTechMVP
- Workflow
- 1 Dev works in a dev or feature branch (e.g. multipage)
- 2 Dev sees multipage branch changes represented every 5 minutes in tssgTechMultipage endpoint
- 3 When acceptable, Dev merges to master branch
- 4 Dev sees master branch changes represented every 5 minutes in tssgTechStagedMaster endpoint
- 5 When acceptable, Dev deploys master branch to production tssgTech endpoint
Action items
- Refactored tssgTechMVP git repo to just be tssgTech
- Refactored multipage branch to have site and tools directory. Later we will add a tests directory.