You are viewing an old version of this page. Return to the latest version.
Version of 14:34, 26 September 2019 by MLR
Difference between revisions of "Setup:Installation Guide/Docker/Docker Hub"
< Setup:Installation Guide | DockerReturn to history page
← Setup:Installation Guide/Docker/Docker Hub
← Setup:Installation Guide/Docker/Docker Hub
| [quality revision] | [quality revision] |
(Created page with "The easieast way to run BlueSpice free is to use Docker Hub with an all-in-one image. All required services are preconfigured. [https://hub.docker.com/r/bluespice/bluespice...") (Tag: 2017 source edit) |
(Default password is changed.) (Tag: Visual edit) |
The easieast easiest way to run BlueSpice free is to use Docker Hub install it with an all-in-one Docker image. All required services are preconfigured.
You can find all necessary information directly on Docker Hub.
Contents
How to use the Docker Hub image
How to use the Docker Hub image[edit | edit source]
Introduction[edit | edit source]
Basic usage[edit | edit source]
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[edit | edit source]
docker run -d -p 80:80 -v {/my/data/folder}:/data bluespice/bluespice-free
Setting BlueSpice language and URL[edit | edit source]
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[edit | edit source]
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 Blue SpiceBlueSpice[edit | edit source]
username: WikiSysop
password:
PleaseChangeMe
Which services are runnning?[edit | edit source]
- Apache
- PHP-FPM
- Jetty9
- Elasticsearch
- MySQL/MariaDB
- Parsoid
- crond
- memcached
Manually updating the Docker image[edit | edit source]
BlueSpice 3.1.2 has no automatic upgrade feature.
See: Manual upgrade process and how to fix some known issues.
The easieast{{DISPLAYTITLE:Installing BlueSpice free with Docker}} __NOTOC__ The easiest way to run BlueSpice free is to use Docker Hub 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.] == How to use the Docker Hub image == == Introduction == === Basic usage == ===Basic usage=== Example for quick start. Blue Spice will be accessible only in localhost. <code><syntaxhighlight lang="docker"> docker run -d -p 80:80 bluespice/bluespice-free</code> === </syntaxhighlight> ===Keep your data outside of the docker === <code>=== <syntaxhighlight lang="docker"> docker run -d -p 80:80 -v {/my/data/folder}:/data bluespice/bluespice-free</code> === </syntaxhighlight> ===Setting BlueSpice language and URL === <code>=== <syntaxhighlight lang="docker"> docker run -d -p 80:80 -v {/my/data/folder}:/data -e "bs_lang=en" -e "bs_url=<nowiki>http://www.domain.com</nowiki>" bluespice/bluespice-free</code> === Activating SSL </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: * <code>ssl.cert</code> (SSL certificate. ''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><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=<nowiki>https://www.domain.com</nowiki>" bluespice/bluespice-free</code> </syntaxhighlight> ''Note: Port 443 includes the command and also <code>$bs_url</code> schema changed to <code>https</code>'' === Login to Blue Spice === <code>username: WikiSysop password: hallowelt</code> == BlueSpice=== <syntaxhighlight lang="docker"> username: WikiSysop password: PleaseChangeMe </syntaxhighlight> ==Which services are runnning? == * Apache * PHP-FPM * Jetty9 * Elasticsearch * MySQL/MariaDB * Parsoid * crond * memcached [[en:{{PAGENAME}}]][[de:https://de.wiki.bluespice.com/wiki/Setup:Docker_== *Apache *PHP-FPM *Jetty9 *Elasticsearch *MySQL/MariaDB *Parsoid *crond *memcached ==Manually updating the Docker image== 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]]
| (16 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | The | + | {{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. | ||
[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 == | + | ==How to use the Docker Hub image== |
| − | + | ===Basic usage=== | |
| − | |||
| − | === 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 === | + | ===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 === | + | ===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 === | + | ===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>'' | ''Note: Port 443 includes the command and also <code>$bs_url</code> schema changed to <code>https</code>'' | ||
| − | === Login to | + | ===Login to BlueSpice=== |
| − | + | <syntaxhighlight lang="docker"> | |
| − | + | username: WikiSysop | |
| + | password: PleaseChangeMe | ||
| + | </syntaxhighlight> | ||
| − | == Which services are runnning? == | + | ==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. | ||
| − | [[en:{{ | + | [[Setup:Installation Guide/Docker/Update|See: Manual upgrade process and how to fix some known issues.]] |
| + | [[en:{{FULLPAGENAME}}]] | ||
| + | [[de:Setup:Installationsanleitung/Docker/Docker Hub]] | ||