InstallFromSource » History » Revision 25
« Previous |
| Next »
gstrauss, 2021-07-17 04:29
- Table of contents
View source code in the lighttpd 1.4 git repository
There are multiple options to obtain a lighttpd source tree. git is recommended.
- git: (recommended)
$ git clone https://git.lighttpd.net/lighttpd/lighttpd1.4.git
$ git clone git+ssh://firstname.lastname@example.org/lighttpd/lighttpd1.4.git
# initial checkout git clone https://git.lighttpd.net/lighttpd/lighttpd1.4.git cd lighttpd1.4 # subsequent updates (to obtain latest source) #cd lighttpd1.4 git pull
- svn: (alternative to git)
# initial checkout svn checkout https://github.com/lighttpd/lighttpd1.4/trunk lighttpd1.4 cd lighttpd1.4 # subsequent updates (to obtain latest source) #cd lighttpd1.4 svn update
- source release/snapshot
# download and extract tarball latest=$(curl -s https://download.lighttpd.net/lighttpd/releases-1.4.x/latest.txt) curl -o $latest.tar.xz https://download.lighttpd.net/lighttpd/releases-1.4.x/$latest.tar.xz tar -xJf $latest.tar.xz cd $latest
lighttpd supports multiple build frameworks: automake, cmake, meson, and scons.Ensure you have installed the latest development tools and packages available, e.g. for automake:
- pcre-devel / libpcre3-dev
Further details can be found in lighttpd INSTALL (Please read)
Depending on which features you want, other development libraries may be needed: OptionalLibraries
On most systems you need to install the development version of the library packages; the library itself will not be enough!
On debian you can also use apt-get to install all lighttpd build dependencies:
apt-get build-dep lighttpd
build commands (examples)¶
#cd lighttpd1.4 ./autogen.sh ./configure -C --prefix=/usr/local # ./configure --help for additional options make -j 4 make check #sudo make install
#cd lighttpd1.4 cmake -DCMAKE_INSTALL_PREFIX=/usr/local -Wno-dev . make -j 4 make test #sudo make install
#cd lighttpd1.4 meson setup --prefix /usr/local build cd build meson compile meson test #sudo meson install
#cd lighttpd1.4 scons -j 4 build_static=1 build_dynamic=0 prefix=/usr/local #sudo scons -j 4 build_static=1 build_dynamic=0 prefix=/usr/local install
Examples commands for more fully-featured builds might reference lighttpd scripts/ci-build.sh
Also, there are more options for running unit tests
./configure --build=arm-linux --host=x86_64-pc-linux-gnu --prefix=/usr/local --disable-static --enable-shared ...
distro packaging (external examples)¶
running lighttpd from build tree¶
lighttpd can be run from the build tree, without needing to install it. This is useful for testing. In the shell in which you built lighttpd, chdir to the top of the source tree (if not already there).
Create a basic lighttpd.conf to listen on localhost port 8080 and serve files from
/tmp (not recommended for production use!):
server.document-root = "/tmp" server.bind = "127.0.0.1" server.port = 8080 mimetype.assign = (".txt" => "text/plain", ".html" => "text/html" )
Create a simple file to serve:
echo "Hello World!" > /tmp/hello.txt
Run lighttpd in the foreground:
src/lighttpd -D -f lighttpd.conf -m $PWD/src/.libs
In a different shell:
In the shell running lighttpd, press press
Ctrl-Cto cause lighttpd to exit.
lighttpd responds to the following signals:
- SIGTERM - shut down immediately (terminate existing connections, then exit)
- SIGINT - shut down gracefully (serve existing connections, then exit)
- SIGUSR1 - reload gracefully (serve existing connections, then reload config)
- SIGHUP - re-open log files (NOTE: does not reload lighttpd configuration)
(Note: SIGUSR1 behavior is available in lighttpd 1.4.46 and later)
With lighttpd 1.4.46 and later, SIGUSR1 is the recommended method to gracefully handle configuration reloads, though a graceful stop and then restart of lighttpd is still required for lighttpd configurations which chroot.
With lighttpd 1.4.56 and later, graceful restart can have a time limit applied to existing active connections before the server reloads the config: (server.feature-flags)
server.feature-flags = ( "server.graceful-shutdown-timeout" => 5 )
In some configurations, lighttpd can immediately restart, while a forked copy of the server continued to serve existing connections (YMMV):
server.feature-flags = ( "server.graceful-shutdown-timeout" => 5, "server.graceful-restart-bg" => "enable" )
server.systemd-socket-activation = "enable"
archive: older article from 2005 talks about graceful restart using SIGINT: https://blog.lighttpd.net/articles/2005/09/02/graceful-restart/
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://salsa.debian.org/debian/lighttpd
- 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
- OpenWRT: https://github.com/openwrt/packages/tree/master/net/lighttpd
sample systemd unit script lighttpd.service
As an alternative to init scripts you can setup a "supervised" lighttpd with daemontools or runit, see LighttpdUnderSupervise
Updated by gstrauss over 1 year ago · 25 revisions