Creating a development environment, Phase 4, env setup #2265
Labels
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
Dependency
An issue is blocking the completion or starting of another issue
Feature: Board/GitHub Maintenance
Project board maintenance that we have to do repeatedly
feature: dev env
A separate development version of the website
role: back end/devOps
Tasks for back-end developers
size: 2pt
Can be done in 7-12 hours
Milestone
Dependency
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
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:
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
The text was updated successfully, but these errors were encountered: