Darkhttpd - Revision history

Sertonix: prefix commands with $ or #

2023-09-26T07:36:56Z

prefix commands with $ or #

← Older revision		Revision as of 07:36, 26 September 2023
Line 6:		Line 6:
	= Install =		= Install =

	{{Cmd\|apk add darkhttpd}}		{{Cmd\|# apk add darkhttpd}}

	= Configure =		= Configure =
Line 32:		Line 32:
	Change any of these values as you see fit, but it's a good idea to backup the file before making changes.		Change any of these values as you see fit, but it's a good idea to backup the file before making changes.

	For a full list of available options, run: {{Cmd\|darkhttpd}}		For a full list of available options, run: {{Cmd\|$ darkhttpd}}

	and amend the <code>command_args</code> line as you see fit.		and amend the <code>command_args</code> line as you see fit.
Line 55:		Line 55:
	Create a test page under the server root, by default {{Path\|/var/www/localhost/htdocs}}		Create a test page under the server root, by default {{Path\|/var/www/localhost/htdocs}}

	{{Cmd\|echo "this is a test page" > /var/www/localhost/htdocs/index.html}}		{{Cmd\|# echo "this is a test page" > /var/www/localhost/htdocs/index.html}}

	{{Note\| You don't have to create a test page; in a working environment darkhttpd will generate a directory listing if no index page is found.}}		{{Note\| You don't have to create a test page; in a working environment darkhttpd will generate a directory listing if no index page is found.}}

	Start the daemon: {{Cmd\|rc-service darkhttpd start}}		Start the daemon: {{Cmd\|# rc-service darkhttpd start}}

	Output should be something like this:		Output should be something like this:
Line 72:		Line 72:
	Now point a browser to your darkhttpd server and you should get the index page, or a directory listing if you didn't create an index page.		Now point a browser to your darkhttpd server and you should get the index page, or a directory listing if you didn't create an index page.

	Check the logfile: {{Cmd\|tail /var/log/darkhttpd/access.log}}		Check the logfile: {{Cmd\|$ tail /var/log/darkhttpd/access.log}}

	== Controlling darkhttpd status ==		== Controlling darkhttpd status ==

	Stop, start and restart the daemon in the usual fashion:		Stop, start and restart the daemon in the usual fashion:
	{{Cmd\|rc-service darkhttpd start}}		{{Cmd\|# rc-service darkhttpd start}}

	{{Cmd\|rc-service darkhttpd stop}}		{{Cmd\|# rc-service darkhttpd stop}}

	{{Cmd\|rc-service darkhttpd restart}}		{{Cmd\|# rc-service darkhttpd restart}}

	== Auto-start darkhttpd at boot ==		== Auto-start darkhttpd at boot ==

	To add the daemon to the default runlevel so it auto-starts at boot, do: {{Cmd\|rc-update add darkhttpd}}		To add the daemon to the default runlevel so it auto-starts at boot, do: {{Cmd\|# rc-update add darkhttpd}}

	= Troubleshooting =		= Troubleshooting =
Line 100:		Line 100:
	* If the daemon will not start, ensure you haven't made a syntax error in the init script.		* If the daemon will not start, ensure you haven't made a syntax error in the init script.

	* Ensure the daemon is running with {{Cmd\|rc-status}}		* Ensure the daemon is running with {{Cmd\|$ rc-status}}

	* Make use of the logs to check it is receiving requests. To do this, run {{Cmd\|tail -f /var/log/darkhttpd/access.log}} and then send requests to the web server. If darkhttpd is receiving the requests, lines will be logged. If you don't see these lines, perhaps a firewall rule is blocking access to the server or there is a routing issue somewhere?		* Make use of the logs to check it is receiving requests. To do this, run {{Cmd\|$ tail -f /var/log/darkhttpd/access.log}} and then send requests to the web server. If darkhttpd is receiving the requests, lines will be logged. If you don't see these lines, perhaps a firewall rule is blocking access to the server or there is a routing issue somewhere?
	Use {{key\|Ctrl}}+{{key\|C}} to exit back to the prompt when finished testing.		Use {{key\|Ctrl}}+{{key\|C}} to exit back to the prompt when finished testing.

Sertonix: fix syntax error in init script

2023-09-26T07:30:02Z

fix syntax error in init script

← Older revision		Revision as of 07:30, 26 September 2023
Line 16:		Line 16:
	There's no configuration file for {{Pkg\|darkhttpd}}, everything is controlled from the command line or in our case the OpenRC init file, which is stored in {{Path\|/etc/init.d/darkhttpd}} and by default looks like this:		There's no configuration file for {{Pkg\|darkhttpd}}, everything is controlled from the command line or in our case the OpenRC init file, which is stored in {{Path\|/etc/init.d/darkhttpd}} and by default looks like this:

	{{cat\|/etc/init.d/darkhttpd\|<nowiki>#! /sbin/runscript		{{cat\|/etc/init.d/darkhttpd\|<nowiki>#!/sbin/runscript

	description="darkhttpd web server"		description="darkhttpd web server"
Line 37:		Line 37:
	For example, you might wish to serve files from {{Path\|/var/files}} instead, so you can edit the {{Path\|/etc/init.d/darkhttpd}} file with an editor of your choice (vi, nano, vim or whatever) and make it like so:		For example, you might wish to serve files from {{Path\|/var/files}} instead, so you can edit the {{Path\|/etc/init.d/darkhttpd}} file with an editor of your choice (vi, nano, vim or whatever) and make it like so:

	{{cat\|/etc/init.d/darkhttpd\|<nowiki>#! /sbin/runscript		{{cat\|/etc/init.d/darkhttpd\|<nowiki>#!/sbin/runscript

	description="darkhttpd web server"		description="darkhttpd web server"

Sertonix: fix name casing

2023-09-26T07:29:12Z

fix name casing

← Older revision		Revision as of 07:29, 26 September 2023
Line 1:		Line 1:
			{{DISPLAYTITLE:darkhttpd}}
			darkhttpd is a simple, fast HTTP 1.1 web server for static content. It does not support PHP or CGI etc but is designed to serve static content, which it does very well. darkhttpd would be an excellent alternative to [[Lighttpd]] for [[How to setup a Alpine Linux mirror\|running an Alpine mirror]]

	Darkhttpd is a simple, fast HTTP 1.1 web server for static content. It does not support PHP or CGI etc but is designed to serve static content, which it does very well. Darkhttpd would be an excellent alternative to [[Lighttpd]] for [[How to setup a Alpine Linux mirror\|running an Alpine mirror]]

	For a full list of features see the [https://unix4lyfe.org/darkhttpd/ darkhttpd homepage]		For a full list of features see the [https://unix4lyfe.org/darkhttpd/ darkhttpd homepage]

Sertonix: /* man darkhttpd */ changed darkhttpd help to see also

2023-09-26T07:26:58Z

man darkhttpd: changed darkhttpd help to see also

@@ Line 105: / Line 105: @@
 Use {{key|Ctrl}}+{{key|C}} to exit back to the prompt when finished testing.
-= man darkhttpd =
+= See also =
-<pre>
+* <code>darkhttpd --help</code>
 [[Category:Web Server]]

Sertonix: use cat & key template

2023-09-26T07:18:57Z

use cat & key template

← Older revision		Revision as of 07:18, 26 September 2023
Line 16:		Line 16:
	There's no configuration file for {{Pkg\|darkhttpd}}, everything is controlled from the command line or in our case the OpenRC init file, which is stored in {{Path\|/etc/init.d/darkhttpd}} and by default looks like this:		There's no configuration file for {{Pkg\|darkhttpd}}, everything is controlled from the command line or in our case the OpenRC init file, which is stored in {{Path\|/etc/init.d/darkhttpd}} and by default looks like this:

	<~~pre~~>		{{cat\|/etc/init.d/darkhttpd\|<nowiki>#! /sbin/runscript
	#! /sbin/runscript

	description="darkhttpd web server"		description="darkhttpd web server"
Line 25:		Line 24:
	pidfile=""		pidfile=""
	stopsig="SIGTERM"		stopsig="SIGTERM"
	</~~pre~~>		</nowiki>}}

	So by default we will serve pages from {{Path\|/var/www/localhost/htdocs}} and darkhttpd will run as a background daemon, [https://en.wikipedia.org/wiki/Chroot chrooted] to {{Path\|/var/www/localhost/htdocs}} with a user of <code>darkhttpd</code> and group of <code>www-data</code>.		So by default we will serve pages from {{Path\|/var/www/localhost/htdocs}} and darkhttpd will run as a background daemon, [https://en.wikipedia.org/wiki/Chroot chrooted] to {{Path\|/var/www/localhost/htdocs}} with a user of <code>darkhttpd</code> and group of <code>www-data</code>.
Line 38:		Line 37:
	For example, you might wish to serve files from {{Path\|/var/files}} instead, so you can edit the {{Path\|/etc/init.d/darkhttpd}} file with an editor of your choice (vi, nano, vim or whatever) and make it like so:		For example, you might wish to serve files from {{Path\|/var/files}} instead, so you can edit the {{Path\|/etc/init.d/darkhttpd}} file with an editor of your choice (vi, nano, vim or whatever) and make it like so:

	<~~pre~~>		{{cat\|/etc/init.d/darkhttpd\|<nowiki>#! /sbin/runscript
	#! /sbin/runscript

	description="darkhttpd web server"		description="darkhttpd web server"
Line 47:		Line 45:
	pidfile=""		pidfile=""
	stopsig="SIGTERM"		stopsig="SIGTERM"
	</~~pre~~>		</nowiki>}}

	= Use =		= Use =
Line 105:		Line 103:

	* Make use of the logs to check it is receiving requests. To do this, run {{Cmd\|tail -f /var/log/darkhttpd/access.log}} and then send requests to the web server. If darkhttpd is receiving the requests, lines will be logged. If you don't see these lines, perhaps a firewall rule is blocking access to the server or there is a routing issue somewhere?		* Make use of the logs to check it is receiving requests. To do this, run {{Cmd\|tail -f /var/log/darkhttpd/access.log}} and then send requests to the web server. If darkhttpd is receiving the requests, lines will be logged. If you don't see these lines, perhaps a firewall rule is blocking access to the server or there is a routing issue somewhere?
	Use 'Ctrl C' to exit back to the prompt when finished testing.		Use {{key\|Ctrl}}+{{key\|C}} to exit back to the prompt when finished testing.

	= man darkhttpd =		= man darkhttpd =

Zcrayfish: Changed a hyperlink to https

2023-07-26T13:04:34Z

Changed a hyperlink to https

← Older revision		Revision as of 13:04, 26 July 2023
Line 2:		Line 2:
	Darkhttpd is a simple, fast HTTP 1.1 web server for static content. It does not support PHP or CGI etc but is designed to serve static content, which it does very well. Darkhttpd would be an excellent alternative to [[Lighttpd]] for [[How to setup a Alpine Linux mirror\|running an Alpine mirror]]		Darkhttpd is a simple, fast HTTP 1.1 web server for static content. It does not support PHP or CGI etc but is designed to serve static content, which it does very well. Darkhttpd would be an excellent alternative to [[Lighttpd]] for [[How to setup a Alpine Linux mirror\|running an Alpine mirror]]

	For a full list of features see the [~~http~~://unix4lyfe.org/darkhttpd/ darkhttpd homepage]		For a full list of features see the [https://unix4lyfe.org/darkhttpd/ darkhttpd homepage]

	= Install =		= Install =

Arrogance at 06:37, 30 May 2023

2023-05-30T06:37:31Z

← Older revision		Revision as of 06:37, 30 May 2023
Line 174:		Line 174:


	[[Category:Server]]		[[Category:Web Server]]

Ginjachris: /* man darkhttpd */ updated

2017-03-29T11:33:56Z

man darkhttpd: updated

← Older revision		Revision as of 11:33, 29 March 2017
Line 109:		Line 109:
	= man darkhttpd =		= man darkhttpd =
	<pre>		<pre>
	~~v-alpine-server:~# darkhttpd~~		darkhttpd/1.12, copyright (c) 2003-2016 Emil Mikulic.
	darkhttpd/1.9, copyright (c) 2003-~~2013~~ Emil Mikulic.		usage: darkhttpd /path/to/wwwroot [flags]
	usage: darkhttpd /path/to/wwwroot [flags]

	flags: --port number (default: 8080, or 80 if running as root)		flags: --port number (default: 8080, or 80 if running as root)
	Specifies which port to listen on for connections.		Specifies which port to listen on for connections.
			Pass 0 to let the system choose any free port for you.

	--addr ip (default: all)		--addr ip (default: all)
	If multiple interfaces are present, specifies		If multiple interfaces are present, specifies
	which one to bind the listening port to.		which one to bind the listening port to.

	--maxconn number (default: system maximum)		--maxconn number (default: system maximum)
	Specifies how many concurrent connections to accept.		Specifies how many concurrent connections to accept.

	--log filename (default: stdout)		--log filename (default: stdout)
	Specifies which file to append the request log to.		Specifies which file to append the request log to.

	--chroot (default: don't chroot)		--chroot (default: don't chroot)
	Locks server into wwwroot directory for added security.		Locks server into wwwroot directory for added security.

	--daemon (default: don't daemonize)		--daemon (default: don't daemonize)
	Detach from the controlling terminal and run in the background.		Detach from the controlling terminal and run in the background.

	--index filename (default: index.html)		--index filename (default: index.html)
	Default file to serve when a directory is requested.		Default file to serve when a directory is requested.

	--~~mimetypes filename (optional)~~		--no-listing
	~~Parses specified file for extension-MIME associations~~.		Do not serve listing if directory is requested.

	--~~uid uid/uname, --gid gid/gname~~ (~~default: don't privdrop~~)		--mimetypes filename (optional)
	~~Drops privileges to given uid:gid after initialization~~.		Parses specified file for extension-MIME associations.

	--~~pidfile filename~~ (default: ~~no pidfile~~)		--default-mimetype string (optional, default: application/octet-stream)
	~~Write PID to the specified file. Note that if you~~ are		Files with unknown extensions are served as this mimetype.
	~~using --chroot, then the pidfile must be relative to,~~
	~~and inside the wwwroot~~.

	--no-~~keepalive~~		--uid uid/uname, --gid gid/gname (default: don't privdrop)
	~~Disables HTTP Keep-Alive functionality~~.		Drops privileges to given uid:gid after initialization.

	--~~forward host url~~ (default: ~~don't forward~~)		--pidfile filename (default: no pidfile)
	~~Web forward (301 redirect).~~		Write PID to the specified file. Note that if you are
	~~Requests~~ to the ~~host~~ are ~~redirected to~~ the ~~corresponding url.~~		using --chroot, then the pidfile must be relative to,
	~~The option may~~ be ~~specified multiple times~~, ~~in which case~~		and inside the wwwroot.
	the ~~host is matched in order of appearance~~.

	--no-server-id		--no-keepalive
	Don't identify the server type in headers		Disables HTTP Keep-Alive functionality.
	or directory listings.
			--forward host url (default: don't forward)
			Web forward (301 redirect).
			Requests to the host are redirected to the corresponding url.
			The option may be specified multiple times, in which case
			the host is matched in order of appearance.

			--forward-all url (default: don't forward)
			Web forward (301 redirect).
			All requests are redirected to the corresponding url.

			--no-server-id
			Don't identify the server type in headers
			or directory listings.

			--ipv6
			Listen on IPv6 address.
	</pre>		</pre>


	[[Category:Server]]		[[Category:Server]]

Ginjachris: replaced yet more 'hdoc' with 'htdoc' :¬S

2015-05-06T17:45:04Z

replaced yet more 'hdoc' with 'htdoc' :¬S

← Older revision		Revision as of 17:45, 6 May 2015
Line 51:		Line 51:
	= Use =		= Use =

	Filesharing is made easy; simply add your files under the server root, by default {{Path\|/var/www/localhost/~~hdocs~~}}		Filesharing is made easy; simply add your files under the server root, by default {{Path\|/var/www/localhost/htdocs}}

	== Test ==		== Test ==

	Create a test page under the server root, by default {{Path\|/var/www/localhost/~~hdocs~~}}		Create a test page under the server root, by default {{Path\|/var/www/localhost/htdocs}}

	{{Cmd\|echo "this is a test page" > /var/www/localhost/htdocs/index.html}}		{{Cmd\|echo "this is a test page" > /var/www/localhost/htdocs/index.html}}

Ginjachris: /* Use */

2015-05-06T09:05:07Z

Use

← Older revision		Revision as of 09:05, 6 May 2015
Line 51:		Line 51:
	= Use =		= Use =

	Filesharing is made easy; simply add your files under the server root, by default {{Path\|/var/www/localhost/hdocs}}		Filesharing is made easy; simply add your files under the server root, by default {{Path\|/var/www/localhost/hdocs}}


	== Test ==		== Test ==