GuidesOnly show guides for your app
GuidesGuidesThe capstone — combine Schedules, Git deploy, webhooks and templates into automations that run your server for you, from nightly backup-and-restart to deploy-on-push with a build step to a Discord ping when a backup completes.
You've met the pieces one at a time — Schedules, Git deploy, webhooks, templates. This is where they stop being separate features and start being a server that looks after itself. Every recipe below is built only from things the panel actually does; each names the plan it needs. Copy the ones that fit, and hands-off becomes the default.
| At a glance | |
|---|---|
| You need | Any Falix server; a linked Git repo for the deploy recipes |
| Plan | Any — free runs the Command schedule task while online; richer tasks and offline runs are premium (flagged per recipe) |
| Time | Ten minutes per recipe |
| Block | What it contributes | Guide |
|---|---|---|
| Schedules | A trigger (clock or event) + ordered tasks | Schedules |
| Git deploy | Pull code, run post-deploy build commands, auto-deploy on push | Git quickstart |
| Webhooks | Notify Discord / any HTTPS endpoint when things happen | below |
| Templates | Lay down starter files in one click | One-click templates |
Two things to hold in mind throughout: schedule tasks run top to bottom in the order you list them, and the fastest way to test any schedule is its Run now button — fire it by hand, watch the console, then check the schedule's Logs.
A fresh restart clears memory creep; a nightly backup means you always have yesterday to fall back to. Do both in one schedule.
say Nightly maintenance in 60s to warn players.Because tasks run in order, the backup finishes before the restart begins. Plan note: the Backup and Power-action tasks are premium; on free, the Command task runs while the server is online.
Push to your repo and let the server pull, build, and restart itself.
npm run build, tsc, or go build -o app — and set the post-deploy action to Restart.Now: push → Falix pulls the branch into /home/container → your build runs → the server restarts on the new code. Nothing to click. See Auto-deploy and Build steps.
🎯 Good to know: Linked a public repo by URL instead of connecting an account? Those don't get push webhooks — but they support scheduled pulls every 1 / 6 / 12 / 24 hours, plus manual deploys. Same hands-off result, on a timer instead of on push.
You don't want to watch the Logs to know a backup ran — you want to be told, especially when one fails.
Now a completed backup pings your channel, and — more importantly — a failed one does too, so a quietly broken backup can't hide from you.
💡 Tip: The webhook URL must be HTTPS. Of the four events, task failed is the one most people actually want — it's how you hear about the backup or restart that broke without babysitting the panel. Separately, Settings → General has a Discord webhook for crash notifications; the two work well together.
Keep the server up even when it falls over at 3 AM.
A crash is now followed immediately by a boot instead of hours of downtime. This one needs a power task and a just-stopped server, so it's premium in practice; premium also has dedicated crash-detection settings on the Settings page. Pair it with Recipe 1 and the server mostly runs itself. See Keeping apps online.
Servers accumulate cruft — temp files, old logs, stale data. Sweep it on a timer.
Keep the paths specific — Delete files does exactly what it says, with no undo — and take a backup before trusting a destructive schedule.
| Recipe | Trigger | Tasks | Plan |
|---|---|---|---|
| Nightly backup + restart | Daily | Command → Backup → Restart | Backup/Power = premium |
| Deploy on push + build | Git (auto-deploy) | post-deploy build + restart | Any |
| Backup-completed → Discord | Daily + webhook | Backup + notify | Notify = any; Backup task = premium |
| Auto-restart on crash | Event: crashed | Power → Start | Premium |
| Housekeeping | Daily / Interval | Command or Delete files | Command = any |
A one-click template writes starter files onto a server (overwriting only same-named files) — a great starting point that pairs naturally with these recipes: deploy a template to scaffold the project, then wire up Git auto-deploy (Recipe 2) for everything after. See One-click templates.