Page History

...

•  We will follow the guidelines for code review as specified in Requesting a merge to scheduledb of your code contributions.
•  The scheduledb branch will be merged into the master branch.  The master branch contains the state of the current tssg.tech web site.
•  The database will be compared to the data on the current site and updated to match
  •  We should split up the List All pages and each Web Team member update his/her collection data vs the True Data
  •  Afterward, do the same for the static pages in the new Site folder.  Jim Turner 17 Mar 2021 (or when it is done) Let client make modifications to either the database (through the FrontEnd) or raise tickets for the Web Team to change the Site content as necessary.
  •  Final step: see to it somehow that this (newest) data is in the (initializing) db saved in the Git repository.  Not needed because the db is persistent.  Just change the data through the FrontEnd UI.
•  Ralph A. Navarro Jr.13 Mar 2021 Upgrade a13 storage from 128G to 512G
•  A Jenkins project will deploy the master branch to a staging (i.e. QA) endpoints.  
  •  decide the names of the services' subdomain endpoints
    •  Website
      https://tssg.tech → a13
      
    •  Backend
      https://backend.tssg.tech → a13
      
    •  Admin (FrontEnd)
      https://admin.tssg.tech → a13
  •  Ralph A. Navarro Jr. 13 Mar 2021 configure Nginx to reverse-proxy them to the underlying services
  •  Paul Scheidemantel 14 Mar 2021 Enable scheduledb.env working in private branch taken from master branch
    to configure either dev or prod endpoints by passing an environment variable (deployEnv) option (default=dev) to scheduledb.env.
  •  Paul Scheidemantel 14 Mar 2021 Create a prod.install for deploying scheduledb to prod.
  •  Ralph A. Navarro Jr. 14 Mar 2021 configure Jenkins
  •  Ralph A. Navarro Jr. 14 Mar 2021 execute the deploy
•  Automated and manual tests will be run against the staging production area.  This will verify that the merge has happened successfully before moving to the next step in the pipeline.  Corrections will be made if needed until the staging area quality can be assured.
  •  create "smoke" tests to verify service inter-connectivity
  •  enhance code coverage for all UX features
•  Another Jenkins project will deploy the master branch to the production endpoints.  We will be 
•  Automated and manual tests will be run against the production endpoints.  This will verify the quality of the production endpoints.  Corrections will be made if needed until the production area quality can be assured.
•  Once in production, create a backup script to backup the database data periodically (either cron job or manually).

...