Lighttpd - Revision history

Yorick at 10:12, 16 July 2024

2024-07-16T10:12:05Z

← Older revision		Revision as of 10:12, 16 July 2024
Line 2:		Line 2:
	Its name is a portmanteau of "light" and "httpd": [https://www.lighttpd.net/ lighttpd] is a simple, standards-compliant, secure, and flexible web server.		Its name is a portmanteau of "light" and "httpd": [https://www.lighttpd.net/ lighttpd] is a simple, standards-compliant, secure, and flexible web server.

	'''lighttpd is a powerful server, made long ago to handle upwards of 10,000 connections in parallel on one server'''. It was used in wikipedia server a ~~log~~ time ago and also some google services.		'''lighttpd is a powerful server, made long ago to handle upwards of 10,000 connections in parallel on one server'''. It was used in wikipedia server a long time ago and also some google services.

	{{Note\|As for minimal sites and quick-start purposes, it is recommended due to its easy configuration process and excellent performance without much configuration. Check https://w3techs.com/technologies/details/ws-lighttpd and note that it is used in high traffic and important sites like postgresql.org}}		{{Note\|As for minimal sites and quick-start purposes, it is recommended due to its easy configuration process and excellent performance without much configuration. Check https://w3techs.com/technologies/details/ws-lighttpd and note that it is used in high traffic and important sites like postgresql.org}}

Zcrayfish: /* Testing Lighttpd */ Attempt, badly, to correct spelling and grammar mistakes... ic template usage.

2024-01-09T01:11:35Z

Testing Lighttpd: Attempt, badly, to correct spelling and grammar mistakes... ic template usage.

← Older revision		Revision as of 01:11, 9 January 2024
Line 55:		Line 55:
	This section is assuming that lighttpd is running. If you now launch a web browser from a remote system and point it to your web server, you will see a page that says "404 - Not Found". Well, at the moment there is no content available but the server is up and running.		This section is assuming that lighttpd is running. If you now launch a web browser from a remote system and point it to your web server, you will see a page that says "404 - Not Found". Well, at the moment there is no content available but the server is up and running.

	Let's add a simple test page to get rid of the "404 - Not Found page".		Let's add a simple test page to get rid of the "404 - Not Found page":

	{{Cmd\|echo '<!DOCTYPE html><html><head><title>✔️</title><meta charset="utf-8"></head><body>Lighttpd is running!</body></html>' > /var/www/localhost/htdocs/index.html}}		{{Cmd\|echo '<!DOCTYPE html><html><head><title>✔️</title><meta charset="utf-8"></head><body>Lighttpd is running!</body></html>' > /var/www/localhost/htdocs/index.html}}

	'''For testing open a browser and go to ~~<code>~~<nowiki>http://127.0.0.1/</nowiki>~~</code>~~ and you ~~will~~ see "Lighttpd is running~~...~~"'''. Note ~~that we used~~ "127.0.0.1" ~~if you~~ are ~~using alpine as~~ the ~~only machine for all as your main desktop/pc/~~machine.		'''For testing open a browser and go to {{ic\|<nowiki>http://127.0.0.1/</nowiki>}} and you should see "Lighttpd is running!"'''. Note the example usage of "127.0.0.1" indicating that the lighttpd server and the web browser are running on the same machine.

	If you are using alpine ~~remotelly as web server and just install it the package~~, '''open a browser in your ~~desktop~~ machine, and go to ~~<code><nowiki>~~http://<webserveripaddres>/~~</nowiki></code>~~. The "webserveripaddres" ~~are~~ the ip address of your ~~setup/~~server machine.		If you are using alpine remotely, '''open a browser on your client machine, and go to {{ic\|http://<webserveripaddres>/}}. The "webserveripaddres" is the IP address of your lighttpd server machine.'''

	== Lighttpd Configuration ==		== Lighttpd Configuration ==

Zcrayfish: /* Install Lighttpd */ Use cmd template. Attempt to correct grammar and spelling errors. Remove extra line breaks and spaces.

2024-01-09T01:06:09Z

Install Lighttpd: Use cmd template. Attempt to correct grammar and spelling errors. Remove extra line breaks and spaces.

← Older revision		Revision as of 01:06, 9 January 2024
Line 42:		Line 42:

	== Install Lighttpd ==		== Install Lighttpd ==
			The installation works out of the box for static pages. After installing you can see webserver in action by putting any file inside the {{Path\|/var/www/localhost/htdocs/}} directory.

	~~The installation works just out of the box for only static pages, just with install you can see webserver in action by putting any file inside the {{Path\|/var/www/localhost/htdocs/}} directory.~~		Per user web files are supported by default in {{Path\|/home/<user>/public_html}} directory by default if we enable it (process are described below in further section "Lighttpd configuration".

	Per user web files are supported by default in {{Path\|/home/<user>/public_html}} directory by default if we enable it (process are described below in further section "Lighttpd configuration".

	{{Pkg\|lighttpd}} is available in the Alpine Linux repositories. To install, simple launch the commands below:		{{Pkg\|lighttpd}} is available in the Alpine Linux repositories. To install, simple launch the commands below:
			{{cmd\|apk add lighttpd
	~~<pre>~~
	~~<nowiki>~~
	apk add lighttpd

	rc-update add lighttpd default		rc-update add lighttpd default
			rc-service lighttpd restart}}
	rc-service lighttpd restart
	~~</nowiki>~~
	~~</pre>~~

	== Testing Lighttpd ==		== Testing Lighttpd ==

CAPSLOCK: Grammatical fix

2023-11-24T15:28:30Z

Grammatical fix

← Older revision		Revision as of 15:28, 24 November 2023
Line 43:		Line 43:
	== Install Lighttpd ==		== Install Lighttpd ==

	The installation works just out of the box for only static pages, just with install you can see webserver in action by ~~put~~ any file inside the {{Path\|/var/www/localhost/htdocs/}} directory.		The installation works just out of the box for only static pages, just with install you can see webserver in action by putting any file inside the {{Path\|/var/www/localhost/htdocs/}} directory.

	Per user web files are supported by default in {{Path\|/home/<user>/public_html}} directory by default if we enable it (process are described below in further section "Lighttpd configuration".		Per user web files are supported by default in {{Path\|/home/<user>/public_html}} directory by default if we enable it (process are described below in further section "Lighttpd configuration".

Zcrayfish: /* Testing Lighttpd */ Changed example HTML document to actually be an HTML document.

2023-08-07T05:24:56Z

Testing Lighttpd: Changed example HTML document to actually be an HTML document.

← Older revision		Revision as of 05:24, 7 August 2023
Line 65:		Line 65:
	Let's add a simple test page to get rid of the "404 - Not Found page".		Let's add a simple test page to get rid of the "404 - Not Found page".

	{{Cmd\|echo "Lighttpd is running~~..."~~ > /var/www/localhost/htdocs/index.html}}		{{Cmd\|echo '<!DOCTYPE html><html><head><title>✔️</title><meta charset="utf-8"></head><body>Lighttpd is running!</body></html>' > /var/www/localhost/htdocs/index.html}}

	'''For testing open a browser and go to <code><nowiki>http://127.0.0.1/</nowiki></code> and you will see "Lighttpd is running..."'''. Note that we used "127.0.0.1" if you are using alpine as the only machine for all as your main desktop/pc/machine.		'''For testing open a browser and go to <code><nowiki>http://127.0.0.1/</nowiki></code> and you will see "Lighttpd is running..."'''. Note that we used "127.0.0.1" if you are using alpine as the only machine for all as your main desktop/pc/machine.

Zcrayfish: Changed a hyperlink to https

2023-07-26T21:46:07Z

Changed a hyperlink to https

← Older revision		Revision as of 21:46, 26 July 2023
Line 1:		Line 1:

	Its name is a portmanteau of "light" and "httpd": [~~http~~://www.lighttpd.net/ lighttpd] is a simple, standards-compliant, secure, and flexible web server.		Its name is a portmanteau of "light" and "httpd": [https://www.lighttpd.net/ lighttpd] is a simple, standards-compliant, secure, and flexible web server.

	'''lighttpd is a powerful server, made long ago to handle upwards of 10,000 connections in parallel on one server'''. It was used in wikipedia server a log time ago and also some google services.		'''lighttpd is a powerful server, made long ago to handle upwards of 10,000 connections in parallel on one server'''. It was used in wikipedia server a log time ago and also some google services.

Arrogance at 06:41, 30 May 2023

2023-05-30T06:41:07Z

← Older revision		Revision as of 06:41, 30 May 2023
Line 111:		Line 111:
	* [[Lighttpd Advanced security]]		* [[Lighttpd Advanced security]]

	~~[[Category:Server]]~~
	[[Category:Web_Server]]		[[Category:Web_Server]]
	[[Category:Development]]		[[Category:Development]]

Mckaygerhard: remove newbie reference to stop the discussion

2022-01-06T14:05:39Z

remove newbie reference to stop the discussion

← Older revision		Revision as of 14:05, 6 January 2022
Line 110:		Line 110:
	* [[Setting_Up_Lighttpd_with_PHP\|Setting Up Lighttpd with PHP]]		* [[Setting_Up_Lighttpd_with_PHP\|Setting Up Lighttpd with PHP]]
	* [[Lighttpd Advanced security]]		* [[Lighttpd Advanced security]]
	* LAMP deploy of the Web Server with PHP, user html_dir and MariaDB: [[Production LAMP system: Lighttpd + PHP + MySQL]]
	* LAMP deploy of the Web Server with PHP 5.6 and MariaDB: [[Production LAMP system: Lighttpd + PHP5 + MySQL]]
	* [[Alpine newbie developer]]

	~~[[Category:Newbie]]~~
	[[Category:Server]]		[[Category:Server]]
	[[Category:Web_Server]]		[[Category:Web_Server]]
	[[Category:Development]]		[[Category:Development]]

Zcrayfish: /* See Also */ Removed wikilinks to non-existent articles.

2021-12-14T19:32:43Z

See Also: Removed wikilinks to non-existent articles.

← Older revision		Revision as of 19:32, 14 December 2021
Line 110:		Line 110:
	* [[Setting_Up_Lighttpd_with_PHP\|Setting Up Lighttpd with PHP]]		* [[Setting_Up_Lighttpd_with_PHP\|Setting Up Lighttpd with PHP]]
	* [[Lighttpd Advanced security]]		* [[Lighttpd Advanced security]]
	* [[Production Lets Encrypt: dehydrated]]
	* LAMP deploy of the Web Server with PHP, user html_dir and MariaDB: [[Production LAMP system: Lighttpd + PHP + MySQL]]		* LAMP deploy of the Web Server with PHP, user html_dir and MariaDB: [[Production LAMP system: Lighttpd + PHP + MySQL]]
	* LAMP deploy of the Web Server with PHP 5.6 and MariaDB: [[Production LAMP system: Lighttpd + PHP5 + MySQL]]		* LAMP deploy of the Web Server with PHP 5.6 and MariaDB: [[Production LAMP system: Lighttpd + PHP5 + MySQL]]
	* [[Alpine newbie developer]]		* [[Alpine newbie developer]]
	* [[Alpine newbie lammers]]

	[[Category:Newbie]]		[[Category:Newbie]]

Gstrauss: lighttpd 1.4.56 and later support HTTP/2; improve English language phrasing

2020-12-22T03:33:28Z

lighttpd 1.4.56 and later support HTTP/2; improve English language phrasing

← Older revision		Revision as of 03:33, 22 December 2020
Line 2:		Line 2:
	Its name is a portmanteau of "light" and "httpd": [http://www.lighttpd.net/ lighttpd] is a simple, standards-compliant, secure, and flexible web server.		Its name is a portmanteau of "light" and "httpd": [http://www.lighttpd.net/ lighttpd] is a simple, standards-compliant, secure, and flexible web server.

	'''~~It was the most powered~~ server, ~~make in old days to how~~ to handle 10,000 connections in parallel on one server'''. ~~Was~~ used in wikipedia server a log time ago and also some google services.		'''lighttpd is a powerful server, made long ago to handle upwards of 10,000 connections in parallel on one server'''. It was used in wikipedia server a log time ago and also some google services.

	{{Note\|As for minimal sites and ~~fast learn~~ purposes ~~are very~~ recommended due it easy configuration process and ~~perfect~~ performance without much configuration. Check https://w3techs.com/technologies/details/ws-lighttpd and ~~noted~~ that is ~~well~~ used in high traffic and important sites like postgresql.org}}		{{Note\|As for minimal sites and quick-start purposes, it is recommended due to its easy configuration process and excellent performance without much configuration. Check https://w3techs.com/technologies/details/ws-lighttpd and note that it is used in high traffic and important sites like postgresql.org}}

	== General information ==		== General information ==

	{{Pkg\|lighttpd}} are not so use due common hosting panels does not handle it's configurations management.. in contrash {{Pkg\|lighttpd}} are multi treated respect {{Pkg\|nginx}} and perfectly support FastCGI process.

	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! Feature/~~Artifac~~ !! Value/Name !! Observations		! Feature/Artifact !! Value/Name !! Observations
	\|-		\|-
	\| Main package name \|\| lighttpd \|\| <code><nowiki>apk add lighttpd</nowiki></code>		\| Main package name \|\| lighttpd \|\| <code><nowiki>apk add lighttpd</nowiki></code>
Line 18:		Line 16:
	\| Manpages and DOCs packages \|\| lighttpd-doc \|\| <code><nowiki>apk add lighttpd-doc</nowiki></code>		\| Manpages and DOCs packages \|\| lighttpd-doc \|\| <code><nowiki>apk add lighttpd-doc</nowiki></code>
	\|-		\|-
	\| Configuration file \|\| {{Path\|/etc/lighttpd/lighttpd.conf}} \|\| ~~It's not close to alpine, just~~ vanilla ~~provived!~~		\| Configuration file \|\| {{Path\|/etc/lighttpd/lighttpd.conf}} \|\| A vanilla default configuration
	\|-		\|-
	\| Html place for system pages \|\| {{Path\|/var/www/localhost/htdocs/}} \|\| Each web server in alpine has own path for that		\| Html place for system pages \|\| {{Path\|/var/www/localhost/htdocs/}} \|\| Each web server in alpine has own path for that
Line 35:		Line 33:
	==== Important Limitations ====		==== Important Limitations ====

	~~'''~~No ~~HTTP/2 or~~ HTTP/3 support~~, also ''not recommended for large files''~~.~~'''~~		Some common hosting panels do not handle {{Pkg\|lighttpd}} configuration management.

			No HTTP/3 support.

	As we read previously.. main purpose was handle several request on one server, so are focused on high load.		As we read previously.. main purpose was handle several request on one server, so are focused on high load.