I've been trying to run foodsoft in production either with docker and docker-compose, going through all the issues until I obtain up and running containers, but I've not been able to connect to the app. I will open a different topic for docker-compose, here is for basic docker procedure :
Due to a Ruby issue with foodcoops/foodsoft:latest, I tried v4.6.0 wich runs smoothly
`/nonexistent` is not a directory.
Bundler will use `/tmp/bundler/home/unknown' as your home directory temporarily.
=> Booting Thin
=> Rails 4.2.10 application starting in production on http://0.0.0.0:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
Loading app configuration from config/app_config.yml
>> Thin web server (v1.5.1 codename Straight Razor)
>> Maximum connections set to 1024
>> Listening on 0.0.0.0:3000, CTRL+C to stop
docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
86ffa6ee79a8 foodcoops/foodsoft:4.6.0 "./docker-entrypoint…" 25 minutes ago Up 25 minutes 0.0.0.0:32776->3000/tcp foodsoft_web
c7df8d0db12e mysql:5.5 "docker-entrypoint.s…" About an hour ago Up About an hour 3306/tcp mysql
a89ca7e475d2 redis:3.2-alpine "docker-entrypoint.s…" 13 hours ago Up 13 hours 6379/tcp foodcoopsnet_redis_1
I then populated the database succesfully following https://github.com/foodcoops/foodsoft/blob/master/doc/SETUP_PRODUCTION.md
When I try to connect to the container with curl it looks ok,
curl -I 0.0.0.0:32776
HTTP/1.1 301 Moved Permanently
Server: thin 1.5.1 codename Straight Razor
but using the browser, I have this error : SSL_ERROR_RX_RECORD_TOO_LONG, and
!! Invalid request
appearing in the terminal below the running container's information.
I used "RAILS_FORCE_SSL=false" option when running it.