Creating a development environment, Phase 4, env setup
- Dominant language
- JavaScript
- Stars
- 363
- Forks
- 872
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 18
Description
### Dependency
- [ ] #2264
### 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 configure environments created in phase 3.
### Action Items
- [ ] Moves file from hackforla/website to hackforla/website-uat.
- [ ] Host the files added to hackforla/website-uat under the provided UAT domain
- [ ] Move files from hackforla/website-dev to hackforla/website
- [ ] Host the files added to hackforla/website under the name hackforla.org
- [ ] Host the files in hackforla/website-dev under the provided DEV domain
- [ ] Once this issue is completed, please do the following for #2658:
- [ ] Move it to the New Issue Approval column
- [ ] Remove the "Dependency" label from it
- [ ] Add a "ready for dev lead" label to it
### 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](https://en.wikipedia.org/wiki/Development,_testing,_acceptance_and_production)
Contributor guide
Assessment
This issue has not been assessed yet.