caddy/dist/init
Richard Bowden 25a596a98f freebsd init: added new functionality and enabled better logging (#1740)
* uses more of the builtin functionality for starting and stopping of the process by using command and command_args along with procname
* removed -f from daemon as this was hiding error message that were sent to stdout on startup, now writing stdout to the logfile directly

for example, this was being hidden:

“Activating privacy features.. [www.domain.com] failed to get certificate: Error presenting token: Could not find the start of authority”

it now shows up in the log

* aded “caddy_env” to allow the setting of environment variables that caddy might need, for example when setting creds for “DNS Challenge”

* added a check to ensure caddy_config_path file exists
2017-07-10 16:20:30 -06:00
..
freebsd freebsd init: added new functionality and enabled better logging (#1740) 2017-07-10 16:20:30 -06:00
linux-systemd Configure systemd to send SIGQUIT on stop (#1702) 2017-06-24 11:15:13 -07:00
linux-sysvinit Update Initscripts 2017-06-04 12:18:33 +08:00
linux-upstart Make CADDYPATH equal across init scripts 2017-03-28 22:04:19 +01:00
mac-launchd update macOS launchd example (#1600) 2017-04-26 13:44:32 -06:00
README.md Post init script guidelines 2016-12-30 11:56:37 -07:00

Init/Service Scripts

This folder contains init/service scripts for using Caddy on various Linux and BSD distributions. They are created and maintained by the community.

Getting Help

Different scripts have different maintainers; please consult the comments in the file and any README for assistance setting it up. Do not open an issue on the Caddy project about these scripts; instead, to ask a question or suggest a change, please contact the maintainer of the script directly.

Disclaimer

The files contained herein are not officially supported by the Caddy project author and/or contributors, and as such, the files are not endorsed by the same. The Caddy project author and its contributors are not responsible for the function or malfunction of these scripts/files, or any unintended consequences to your system or website in attempting to set up Caddy. Users are expected to know how to administer their system, and these files should be considered as only a guide or suggestion for using Caddy in certain environments.

Guidelines

The files distributed here should adhere to these principles where relevant (adjust accordingly for each system/platform):

  • Don't run as root.
  • Create a no-shell default user to run it.
  • Raise file descriptor limits.
  • Don't restart endlessly; if Caddy fails to start, there's a reason -- fix it, don't hammer it.
  • Allow Caddy to re-use the same, persistent folder for storage.
  • Stay as simple and minimal as possible.
  • Be idempotent.
  • Use comments to explain unexpected or unusual lines/patterns.
  • Be secure by default.

Thank you for using Caddy! May it serve you well.