generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Labels
Status: Updatedupdate is ready for reviewupdate is ready for reviewdeck: staging not for stakeholderStaging deck https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fgStaging deck https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fgfeature: Code Cleanuplevel: mediumpriority: SHOULD HAVErole: DevOpssize: 3ptCan be done in 13-18 hoursCan be done in 13-18 hours
Milestone
Description
Overview
Set up docker-compose so that devs can easily run the dev environment without OS-specific issues. This includes the client, the server, and the database.
The goal is a more or less turn-key dev environment setup rather than leaving some setup steps in the documentation. Any extra steps should be scripted as much as possible.
Action Items
- Set up docker-compose for the dev environment
- database from Set up docker-compose for local db #765
- server
- client
- resolve .env file problem switching between localhost and docker
- auto-create the database and auto-apply migrations
- check that tests still run correctly
- Release dependency on Update scss to remove @import rules #2359 and Set up docker-compose for local db #765 and move them to the New Issue Approval column
Resources/Instructions
- See Contributing page for how to set up the dev environment on the host machine
- In order to not conflict with existing dev environment instructions, we should leave the
.env
file in the/server
directory and reference it from thedocker-compose.yml
in the root directory.
Metadata
Metadata
Assignees
Labels
Status: Updatedupdate is ready for reviewupdate is ready for reviewdeck: staging not for stakeholderStaging deck https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fgStaging deck https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fgfeature: Code Cleanuplevel: mediumpriority: SHOULD HAVErole: DevOpssize: 3ptCan be done in 13-18 hoursCan be done in 13-18 hours
Type
Projects
Status
Technical Review