Documentation

menu
HostingIntroductionBranch HostingPull-request DeploymentsSecretsPersistenceDebuggingMultiple ServersCustom DomainsRaw DomainsExample: Typescript & GoExample: JitsiExample: RSS BridgeExample: Tiny Tiny RSSExample: SearxActionsInstalling Nixyaml configNix FlakesWhat Garnix CI doesIncremental BuildsUsing Private InputsCachingEnterprise installationsGitHub Actions IntegrationBadgesFOD ChecksGarnModulesIntroductionNodejsHaskellRustPostgreSQLUserDependenciesHow modules workopen source
HostingIntroductionBranch HostingPull-request DeploymentsSecretsPersistenceDebuggingMultiple ServersCustom DomainsRaw DomainsExample: Typescript & GoExample: JitsiExample: RSS BridgeExample: Tiny Tiny RSSExample: SearxActionsInstalling Nixyaml configNix FlakesWhat Garnix CI doesIncremental BuildsUsing Private InputsCachingEnterprise installationsGitHub Actions IntegrationBadgesFOD ChecksGarnModulesIntroductionNodejsHaskellRustPostgreSQLUserDependenciesHow modules workopen source

Debugging failed buildsshare

One advantage of garnix's approach to deployments is that failed deployments can be debugged at leisure, because they cause no downtime.

If NixOS activation fails, garnix will keep the failed server around until the next deployment. This allows you to ssh in and understand better what happened.

Blog
Docs
Pricing
Discord
Matrix
Report an issue
Privacy Policy
Imprint