Build Logs, Environment Variables and Rollback

These tools are on the Settings tab of every app deployed from a Git repository.

Deploys and build logs

The Deploys card lists the recent builds of your app: whether each one succeeded, failed or is still building, the commit, its message and the time. Press View log on any row to read the build output. A build in progress refreshes by itself. Values of your own environment variables are replaced with *** if a build prints them. A very long log shows only its last part.

Build logs can be read by team members with the Developer role or higher.

Roll back

If a deploy breaks your app, press Roll back to this on an earlier successful deploy. FlyNode builds and runs that exact commit again. You can only go back to a commit this app has already deployed successfully.

After a rollback the app is pinned to that commit: a banner says so, and new pushes keep deploying the pinned version instead of the latest code. When you are ready, press Follow the branch again. FlyNode then deploys the newest commit of your branch and goes back to updating on every push.

Environment variables

The Environment variables card lists the settings and secrets your app reads while it builds and runs.

• Values are hidden until you press the eye icon.
• Add variable creates one. Names use letters, digits and underscores and cannot start with a digit. Names that start with COOLIFY_ or SERVICE_ are managed by the platform and cannot be set.
• Paste a .env reads a whole .env file at once: KEY=value lines, an optional export prefix, comments and quoted values. Nothing is saved until you press Save.
• Copy as .env copies the current variables so you can use them for local development.
• Save and redeploy saves your changes and rebuilds the app so it picks them up. Save only keeps them for the next deploy. A variable is read when the app starts, so it only takes effect after a deploy.

Changing variables needs the Developer role or higher. Never put real secrets in the repository itself; keep them here.

See also

Deploy a GitHub Repository and Deploy a Private Repository.