Hello World - Dokploy Template

Deployment Guide

This is a simple Flask template app. Follow these steps to deploy your own app using Dokploy.

1. Create Your Repository

Go to GitHub.com and create a new repository
Name it something like 1r-apps-yourappname
Clone this template or create your own Flask app
Push your code to GitHub

git init git add . git commit -m "Initial commit" git remote add origin [email protected]:yourorg/your-app.git git push -u origin main

2. Create Project in Dokploy

Open Dokploy dashboard
Click "Create Project"
Choose "Application" type
Select "GitHub" as source
Enter your repository URL
Choose build type: Nixpacks (recommended) or Dockerfile

Tip: This template includes both Nixpacks configuration and Dockerfile, so either option will work.

3. Configure Domain & SSL

In Dokploy, go to your app's Domains tab
Add your domain (e.g., apps-yourapp.1ravel.com)
Click "Generate Certificate" to enable HTTPS
Select "Let's Encrypt" for free SSL
Make sure your domain points to the server IP in your DNS settings

https://apps-yourapp.1ravel.com

Important: SSL certificate generation requires that your domain DNS is already pointing to the server. Certificate generation may fail if DNS is not configured correctly.

4. Deploy Your App

Click "Deploy" button in Dokploy
Watch the build logs for any errors
Once deployed, your app will be accessible at your configured domain
Check the /health endpoint to verify it's running

Success: Your app should now be live and accessible via HTTPS.

What's Included

Flask App

Dockerfile

Nixpacks Config

Health Check

Customization

To build your own app:

Edit app.py to add your routes and logic
Update requirements.txt with your Python packages
Modify this template in templates/index.html
Add environment variables in Dokploy's settings
The health endpoint at /health is required for monitoring

Common Issues

Port Configuration: Make sure your app listens on the PORT environment variable (default: 8080)
SSL Errors: Ensure your domain DNS is pointing to the server before generating certificates
Build Failures: Check that all dependencies are listed in requirements.txt
502 Bad Gateway: Verify the app is running on the correct port and the health check passes