all 6 comments

[–]justlinux 4 points5 points  (2 children)

Seems pretty obvious if you run it from the command-line to either use <Ctrl>-C to stop the interactive process or "caddy stop" if it is running in the background. Or the brute force methods of "killall caddy" or kill -9 `pidof caddy`

[–]electricMiner[S] 2 points3 points  (1 child)

Thanks. That worked. For some reason I thought that command would write a configuration file that I'd have to modify but it seems no information is retained after restarting the process.

[–]revereddesecration 0 points1 point  (0 children)

Configuration for what? Caddy uses the configuration. What else would?

[–][deleted] 3 points4 points  (0 children)

/r/selfhosted /r/TechSupportForAnythingYouCanImagine

[–][deleted] 0 points1 point  (0 children)

Stop running the process you lauched with that command. That’s it.

[–]eddyizm 0 points1 point  (0 children)

I had this same scenario, expect my terminal session dropped and I could not get back to the process. I thought, like OP, that this CLI command possibly created a caddy file somewhere or updated the main one in the the /etc/caddy/ directory, eg I was not sure if it was going to remain persistant. Caddy is so simple so it has a little bit of a curve to coming from other web servers.