Difference between revisions of "Internal:Master Server services"

From Collective Computational Unit
Jump to navigation Jump to search
(Created page with "The master server provides a number of containerized services. This page documents these services and how they have to be started. All services are run from the user account "...")
 
m (Docker registry)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
The master server provides a number of containerized services. This page documents these services and how they have to be started. All services are run from the user account "services", which has no other functions. The subdirectory "volumes" of this account contains persistent docker volumes for the services which should be backed up regularly.
 
The master server provides a number of containerized services. This page documents these services and how they have to be started. All services are run from the user account "services", which has no other functions. The subdirectory "volumes" of this account contains persistent docker volumes for the services which should be backed up regularly.
 +
 +
== Frontend nginx and firewall ==
 +
 +
The web frontend service initializes the network "frontend", which all other services join if they want to be exposed. Therefore, it needs to be started first, although it will fail and needs to be restarted once all other services are up.
 +
 +
<syntaxhighlight lang="bash">
 +
> cd frontend
 +
> ./update_and_restart.sh
 +
</syntaxhighlight>
 +
 +
  
 
== LDAP server and administration interface ==
 
== LDAP server and administration interface ==
  
 +
<syntaxhighlight lang="bash">
 +
> cd ldap
 +
> ./update_and_restart.sh
 +
</syntaxhighlight>
  
== Mediawiki ==
 
  
  
== Dex and Kubernetes authentication with login app ==
+
== Mediawiki ==
  
 +
<syntaxhighlight lang="bash">
 +
> cd mediawiki
 +
> ./update_and_restart.sh
 +
</syntaxhighlight>
  
== Docker registry ==
 
  
  
== Frontend nginx and firewall ==
+
== Dex and Kubernetes authentication with login app ==
  
 +
<syntaxhighlight lang="bash">
 +
> cd dex
 +
> ./update_and_restart.sh
 +
</syntaxhighlight>
  
  
 +
== Docker registry ==
  
 +
<syntaxhighlight lang="bash">
 +
> cd docker
 +
> sudo apt install gnupg2 pass
 +
> ./update_and_restart.sh
 +
</syntaxhighlight>
  
  
 
[[Category:Internal]]
 
[[Category:Internal]]

Latest revision as of 18:18, 17 June 2019

The master server provides a number of containerized services. This page documents these services and how they have to be started. All services are run from the user account "services", which has no other functions. The subdirectory "volumes" of this account contains persistent docker volumes for the services which should be backed up regularly.

Contents

Frontend nginx and firewall

The web frontend service initializes the network "frontend", which all other services join if they want to be exposed. Therefore, it needs to be started first, although it will fail and needs to be restarted once all other services are up.

> cd frontend
> ./update_and_restart.sh


LDAP server and administration interface

> cd ldap
> ./update_and_restart.sh


Mediawiki

> cd mediawiki
> ./update_and_restart.sh


Dex and Kubernetes authentication with login app

> cd dex
> ./update_and_restart.sh


Docker registry

> cd docker
> sudo apt install gnupg2 pass
> ./update_and_restart.sh