https://github.com/sub-xaero/docker-ruby-on-rails
https://github.com/sub-xaero/docker-ruby-on-rails
docker docker-compose docker-image puma rails5 ruby ruby-on-rails rubyonrails
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/sub-xaero/docker-ruby-on-rails
- Owner: Sub-Xaero
- License: mit
- Created: 2018-08-08T19:27:04.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2018-08-08T19:27:10.000Z (almost 8 years ago)
- Last Synced: 2025-11-11T20:03:36.259Z (8 months ago)
- Topics: docker, docker-compose, docker-image, puma, rails5, ruby, ruby-on-rails, rubyonrails
- Language: Dockerfile
- Size: 1.95 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Quickstart
The docker-compose file mounts a volume called `/app` which is where the server will be sourced from.
There are also cache volumes mounted for the PostGRES data directory and the bundle install directory, so that you don't have to wait for bundles to install every `compose up`. To bust the cache, simply run `docker-compose down -v` to destroy the volumes, and then `docker-compose up` as usual.
The docker-start.sh file runs a `yarn install`, `bundle check || bundle install` to check if any gems are missing and if so, install them. Kills any artifacts blocking the server from running if the container is shutdown forcibly, and binds the server to port `3000` along with some self-signed SSL certificates, to comply with the new Chrome forced HTTPS protocol. This fixes the `ERR_SSL_PROTOCOL` white screen in Chrome when trying to use `rails server` or `rails s`, and the Puma Error in the rails logs: `HTTP parse error, malformed request (): #