ER: update docker-compose.yml to remove warning when running `docker-compose up`

[roslynwythe]

Emergent Requirement - Problem

When running docker-compose up the following message appears

$ docker-compose up
time="2024-11-26T16:24:37-08:00" level=warning msg="C:\\Users\\rosly\\hfla\\website\\docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"

According to this article, the version attribute is informative only and will result in a warning message that it is obsolete if used.

Issue you discovered this emergent requirement in

Date discovered

11/26/2024

Did you have to do something temporarily

• YES
• NO

Who was involved

@roslynwythe

What happens if this is not addressed

potential confusion

Resources

article

Recommended Action Items

• Make a new issue
• Discuss with team
• Let a Team Lead know

Potential solutions [draft]

• Create a new issue from this ER using the "Blank Issue Template"
• This issue involves editing a file in the codebase. As you are working on this issue, use similar issues such as Update Project Profile: Hackforla.org Website Add Xavier Neal-Carson #8361 as guides.
• The "Overview" should follow the concise format "We need to do X for Y reason". Note that the ER title states what needs to be done, and the "What happens if this is not addressed" explains the reason why.
• The "Action Items" should describe which file needs to be edited, how it needs to be edited, and how the dev will verify that their changes did not break anything.
• The issue you are creating is probably a good first issue, .25 pt, a back end/ Dev Ops role, involves Docker. Choose the appropriate labels.
• Ask questions if you would like more guidance.
• When you think this is ready, add the ready for merge team label, and let us know via Slack or at a meeting.

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels