Update Docker Setup For Development

[aaronskiba]

Please complete the following fields as applicable:

What version of the DMPRoadmap code are you running? (e.g. v2.2.0)
3.3.1+portage-3.2.2

We can currently run the db services in the background by executing docker-compose -f docker-compose-development.yml up -d. There is also a docker-compose.yml and a corresponding Dockerfile to create an image for the rails server. However, these files need to be updated (e.g. Dockerfile has FROM ruby:2.6.6 and docker-compose.yml has DATABASE_URL: 'mysql2://db').

In addition, these files could be useful for the upstream DMPRoadmap repo. They have an outstanding ticket for a Docker setup for development DMPRoadmap#3282.

[aaronskiba]

Issue #213 (now closed and added here instead) describes another issue regarding Dockerfile:

In Dockerfile, multiple 'apt-get update' commands

What version of the DMPRoadmap code are you running? (e.g. v2.2.0)
v3.0.12

Expected behaviour:
In the Dockerfile, there are 2 statements which run , apt-get update. Once should be enough!

Actual behaviour:
Line 4: 4 RUN apt-get update -qq && \
Line 30: 30 RUN apt-get update && apt-get install -y yarn

[laceysanderson]

Based on the github workflows it looks like the current versions being tested (and thus the ideal ones to use in the docker setup) are:

• ruby: 3.1.4
• node: 16.6.0
• postgresql: 16 or 17 (not sure as the version is not specified and thus it's likely the most recent stable but 17 was just released in September making it a bit vague right now)
• mysql: 9.1

Is that right?

Pertinent workflows:

• https://github.com/portagenetwork/roadmap/blob/deployment-portage/.github/workflows/ruby.yml
• https://github.com/portagenetwork/roadmap/blob/deployment-portage/.github/workflows/postgres.yml
• https://github.com/portagenetwork/roadmap/blob/deployment-portage/.github/workflows/mysql.yml

[aaronskiba]

Based on the github workflows it looks like the current versions being tested (and thus the ideal ones to use in the docker setup) are:

• ruby: 3.1.4
• node: 16.6.0
• postgresql: 16 or 17 (not sure as the version is not specified and thus it's likely the most recent stable but 17 was just released in September making it a bit vague right now)
• mysql: 9.1

Is that right?

Pertinent workflows:

• https://github.com/portagenetwork/roadmap/blob/deployment-portage/.github/workflows/ruby.yml
• https://github.com/portagenetwork/roadmap/blob/deployment-portage/.github/workflows/postgres.yml
• https://github.com/portagenetwork/roadmap/blob/deployment-portage/.github/workflows/mysql.yml

Thank you for the helpful starting point. Looks like this issue is being raised in priority, so we'll have it working in the near future. :)