From your code to a checked first release.
Connect your code, review what it needs and choose where it runs. Then follow the release from build to verification.
01 · Connect your code.
Choose a repository through the GitHub App, or connect GitLab, Gitea or Bitbucket Cloud through webhooks.
02 · Review what the app needs. Beta
A quick read proposes the app type, which you can change. Detection then reads the runtime, extensions, database, cache, workers and scheduler. Nothing is set up until you confirm the proposed requirements.
Confirmation prepares the recorded setup for the servers the app uses. Requirements move from Provisioning to Provisioned, then Active after the first successful deploy. How setup changes stay recoverable.
03 · Choose fresh servers or Layover.
Use fresh servers in your provider account. Setup replaces the operating system, lays out the disks and erases their contents. strackt does not adopt an existing production server in place.
You need at least 2 GB memory and 20 GB disk (4 GB memory recommended), x86_64 or ARM with UEFI, and root or sudo SSH access to a fresh Ubuntu, Debian, CentOS, Rocky, Alma, Fedora or openSUSE Leap installation. Adoption typically takes 5–10 minutes. Read the connection and adoption checklist.
No servers yet? Layover is temporary hosting while you arrange your own: 30 days on us, one per team, then €10 a month excl. VAT. Pricing and separate provider costs.
Bringing an existing app?
Keep your old hosting until you have transferred files and data, checked the app on its new address and are ready to switch your domain. The moving guide covers the transfer, final sync and cutover warnings. Jan Peter (JP) can help by email or chat.
04 · Deploy the first release.
Secrets are encrypted separately for each environment and written to the servers on every deploy. The app gets an HTTPS address on on-strackt.dev; your own domains get certificates automatically. DNS and certificate checks run every 5 minutes.
From one release to the next.
A later Laravel zero-downtime deploy: prepare beside the serving release, switch traffic, then check. The way back is a separate failure scenario.
The app keeps serving.
On later deploys, the current release keeps answering requests while the next release is built beside it. On the very first deploy, there is no previous release yet.
Get the next release ready.
PHP dependencies and front-end assets are prepared in the new release. The environment is checked and configuration cached before traffic moves.
Migrations run before the switch.
The new release runs the migrations while the current code still serves traffic. Keep migrations compatible with that code; switching releases does not undo a schema change.
Traffic moves to the new release.
Once preparation has finished, the new release takes over. The previous code stays on disk as the way back.
Check the release that is now serving.
Release verification is on by default. After the PHP reload, strackt probes the site and retries server errors for up to 30 seconds. An HTTP response below 500 lets the deploy continue.
Server errors? Return to the previous code.
If server errors persist through the check and a previous release is available, strackt switches back and marks the deploy failed. This returns the code, not the database. Migrations stay applied.
The check can be switched off. If the site cannot be reached, the probe cannot run, or too little deploy time remains, the deploy continues with a warning. It only checks the route it probes. After a bad migration, recover the database separately from an available database snapshot. More about deploys and recovery.
05 · Check the app. Continue working.
Open the app at its HTTPS address and check its behavior. On GitHub, pull requests get separate preview environments; closing a pull request removes its preview according to the cleanup settings. Previews are GitHub-only today.
Between releases, strackt handles the ongoing server work. Security fixes go onto running servers within 24 hours. Only a reboot waits. Routine reboots use your window with at least seven days’ notice. Expedited security reboots use your window after a 72-hour lead time. An actively exploited flaw overrides the window: reboot within 24 hours, with four hours’ notice. Follow a fix and its reboot rules.
Off-server backups in your own storage are in beta; they need a backup destination. See the complete capability overview and conditions.
When you want the keys back. Beta
You can leave strackt and keep the app running on your servers. Handover is in beta and is not enabled in every workspace. It needs your own SSH key and access confirmation; custom domains, backups and the end of managed upkeep need attention.