From a5a13930e51bcaad15e6a8ce1e8a4ab0f897596c Mon Sep 17 00:00:00 2001 From: Jonathan Rosenbaum Date: Mon, 27 Dec 2021 01:36:56 -0500 Subject: [PATCH] Adds more enlightenment for switching from development to production; adds vim and less to Dockerfile. Former-commit-id: a8c6c72a9c28f960a955ead231d7d17ff732630f --- Dockerfile | 2 +- README.md | 11 ++++++++--- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/Dockerfile b/Dockerfile index fa08392..7571563 100644 --- a/Dockerfile +++ b/Dockerfile @@ -8,7 +8,7 @@ MAINTAINER Jonathan Rosenbaum COPY . /app/BikeBike -RUN apt-get update && apt-get install -y nodejs postgresql-client +RUN apt-get update && apt-get install -y nodejs postgresql-client vim less # Note: phantomjs has been deprecated in favor of headless chrome WORKDIR /app/BikeBike diff --git a/README.md b/README.md index 4a2325a..12df2d0 100644 --- a/README.md +++ b/README.md @@ -15,21 +15,26 @@ Instructions can be found in docker-compose.yml, and docker-compose.build. You may easily switch between the production and development environment. One good reason for doing this is that some system administration tasks are handled differently in production. For instance, mail is delayed in production. -Realize you can always do things in the containe: +Realize you can always do things in the container .. the commands without docker-compose, or automate it all with a docker-compose script: `docker-compose exec bikebike /bin/bash` -### From production to development +### From production to development after changing .env ``` + docker-compose down + docker-compose up -d rake assets:clobber rake assets:precompile ``` -### From development to production +### From development to production after changing .env ``` + docker-compose down + docker-compose up -d rake assets:clobber rake assets:precompile + rake db:sessions:clear docker-compose restart bikebike ``` ### About that letsencrypt network in docker-compose.yml