InstallFromSource » History » Revision 17
Revision 16 (gstrauss, 2017-01-23 11:58) → Revision 17/35 (gstrauss, 2017-01-24 23:34)
h1. InstallFromSource h2. Get the source You can either use a release from "www.lighttpd.net/download"://www.lighttpd.net/download or compile from git: * Using a release/snapshot: Extract the tar ball and enter the new directory: <pre> tar -xf lighttpd-1.4.XXX.tar.gz cd lighttpd-1.4.XXX </pre> * git (you will need autoconf and automake for this): First time: <pre> git clone https://git.lighttpd.net/lighttpd/lighttpd1.4.git cd lighttpd1.4 ./autogen.sh </pre> Next time in @lighttpd1.4/@: <pre> git pull ./autogen.sh </pre> * svn: instead of git you can also use svn, the initial checkout is created with: <pre> svn checkout https://github.com/lighttpd/lighttpd1.4/trunk lighttpd1.4 </pre> And updates will be fetched with the usual: <pre> svn update </pre> Also see [[DevelGit]] and [[Devel]]. h2. Install dependencies Depending on which features you want, you need other libraries; you will want at least libpcre and zlib, for more see [[OptionalLibraries]]. On most systems you need to install the development version of the library packages, the library itself won't be enough! On debian you can also use apt-get to install all build dependencies: <pre> apt-get build-dep lighttpd </pre> h2. Configure Now you have to use the @./configure@ script - there is a help option for it: <pre> ./configure --help </pre> Don't forget to set the @--prefix@ if you don't want to install in /usr/local. h2. Build If the configure step was successful, you can now build it: <pre> make </pre> h2. Install After a successful build you may install the package. This is not needed, but you will have to give lighttpd the correct location of the modules if you don't (see ./lighttpd -h). As you hopefully didn't use root to build the package, you probably have now to get root access: <pre> su make install </pre> h2. signals lighttpd responds to the following signals: * SIGTERM - shut down immediately (terminate existing connections, then exit) * SIGINT - shut down gracefully (serve (finish serving existing connections, then connections and exit) * SIGUSR1 SIGTERM - reload gracefully (serve shut down immediately (terminate existing connections, then reload config) connections and exit) * SIGHUP - re-open log files (NOTE: does not reload lighttpd configuration) (Note: SIGUSR1 behavior is available in lighttpd 1.4.46 and later) h2. graceful restart https://blog.lighttpd.net/articles/2005/09/02/graceful-restart/ The current recommended way to reload lighttpd config is to gracefully stop and then to restart lighttpd. With lighttpd 1.4.46 and later, SIGUSR1 is the recommended method to gracefully handle configuration reloads and log rotation, though a graceful stop and then restart of lighttpd is still required for lighttpd configurations which chroot. h2. initscripts Depending on the operating system and distribution brand, there are many ways to set up lighttpd to run as a daemon when the system starts up, and to send signals to lighttpd for start/stop/restart/etc. Rather than attempting to maintain scripts for an unknown number of distros, here are links to a few, which can be used as examples. * Arch: https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/lighttpd * Debian: https://anonscm.debian.org/cgit/pkg-lighttpd/lighttpd.git/tree/debian * Fedora: http://pkgs.fedoraproject.org/cgit/rpms/lighttpd.git/tree/ * Gentoo: https://gitweb.gentoo.org/repo/gentoo.git/tree/www-servers/lighttpd/files * openSUSE: https://build.opensuse.org/package/show/server:http/lighttpd h2. Supervise As an alternative to init scripts you can setup a "supervised" lighttpd with daemontools or runit, see [[LighttpdUnderSupervise]]