[dewey]

I believe they are talking about the Dokku commands that are needed to set up a new Dokku app.

For example for a static site that would be the following:

    dokku apps:create dewey.at
    dokku domains:set dewey.at dewey.at www.dewey.at
    dokku letsencrypt:enable dewey.at

That's also one of my wishes to get improved, currently I just have a long text file where I store them so that if I move servers I can just re-run them if needed.

[mdasen]

Could you put them in a .sh file and then just run `sh setup_dewey.sh`? Maybe put `&&` between them so that if one fails, it won't keep running through the script?

[chuckadams]

> Maybe put `&&` between them so that if one fails, it won't keep running through the script?

Or just add `set -o errexit` at the top of the script. Or use make.

[dewey]

Yep, in theory I think that should work nicely. So the recovery procedure after a server died would be to restore the dokku data directory from backup and then re-run all the commands. I haven't tested that but I think that should do the job.

Right now I keep the list of commands more as a reference to look up things like how I mounted a volume or my naming scheme for data directories.

[oezi]

Exactely, I was really surprised that dokku isn't all based on storing these commands in a config/script which gets executed every time you change something.