Create a demo docker image about fat_free_crm HOT 15 OPEN

With this demo image, we could set up a demo heroku instance to let people test the app before they clone the repo

from fat_free_crm.

Is this issue still open? I would like to work on it.

from fat_free_crm.

from fat_free_crm.

I forked the repo. Can this issue be assigned to me under 'Assignees'? Thanks.

from fat_free_crm.

I forked the repo. Can this issue be assigned to me under 'Assignees'? Thanks.

done

from fat_free_crm.

Your Docker Compose file is pulling an image of postgres:9.5, which according to endoflife.date is deprecated. The official Postgres images on Docker Hub start with version 12.15-bullseye. Is your docker-compose.yml file out of date?

from fat_free_crm.

Your Docker Compose file is pulling an image of postgres:9.5, which according to endoflife.date is deprecated. The official Postgres images on Docker Hub start with version 12.15-bullseye. Is your docker-compose.yml file out of date?

it is; go ahead and bump this version

from fat_free_crm.

Ruby is also out of date. The Dockerfile is using ruby:2.7, which is deprecated according to endoflife.date. The official Ruby image on Docker Hub starts at 3.0-alpine, docker-hub-ruby. Is the Dockerfile up to date?

from fat_free_crm.

upgrading to Ruby 3.0 is kind of a bigger job. thats on my todo list after finishing the rails 7 migration. for now 2.7 should be fine

from fat_free_crm.

I'm having a similar issue as #961 when I run docker-compose. I created the two volumes pgdata and gems and run docker-compose up. Docker can create the /home/app directory, but it hangs on the RUN step and takes a really long time to run the apt-get commands (250s): Here's the error output. Rails doesn't appear to be able to connect to Postgres, from the error on lines 422-425.

from fat_free_crm.

from fat_free_crm.

Ref PR #1121

from fat_free_crm.

Steve, I tried setting the env variables to the values in docker-compose, which gave me a new error "could not translate host name "db" to address: Name or service not known". I then tried setting the host: host.docker.internal in the database.postgres.docker.yml file, and got the original "could not establish a connection" error message. I'll continue once PR #1121 is completed.

from fat_free_crm.

Steve, I tried setting the env variables to the values in docker-compose, which gave me a new error "could not translate host name "db" to address: Name or service not known". I then tried setting the host: host.docker.internal in the database.postgres.docker.yml file, and got the original "could not establish a connection" error message. I'll continue once PR #1121 is completed.

the issue youre experiencing is probably unrelated to the PR Steve is fixing. try deploying the postgres container using docker compose, then creating a side container and seeing if you can use the CLI to resolve the hostname of the pg container. may require tinkering with the docker compose yml

from fat_free_crm.