Changes for page Interactive Web Sites

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,13 +1,13 @@
1	1	By default you can put static web content in the public_html directory located in your home directory. This content is reachable with [[https:~~/~~/itp.uni-frankfurt.de/~~~~username>>https://itp.uni-frankfurt.de/~~username]].
2	2
3		-There may be reasons that you need some server site processing like php stuff. The following article describes how this is implemented and how you can interactive with it.
	3	+There are reasons that you need some server site processing like php stuff. The following article describes how this is implemented and how you can interactive with it.
4	4
5	5	= Design =
6	6
7	7	It is based on systemd services. Like any system service, services can also run in a user context and under control of the user. Instead of a common web server which delivers files from the public_html directory, a dedicated Apache instance is executed in the users context. There are some prerequisites, which must configure by the admins:
8	8
9		-1. A lingering user session. Normally the session is started with the login of the user. A lingering session is started on boot. This allows the start the services at boot time.
10		-1. A Proxy redirect. The frontend reverse proxy must be configured to forward requests to the specific Apache instance. This allows also second level domains.
	9	+1. A lingering user session. Normally the session is started with the login of the user. A lingering session is started on boot. This allows the start of the services at boot time.
	10	+1. A Proxy redirect. The frontend reverse proxy must be configured to forward request to the specific Apache instance. This allows also second level domains.
11	11
12	12	= Setting up =
13	13