Skip to content

#625 Configure Docker Compose for Production Deployments#682

Open
Olamidepy wants to merge 1 commit into
ceejaylaboratory:mainfrom
Olamidepy:feature/issue-625-configure-docker-compose-for-produc
Open

#625 Configure Docker Compose for Production Deployments#682
Olamidepy wants to merge 1 commit into
ceejaylaboratory:mainfrom
Olamidepy:feature/issue-625-configure-docker-compose-for-produc

Conversation

@Olamidepy

@Olamidepy Olamidepy commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

Closes #625


This PR addresses #625 by configuring Docker Compose profiles for production and testnet environments. Optional monitoring and observability services are now placed under the monitoring profile so they do not start by default during standard deployments.

Key Changes

  • Standard Compose: Added profiles: [monitoring] to jaeger, prometheus, alertmanager, and blackbox-exporter in docker-compose.yml.
  • Testnet Compose: Applied the monitoring profile to jaeger and prometheus in docker-compose.testnet.yml.
  • Core Optimization: Ensures only core services (backend, postgres, redis, and dashboard) start by default, reducing deployment overhead.

@Olamidepy

Copy link
Copy Markdown
Contributor Author

@Ceejaytech25 Kindly merge

@drips-wave

drips-wave Bot commented Jun 27, 2026

Copy link
Copy Markdown

@Olamidepy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Configure Docker Compose for Production Deployments

1 participant