fix: make proWES run locally

[JaeAeich]

fixes - #93

Summary by Sourcery

Enable proWES to run locally by introducing environment-based configuration file selection, adding a Makefile for development tasks, and updating Docker Compose settings.

Bug Fixes:

• Fix the local execution of proWES by adjusting the configuration file path based on the environment.

Enhancements:

• Add a Makefile to streamline development tasks such as creating a virtual environment and running services locally.

Build:

• Update the Docker Compose command to correctly navigate to the application directory before starting the Gunicorn server.

Documentation:

• Add a development configuration file 'config.dev.yaml' to facilitate local development with specific settings.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR implements changes to make proWES run locally in a development environment. The main changes include adding a development configuration file, updating path configurations, introducing environment-based config selection, and adding development tooling through a Makefile and a development-specific docker-compose file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added environment-based configuration file selection	Added logic to select config.dev.yaml when ENVIRONMENT is set to DEV Added default ENVIRONMENT=DEV setting for local development Created new config.dev.yaml with development-specific settings	pro_wes/app.py pro_wes/config.dev.yaml
Updated API and service paths for local development	Modified API specification paths to include pro_wes prefix Updated docker command path to reference correct wsgi application Added specific pymongo version requirement	pro_wes/config.yaml docker-compose.yaml requirements.txt
Added development tooling and infrastructure	Created Makefile with development commands and targets Added development-specific docker-compose configuration Included commands for running app, Celery worker, and Docker services locally	Makefile docker-compose.dev.yaml

Possibly linked issues

• feat: run proWES API locally #93: The PR modifies configurations to allow proWES to run locally, addressing the issue directly.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @JaeAeich - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[uniqueg]

It's neat, but I will not approve this, given that we are planning to address this centrally through FOCA. Just use it locally on your system. After all, you're the only one currently working on this, and nobody else minded - so I don't see the need.