Skip to content

Commit f21e1ff

Browse files
committed
Fixup docker compose
1 parent c53d737 commit f21e1ff

File tree

4 files changed

+3
-9
lines changed

4 files changed

+3
-9
lines changed

Dockerfile

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,5 +13,7 @@ RUN bundle install
1313
# Copy application
1414
COPY . .
1515

16+
RUN echo " secret_key_base:" "$(bundle exec rake secret)" >> config/secrets.yml
17+
1618
# Build app and run migrations
1719
RUN RAILS_ENV=production bundle exec rake assets:precompile

README.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -29,12 +29,6 @@ After proper set database just run the seeder. It gives an admin user with admin
2929
Easy deployment could be achieved with Docker and Docker-compose. I suggest to create two volumes for db data and public data, to easily find later these volumes. Then you need to set some variables, so open `docker-compose.yml`, then modify the following lines:
3030

3131
```yaml
32-
environment:
33-
# Add your secret key
34-
- SECRET_KEY_BASE=
35-
36-
...
37-
3832
# Add your volumes
3933
public_folder:
4034
external:

config/secrets.yml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,4 +19,3 @@ test:
1919
# Do not keep production secrets in the repository,
2020
# instead read values from the environment.
2121
production:
22-
secret_key_base: <%= ENV["SECRET_KEY_BASE"] %>

docker-compose.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,7 @@ services:
1616
build: .
1717
command: bundle exec rails s -p 3000 -b '0.0.0.0'
1818
environment:
19-
# Add your secret key
20-
- SECRET_KEY_BASE=
19+
- RAILS_SERVE_STATIC_FILES=true
2120
- RAILS_ENV=production
2221
- ELASTICSEARCH_URL=http://elastic:changeme@elastic:9200
2322
- DATABASE=leltar

0 commit comments

Comments
 (0)