Creating a development and UAT environment, Phase 3, admin tasks

[Aveline-art]

Dependency

• Creating a development environment, Phase 2, documentation #2266

Overview

As a developer, we are interested in creating environments for our websites that are friendly for the whole team to review. For this issue, we will create new repositories and provide domain names to host other versions of the website.

Action Items

• Provide a domain name that is appropriate for hosting the DEV repository

The following must be done in order:

• Provide a repository named hackforla/website-prod
• Release dependency on Creating a development environment, Phase 4, env setup #2265
  • On this issue, edit the top post to include the domain names in Resources and Instructions.
  • Add relevant team members to the website-prod repository

Resources/Instructions

This issue concerns creating new environments for the HackForLA website team. Documentation below will go into more details, but to briefly summarize, we want to transition from one environment to 2:

1. hackforla/website-prod - this environment will be a production environment, meaning code here is for a website made specifically with external clients in mind
2. hackforla/website-dev - this environment will be exactly like our current environment. As the issue taker, you should be familiar with how this works. The only difference is that changes here will be propagated to prod instead of reflecting on the website.

Notice how each of the environments are worded like a repository--because they are! For each environment, we are interested in hosting different versions of the website. We use GitHub pages as our host, which means that it is impossible for us to host three sites off of one repository. Therefore, the key to this issue is to find a method through which changes can be propagated from DEV -> Prod.

Development, testing, acceptance and production