Common day-to-day operations and how to do them safely.
Open the project and go to the Deploy tab.
Review the exact commands that will run — change them if they look wrong.
Confirm the target and click Deploy. Watch the live log stream.
After the deploy finishes, check the health status. A passing heartbeat means the service is actually reachable, not just running.
The deploy is saved as a record. If something went wrong, you have the full log and can roll back.
Open the project and go to the Env tab.
Optizen shows the current file content fetched from the server.
Make your changes. Optizen validates what it can before saving.
On save, the previous version is backed up on the server before the new file is written.
The change appears in the activity log with a timestamp.
Open the project and go to the Proxy tab.
The current config is fetched from the server.
Edit and save. Optizen backs up the previous version, writes the new file, then reloads the proxy.
Check the proxy reload output for errors before assuming it worked.
Open the project and go to Logs.
Logs stream live from the server over SSH.
Use logs to understand what the runtime actually did — not just whether the container started.
Combine logs with heartbeat status: logs tell you what happened, heartbeats tell you if the service is reachable.
Open the project and go to Deploy history.
Find the previous successful deploy.
Click Rollback. Optizen will re-run the deploy commands from that record.
If re-auth is enabled, you will need to verify your session first.