-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Coolify Template for OpnForm with 1-Click Deploy Button #626
Comments
/attempt #626 Options |
attempt #626 |
@harshtech123: Reminder that in 7 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
Do you still plan on working on this @harshtech123 ? |
/bounty $100 |
/attempt #626
|
Note The user @harshtech123 is already attempting to complete issue #626 and claim the bounty. We recommend checking in on @harshtech123's progress, and potentially collaborating, before starting a new solution. |
Add Coolify Template for OpnForm with 1-Click Deploy Button
We’d love to have a Coolify template for OpnForm, our open-source form builder. The goal is to enable users to deploy OpnForm with a single click through Coolify.
Background:
OpnForm already has a working Docker setup, which you can find in our deployment documentation. The Docker configuration includes everything needed for running the application. The primary task for this issue is to adapt the Docker setup for Coolify and create a 1-click deploy button.
Deliverables:
Coolify Template: A template that adapts the existing Docker setup to Coolify.
.env File Generator Script: A script (or modifications to the current one) that generates
.env
files based on the Coolify deployment setup. Currently we use scripts/setup-env.sh, but we probably need to build an equivalent for Cooolify.1-Click Deploy Button:
docs
Merge Request to Coolify Repository:
Resources:
Skills Required:
If you have any questions or need clarification on this issue, feel free to comment below! 😊
Thank you for contributing to OpnForm!
The text was updated successfully, but these errors were encountered: