zelyqSeparate staging and production
Choose a machine and variables for each environment. Require an admin’s approval for protected environments, or freeze deployments during a release window.
SHIP / Deployments
Your application.Your production.
Deploy from a pipeline to machines you control. Give each environment its own credentials, check the release, and keep a way back.
BUILT FOR THE WORK
What you can do with Deployments.
Build for the application
Use an existing Dockerfile or let Zelyq generate one for supported Node, Python, Go, and static applications. The build runs on the target machine.
Check before accepting
A failed health check causes the deployment to fail and the previous version to be restored or retained, depending on the deployment mode.
Operate the running app
Follow logs, view CPU and memory, restart or stop the app, and inspect release history. Promote the image tested on staging without rebuilding it.
A CLEAR PATH THROUGH
From setup
to your next step.
Follow the guide for configuration details and the complete workflow.
Open the documentation- 01Connect a deployment machine with Docker
- 02Create staging and production environments
- 03Deploy a checked build through a pipeline
- 04Watch health, logs and release history
BEFORE YOU BEGIN
A few useful details.
Can I use my own domain?+
Yes. Give an app an exact address or configure an environment domain. DNS, network ports, and the chosen HTTPS mode must be configured correctly.
Are all deployments without downtime?+
No. Domain-based deployments use the proxy to start and health-check the new version alongside the current version before switching traffic. Direct-port deployments can have a brief interruption.
Does Zelyq provide the deployment machines?+
You connect your own hosts. Current deployment environments use Docker on supported Linux or macOS machines over SSH; pipeline runner OS support is broader.
MAKE IT YOUR WORKSPACE
Start with the work in front of you.
Run Zelyq yourself and connect the parts your team needs.