(Die Seite wurde neu angelegt: „The easiest way to run BlueSpice free is to install it with an all-in-one Docker image. All required services are preconfigured. [https://hub.docker.com/r/blu…“) |
Keine Bearbeitungszusammenfassung Markierung: 2017-Quelltext-Bearbeitung |
||
| Zeile 1: | Zeile 1: | ||
{{DISPLAYTITLE:Installing BlueSpice free with Docker}} | |||
__NOTOC__ | |||
The easiest way to run BlueSpice free is to install it with an all-in-one Docker image. All required services are preconfigured. | The easiest way to run BlueSpice free is to install it with an all-in-one Docker image. All required services are preconfigured. | ||
[https://hub.docker.com/r/bluespice/bluespice-free You can find all necessary information directly on Docker Hub.] | [https://hub.docker.com/r/bluespice/bluespice-free You can find all necessary information directly on Docker Hub.] | ||
== | ==How to use the Docker Hub image== | ||
=== | ===Basic usage=== | ||
Example for quick start. Blue Spice will be accessible only in localhost.< | Example for quick start. Blue Spice will be accessible only in localhost. | ||
<syntaxhighlight lang="docker"> | |||
</ | docker run -d -p 80:80 bluespice/bluespice-free | ||
</syntaxhighlight> | |||
=== | ===Keep your data outside of the docker=== | ||
< | <syntaxhighlight lang="docker"> | ||
docker run -d -p 80:80 -v {/my/data/folder}:/data bluespice/bluespice-free | |||
</ | </syntaxhighlight> | ||
=== | ===Setting BlueSpice language and URL=== | ||
< | <syntaxhighlight lang="docker"> | ||
docker run -d -p 80:80 -v {/my/data/folder}:/data -e "bs_lang=en" -e "bs_url=http://www.domain.com" bluespice/bluespice-free | |||
</ | </syntaxhighlight> | ||
=== | ===Activating SSL=== | ||
Using SSL inside the Blue Spice docker image, the <code>data</code> directory should be outside of the docker. Create a folder named <code>cert</code> inside your data folder. Inside this folder, certificates must be named like: | Using SSL inside the Blue Spice docker image, the <code>data</code> directory should be outside of the docker. Create a folder named <code>cert</code> inside your data folder. Inside this folder, certificates must be named like: | ||
* <code>ssl.cert</code> (SSL certificate. ''mandatory'') | *<code>ssl.cert</code> (SSL certificate. ''mandatory'') | ||
* <code>ssl.key</code> (Private key of <code>ssl.cert</code>. ''mandatory'') | *<code>ssl.key</code> (Private key of <code>ssl.cert</code>. ''mandatory'') | ||
* <code>ssl.ca</code> (3rd party CA certs for <code>ssl.cert</code>. ''optional'') If everything is ready for the first run, just run the following command: | *<code>ssl.ca</code> (3rd party CA certs for <code>ssl.cert</code>. ''optional'') If everything is ready for the first run, just run the following command:<br /> | ||
<syntaxhighlight lang="docker"> | |||
docker run -d -p 80:80 -p 443:443 -v {/my/data/folder}:/data -e "bs_lang=en" -e "bs_url=https://www.domain.com" bluespice/bluespice-free | |||
</syntaxhighlight> | |||
''Note: Port 443 includes the command and also <code>$bs_url</code> schema changed to <code>https</code>'' | |||
=== | ===Login to BlueSpice=== | ||
< | <syntaxhighlight lang="docker"> | ||
username: WikiSysop | |||
password: PleaseChangeMe | |||
</ | </syntaxhighlight> | ||
== | ==Which services are runnning?== | ||
* Apache | *Apache | ||
* PHP-FPM | *PHP-FPM | ||
* Jetty9 | *Jetty9 | ||
* Elasticsearch | *Elasticsearch | ||
* MySQL/MariaDB | *MySQL/MariaDB | ||
* Parsoid | *Parsoid | ||
* crond | *crond | ||
* memcached | *memcached | ||
== | ==Manually updating the Docker image== | ||
BlueSpice 3.1.2 has no automatic upgrade feature. | BlueSpice 3.1.2 has no automatic upgrade feature. | ||
[[ | [[Setup:Installation Guide/Docker/Update|See: Manual upgrade process and how to fix some known issues.]] | ||
[[en:{{FULLPAGENAME}}]] | |||
[[de:Setup:Installationsanleitung/Docker/Docker Hub]] | |||
Version vom 8. Dezember 2021, 11:24 Uhr
The easiest way to run BlueSpice free is to install it with an all-in-one Docker image. All required services are preconfigured.
You can find all necessary information directly on Docker Hub.
How to use the Docker Hub image[Bearbeiten | Quelltext bearbeiten]
Basic usage[Bearbeiten | Quelltext bearbeiten]
Example for quick start. Blue Spice will be accessible only in localhost.
docker run -d -p 80:80 bluespice/bluespice-free
Keep your data outside of the docker[Bearbeiten | Quelltext bearbeiten]
docker run -d -p 80:80 -v {/my/data/folder}:/data bluespice/bluespice-free
Setting BlueSpice language and URL[Bearbeiten | Quelltext bearbeiten]
docker run -d -p 80:80 -v {/my/data/folder}:/data -e "bs_lang=en" -e "bs_url=http://www.domain.com" bluespice/bluespice-free
Activating SSL[Bearbeiten | Quelltext bearbeiten]
Using SSL inside the Blue Spice docker image, the data directory should be outside of the docker. Create a folder named cert inside your data folder. Inside this folder, certificates must be named like:
ssl.cert(SSL certificate. mandatory)ssl.key(Private key ofssl.cert. mandatory)ssl.ca(3rd party CA certs forssl.cert. optional) If everything is ready for the first run, just run the following command:
docker run -d -p 80:80 -p 443:443 -v {/my/data/folder}:/data -e "bs_lang=en" -e "bs_url=https://www.domain.com" bluespice/bluespice-free
Note: Port 443 includes the command and also $bs_url schema changed to https
Login to BlueSpice[Bearbeiten | Quelltext bearbeiten]
username: WikiSysop
password: PleaseChangeMe
Which services are runnning?[Bearbeiten | Quelltext bearbeiten]
- Apache
- PHP-FPM
- Jetty9
- Elasticsearch
- MySQL/MariaDB
- Parsoid
- crond
- memcached
Manually updating the Docker image[Bearbeiten | Quelltext bearbeiten]
BlueSpice 3.1.2 has no automatic upgrade feature.
See: Manual upgrade process and how to fix some known issues.
Diskussionen