Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
set up dev server #1560
We'd like to set up a dev instance of OpenOpps with a vanilla config to make it easier for the open source community developers to work with the new US gov team at OPM (Office of Personnel Management). The goal is to have a running instance that always has the latest dev branch. (We used to have this at 18F, but never re-created it when we moved to a separate private-public open source org.)
@ultrasaurus Currently staging has been running fine on a 512M instance in cloud.gov and prd has 2 1GB instances. So for dev test 512M seems to running just fine. part of producing the docker images should include copying in the node_modules thus not require an attempt to install them on startup that would be unpredictable at best in a production situation. Also I'd look into setting --max-old-space-size node option when running node in the docker container. cloud foundry sets this option appropriately for us when we set
If there is an environment variable in the docker container with the current memory allocation we could create a script similar to this one to add it dynamically at start up
For the docker image, we should worry more about runtime, like @lawrencek76 said. The node_modules should be installed outside of spinning up (mounting a local volume into the VM) the docker image or even better copied into it the Docker image before publishing it to Docker Hub. I think it's okay for the image to be large as it should contain all the vendor dependencies for a faster startup time.
This was referenced
Feb 18, 2018
I've updated the top issue description to reflect current approach of deploying on AWS.
In case these are needed in the future, below are my prior notes from experimenting on digital ocean:
then I get an error running the migrations: