Deploy from GitHub

Connect your GitHub repository and deploy your app. Dublyo auto-detects your framework and builds it for you.

1

Connect GitHub

Your GitHub account is already linked via OAuth login

2

Select a repository

Browse or search your repos and pick a branch

3

Configure build

Dublyo auto-detects your framework — customize if needed

4

Deploy

Select a server, deploy, and watch your app go live

5

Automatic deployments

Push to your branch and Dublyo rebuilds automatically

Connect GitHub

Your GitHub account is already connected via OAuth login. When you signed in to Dublyo with your GitHub account, the connection was established automatically — there are no extra authorization steps or tokens to configure.

Go to the GitHub Deploy page from the sidebar. You can access any of your repositories, including private repos, organizations you belong to, and forks.

Tip: Dublyo only accesses your repositories when you explicitly choose to deploy from one. Your code is pulled at build time and never stored permanently on our infrastructure.

Select a Repository

Once you're on the GitHub Deploy page, you'll see a list of all repositories available to your GitHub account. Follow these steps to select the one you want to deploy.

1

Go to GitHub Deploy page

Click GitHub in the sidebar to open the deploy page

2

Browse or search by name

Scroll through your repositories or use the search bar to find a specific repo

3

Select the repo

Click the repository you want to deploy to continue to configuration

4

Choose the branch

Defaults to main or master — select a different branch if needed

Tip: If you don't see a repository, make sure it's not archived and that your GitHub account has access to it. Organization repos may require admin approval.

Configure Build

After selecting a repository, Dublyo auto-detects your framework and pre-fills the build configuration. You can customize any of these settings before deploying.

Build Settings

Set the build command, start command, port, and environment variables for your app. Dublyo inspects your project files (package.json, requirements.txt, go.mod, etc.) to determine the right defaults.

# Example: Node.js / Next.js detected
Build command: npm run build
Start command: npm start
Port: 3000

Detected Frameworks

Dublyo recognizes a wide range of frameworks and languages out of the box. Common frameworks detected include:

Next.js Nuxt Express Django Flask Go Static Sites

If your project includes a Dockerfile, Dublyo will use it automatically instead of auto-detection.

Environment Variables

Add environment variables directly in the deploy configuration. These are encrypted and injected at build time and runtime. Common examples:

DATABASE_URL=postgresql://user:pass@host:5432/db
NODE_ENV=production
API_KEY=your-secret-key
Tip: You can update environment variables after deployment from the app detail page without needing to redeploy from scratch.

Deploy

Once your build is configured, you're ready to deploy. The entire process is visible in real-time so you can monitor every step.

1

Review configuration

Double-check your build command, start command, port, and environment variables

2

Select target server

Choose which server to deploy your app to from the dropdown

3

Click Deploy

Hit the deploy button to start the build process

4

Watch build logs in real-time

Stream live build output — see dependency installs, compilation, and startup

5

App goes live

Your app is accessible at a .dublyo.co subdomain with automatic HTTPS

https://my-app-abc123.dublyo.co

After deployment completes, you'll see a "What's Next" card with options to add a custom domain, view logs, or deploy another app to the same server.

Tip: If the build fails, check the logs for the exact error. Most issues are caused by missing dependencies or incorrect build commands. You can fix the issue and redeploy without starting over.

Automatic Deployments

Push to your branch and Dublyo automatically rebuilds and deploys your app. No manual intervention required — your latest code is always live within minutes of merging.

How It Works

Automatic deployments are webhook-based — no polling. When you push a commit to your configured branch, GitHub sends a webhook to Dublyo, which triggers a new build and deploy cycle immediately.

1

Push code to your branch

git push origin main

2

Webhook triggers build

Dublyo receives the push event and starts building automatically

3

New version goes live

Zero-downtime deploy — the old version serves traffic until the new one is ready

Disable Auto-Deploy

If you prefer manual deploys, you can disable automatic deployments from the app detail page. When disabled, pushes to your branch will not trigger a rebuild — you'll need to click Redeploy manually when you're ready.

Tip: Use auto-deploy for staging environments where you want every push to go live, and manual deploy for production where you want more control over releases.

Troubleshooting

Running into issues? Here are the most common problems and how to fix them.

Build Fails

If your build fails, check the build command and make sure all dependencies are listed in your project's dependency file (package.json, requirements.txt, go.mod, etc.). The build logs will show the exact error.

# Check that your build command works locally first
npm run build
Common fix: Make sure your package.json includes all required dependencies (not just devDependencies) and that your build script is defined in the scripts section.

Port Mismatch

If your app deploys but doesn't respond, ensure your app listens on the port configured in Dublyo. The configured port must match the port your application actually binds to at runtime.

# Your app should listen on the configured port (e.g., 3000)
app.listen(process.env.PORT || 3000)
Common fix: Use the PORT environment variable in your app and set it to the same value in the Dublyo deploy configuration.

Environment Variables Missing

If your app crashes on startup with errors about missing configuration, you likely need to add environment variables in the deploy configuration. Database URLs, API keys, and secrets should all be set before deploying.

# Add all required env vars in the deploy configuration
DATABASE_URL=postgresql://user:pass@host:5432/mydb
Tip: You can update environment variables after deployment from the app detail page. The app will restart automatically with the new values.

Need Help?

Can't find what you're looking for? Check the full documentation or reach out.

Full Documentation Contact Support