DevOpsForge is a free, 100% client-side visual configurator for Docker Compose, Nginx, Caddy, healthchecks, and cloud backup scripts. Generate optimized production-ready environments in 60 seconds with zero server-side uploads.
No reviews yetBe the first to leave a review for DevOpsForge
Maker
📌
Hi Product Hunt! 👋
I got tired of copy-pasting outdated Docker Compose templates, hunting down port conflicts, and configuring SSL/reverse proxies from scratch. So, I built DevOpsForge.
It is a simple, lightweight helper that runs 100% locally in your browser (no configurations, databases, or secrets are ever uploaded to a server).
Key Features:
- Stack support: React, Next.js, Node/Express, Python/FastAPI, Go/Gin, Postgres, MongoDB, MySQL, and Redis.
- Reverse proxies: Auto-generate Caddyfiles or custom Nginx proxies.
- Extras: Inject container healthchecks, multi-stage production Dockerfiles, and automated database backups.
- One-click downloads: Export your config bundle sequentially in a single click.
I would love to hear your feedback on:
1. What languages, databases, or tools should I add next?
2. What advanced DevOps scripts would save you the most time?
Thank you for checking it out!
Report
The fact that everything runs in the browser and nothing gets uploaded is a huge relief for stuff like nginx configs. Generated a compose file with healthchecks in under a minute and it actually worked first try.
Report
Maker
Thank you so much, @elciogluna6892 ! That was the main reason I built this client-side. Uploading Nginx configs containing server IP addresses and domains always feels risky, so keeping it in the browser was a must.
So glad the healthcheck integration worked on the first try for you! Let me know if there are any other features or frameworks you'd like to see added.
Report
This is exactly the kind of tool I wish existed years ago when I was wrestling with nginx configs at 2am. One thing that would make it even more useful for me: a dry-run preview mode that shows the actual rendered files side by side before I download, so I can sanity check the output without spinning up a container.
Report
Maker
Thank you, @aysimayasanfkz! I've been in that 2 AM Nginx configuration struggle myself many times.
Regarding the preview: the dark-mode code panel on the right of the screen actually updates dynamically in real-time as you toggle options. You can click the file tabs at the top of it (like docker-compose.yml, nginx.conf, or Dockerfile) to sanity-check the code immediately before downloading!
That said, having a split-screen view to display two files side-by-side at the same time is a fantastic idea for wider monitors—I will definitely add that to the roadmap. Thanks for the suggestion!
Report
The 100% client-side angle is genuinely refreshing, especially for something dealing with infra configs. Would love to see a diff view that shows what changed between the generated config and a previous one I saved locally, makes it way easier to iterate without losing track of what I tweaked by hand after the initial generation.
Report
Maker
Hi Asiye! Thank you for the feedback.
That is an incredibly smart feature request. Since developers almost always tweak their generated configs by hand afterwards, having a way to compare the new output against a previously saved local file would be a huge time-saver.
Since the app is 100% client-side, we could implement this by letting you load your previous config file directly in the browser and rendering a side-by-side diff (using a JS diffing library).
I've officially added this "Local Config Diffing" feature to the product roadmap. Thank you for the suggestion!
Report
Love that everything runs in the browser with zero uploads, makes it actually usable for real client configs without trust concerns. The 60 second generation claim is impressively tight too.
Report
Maker
Thanks a lot for the feedback, @nilferwaxa ! You hit the nail on the head—client projects often have strict NDA or trust concerns, so keeping everything local in-browser was a top priority for this builder.
Awesome to hear that the 60-second generation claim held up for you! Appreciate your support.
The fact that everything runs in the browser and nothing gets uploaded is a huge relief for stuff like nginx configs. Generated a compose file with healthchecks in under a minute and it actually worked first try.
Thank you so much, @elciogluna6892 ! That was the main reason I built this client-side. Uploading Nginx configs containing server IP addresses and domains always feels risky, so keeping it in the browser was a must.
So glad the healthcheck integration worked on the first try for you! Let me know if there are any other features or frameworks you'd like to see added.
This is exactly the kind of tool I wish existed years ago when I was wrestling with nginx configs at 2am. One thing that would make it even more useful for me: a dry-run preview mode that shows the actual rendered files side by side before I download, so I can sanity check the output without spinning up a container.
Thank you, @aysimayasanfkz! I've been in that 2 AM Nginx configuration struggle myself many times.
Regarding the preview: the dark-mode code panel on the right of the screen actually updates dynamically in real-time as you toggle options. You can click the file tabs at the top of it (like docker-compose.yml, nginx.conf, or Dockerfile) to sanity-check the code immediately before downloading!
That said, having a split-screen view to display two files side-by-side at the same time is a fantastic idea for wider monitors—I will definitely add that to the roadmap. Thanks for the suggestion!
The 100% client-side angle is genuinely refreshing, especially for something dealing with infra configs. Would love to see a diff view that shows what changed between the generated config and a previous one I saved locally, makes it way easier to iterate without losing track of what I tweaked by hand after the initial generation.
Hi Asiye! Thank you for the feedback.
That is an incredibly smart feature request. Since developers almost always tweak their generated configs by hand afterwards, having a way to compare the new output against a previously saved local file would be a huge time-saver.
Since the app is 100% client-side, we could implement this by letting you load your previous config file directly in the browser and rendering a side-by-side diff (using a JS diffing library).
I've officially added this "Local Config Diffing" feature to the product roadmap. Thank you for the suggestion!
Love that everything runs in the browser with zero uploads, makes it actually usable for real client configs without trust concerns. The 60 second generation claim is impressively tight too.
Thanks a lot for the feedback, @nilferwaxa ! You hit the nail on the head—client projects often have strict NDA or trust concerns, so keeping everything local in-browser was a top priority for this builder.
Awesome to hear that the 60-second generation claim held up for you! Appreciate your support.