Skip to Content

Changes for page Interactive Web Sites

Last modified by Thomas Coelho (local) on 2024/07/03 10:58
From version 1.2
edited by Thomas Coelho (local)
on 2024/05/15 13:12
Change comment: There is no comment for this version
To version 3.2
edited by Thomas Coelho (local)
on 2024/06/07 11:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,12 +6,12 @@
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 start on boot. This is allows the start of the services at boot time.
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 is allows the start of the services at boot time.
10 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  
14 -On the web server (this is currently web3) the script **install-apache-worker** needs to be run to prepare the environment after the prerequisites have been set up. The main job of the script it to prepare the runtime environment below .apache-service and to install the systemd service file. This can be read (and modified if needed) in **.config/systemd/user/apache-worker.service.**
14 +On the web server (this is currently **web3**) the script **install-apache-worker** needs to be run to prepare the environment after the prerequisites have been set up. The main job of the script it to prepare the runtime environment below .apache-service and to install the systemd service file. This can be read (and modified if needed) in **.config/systemd/user/apache-worker.service.**
15 15  
16 16  {{code language="systemd"}}
17 17  [Unit]
... ... @@ -28,4 +28,13 @@
28 28  
29 29  {{/code}}
30 30  
31 -
31 + On the host in ConditionHost you can control the service witch systemctl ~-~-user.
32 +
33 +{{code language="none"}}
34 +systemctl --user status apache-worker
35 +
36 +{{/code}}
37 +
38 +Replace status with stop/start/restart to control the job,
39 +
40 +Logfiles are written to .apache-service/log. The Logfiles are rotated by rotatelogs which is as a pipe for the logfiles,