Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating a development environment, Phase 4, env setup #2265

Open
10 tasks
Tracked by #2658
Aveline-art opened this issue Sep 15, 2021 · 0 comments
Open
10 tasks
Tracked by #2658

Creating a development environment, Phase 4, env setup #2265

Aveline-art opened this issue Sep 15, 2021 · 0 comments
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

Comments

@Aveline-art
Copy link
Member

Aveline-art commented Sep 15, 2021

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

  • 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 Investigate why Credits page displays each item alphabetically locally but in a different order on the live website #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

@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing labels Sep 15, 2021
@Aveline-art Aveline-art changed the title Creating a development environment for our website, Phase 4 Creating a development environment, Phase 4, env setup Sep 15, 2021
@Aveline-art Aveline-art added Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Complexity: Small Take this type of issues after the successful merge of your second good first issue role: back end/devOps Tasks for back-end developers Dependency An issue is blocking the completion or starting of another issue and removed Role: Administrative Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing labels Sep 26, 2021
@SAUMILDHANKAR SAUMILDHANKAR added size: 1pt Can be done in 4-6 hours size: 2pt Can be done in 7-12 hours and removed size: 1pt Can be done in 4-6 hours labels Jun 19, 2022
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone Mar 5, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the feature: dev env A separate development version of the website label Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Development

No branches or pull requests

3 participants