Containerize Dogehouse

About the Problem

Installing dependencies for the backend (Elxir API / Voice/WSS server) and frontend (React webapp / Puppeteer shenanigans AKA UI Tests and Lighthouse checks) is a mess and may cause dependency hell if left unmanged, and running them one-by-one can be also an distater.

Solution and To-Dos

• Make an docker-compose.yml file in the root directory that includes each subdirectiry’s Dockerfiles required for running the instance + database backend.
• Create an Dockerfile on each folder in the Dogehouse monorepo.

[ianjaku]

@Salman2301

@ianjaku If i remove it, it throws the error Cause the Dockerfile in kousa set the env as a production and we can create a new docker file for developement to avoid it may be?

Ah ye my bad, the Dockerfile is building a release so it will always run the releases.exs file.

The underlying issue is that you can’t use the current Dockerfile in dev (even when removing ENV MIX_ENV=prod) because the settings in releases.exs will overlap with the settings in dev.exs.

Creating a separate Dockerfile that doesn’t build a release and instead just calls mix run would be a decent temporary solution for now I think.

[ianjaku]

Could be interesting to also add add adminer to the docker-compose file, It’s extremely light weight and can be useful for testing.

Would be:

  adminer:
    image: adminer
    restart: "no"
    ports:
      - 5051:8080
    depends_on:
      - database

Data for postgres is located at /var/lib/postgresql/data so to add a volume we would need to add:

# In the database section
volumes:
  - dbdata:/var/lib/postgresql/data
      
# At the bottom of the file
volumes:
  dbdata: