Difference between revisions of "Setup:Installation Guide/Docker/Update"
[quality revision] | [quality revision] |
(Tag: 2017 source edit) |
(Tag: Visual edit) |
Introduction[edit | edit source]
- Edition: BlueSpice free, distributed on Docker Hub as a Docker image.
- The current Starting from version 3.1.2 release has no automatic upgrade feature. The automatic upgrade feature will be included at BlueSpice 3.1.3.
- This document covers the manual upgrade process and how to fix some known issues.
- 13, BlueSpice Docker Hub release is able to upgrade itself automatically.
Spinning up a new container with old data[edit | edit source]
We assume you have a BlueSpice installation from Docker Hub. Also, this installation should have been done with using an external data volume.
Example: docker run -d -p 80:80 -v {/my/data/folder}:/data bluespice/bluespice-free
sudo cp -Rf /my/data/folder /my/data/current
docker container stop $your_container_id_or_name
docker container rm $your_container_id_or_name
docker pull bluespice/bluespice-free:latest
5. Create a new data folder for the new installation:
mkdir /my/data/new
6. Create a fresh container with the new image:
docker run -d -p 80:80 -v {/my/data/new}:/data bluespice/bluespice-free
7. When the container boots up, you have an empty wiki. Stop the newly created docker and move back your old backup to the new instance:
docker container stop $new_container_name_or_id
8. Remove the content of the new container:
sudo rm -Rf /my/data/new/*
9. Move the backup into /my/data/new:
sudo cp -Rf /my/data/current/* /my/data/new/
10. Start the newly created container:
docker container start $new_container_name_or_id
Now, your new container with your old data is up.
But you still have to run some maintenance scripts as well as some fixes:
BlueSpice DockerHub container will detect the old installation and execute necessary maintenance tasks in the background.
After the bootup, the Wiki will be up to date.
Fixing the broken search[edit | edit source]
The following commands fix the BlueSpiceExtendedSearch indexes:
sudo docker exec
$container_
name_or_id
/
opt/docker/setwikiperm.sh /data/www/bluespice/w
sudo docker exec
$container_
name_or_id /usr/bin/php /data/www/bluespice/w/maintenance/update.php --quick
sudo docker exec
$container_
name_or_id /usr/bin/php /data/www/bluespice/w/maintenance/rebuildall.php --quick
sudo docker exec
$container_
name_or_id /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/initBackends.php --quick
sudo docker exec
$container_
name_or_id /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/rebuildIndex.php
sudo docker exec
$container_
name_or_id /usr/bin/php /data/www/bluespice/w/maintenance/runJobs.php
Fixing the broken search[edit | edit source]
The following commands fix the BlueSpiceExtendedSearch indexes:
sudo docker exec $container_name_or_id /opt/docker/setwikiperm.sh /data/www/bluespice/w sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/maintenance/update.php --quick sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/maintenance/rebuildall.php --quick sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/initBackends.php --quick sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/rebuildIndex.php su
{{DISPLAYTITLE:Docker upates}} == <span class="mw-headline" id="Introduction">Introduction</span> == * Updating docker images}} ==Introduction== *Edition: BlueSpice free, distributed on Docker Hub as a Docker image. * The currentStarting from version 3.1.2 release has no automatic upgrade feature. The automatic upgrade feature will be included at BlueSpice 3.1.3. * This document covers the manual upgrade process and how to fix some known issues. == <span class="mw-headline" id="Spinning_up_new_container_with_old_data">13, BlueSpice Docker Hub release is able to upgrade itself automatically. ==Spinning up a new container with old data</span> == We assume you have a BlueSpice installation from Docker Hub. Also, this installation should have been done with using an external data volume. Example: <syntaxhighlight lang="bash"> docker run -d -p <span class="m">80</span>:80 -v <span class="o">{</span>{/my/data/folder<span class="o">}</span>}:/data bluespice/bluespice-free </syntaxhighlight> 1.Back- up your current data folder: <syntaxhighlight lang="bash"> sudo cp -Rf /my/data/folder /my/data/current </syntaxhighlight> 2. Stop your current BlueSpice-free container: <syntaxhighlight lang="bash"> docker container stop <span class="nv">$your_container_id_or_name</span> </syntaxhighlight> 3. Remove the container (optional): <syntaxhighlight lang="bash"> docker container rm <span class="nv">$your_container_id_or_name</span> </syntaxhighlight> 4. Fetch the new container image: <syntaxhighlight lang="bash"> docker pull bluespice/bluespice-free:latest 5. Create a new data folder for the new installation: mkdir /my/data/new </syntaxhighlight> 6. Create a fresh container with the new image: <syntaxhighlight lang="bash"> docker run -d -p <span class="m">80</span>:80 -v <span class="o">{</span>{/my/data/new<span class="o">}</span>}:/data bluespice/bluespice-free 7. When </syntaxhighlight> the container boots up, you have an empty wiki. Stop the newly created docker and move back your old backup to the new instance: docker container stop <span class="nv">$new_container_name_or_id</span> 8. Remove the content of the new container: sudo rm -Rf /my/data/new/* 9. Move the backup into /my/data/new: sudo cp -Rf /my/data/current/* /my/data/new/ 10. Start the newly created container: docker container start <span class="nv">$new_container_name_or_id</span> Now, your new container with your old data is up. But you still have to run some maintenance scripts as well as some fixes: sudo docker <span class="nb">exec</span> <span class="nv">$new_container_name_or_id</span> chown -Rf mysql:mysql /data/mysql sudo docker <span class="nb">exec</span> <span class="nv">$new_container_name_or_id</span> /etc/init.d/mysql restart sudo docker <span class="nb">exec</span> <span class="nv">$new_container_name_or_id</span> /BlueSpice DockerHub container will detect the old installation and execute necessary maintenance tasks in the background. After the bootup, the Wiki will be up to date. <br /> ==Fixing the broken search== The following commands fix the BlueSpiceExtendedSearch indexes: <syntaxhighlight lang="bash"> sudo docker exec $container_name_or_id /opt/docker/setwikiperm.sh /data/www/bluespice/w sudo docker <span class="nb">exec</span> <span class="nv">$new_container_ $container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/maintenance/update.php --quick sudo docker <span class="nb">exec</span> <span class="nv">$new_container_ $container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/maintenance/rebuildall.php --quick sudo docker <span class="nb">exec</span> <span class="nv">$new_container_ $container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/initBackends.php --quick sudo docker <span class="nb">exec</span> <span class="nv">$new_container_ $container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/rebuildIndex.php sudo docker <span class="nb">exec</span> <span class="nv">$new_container_ $container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/maintenance/runJobs.php == <span class="mw-headline" id="Fixing_the_broken_Search_Bar">Fixing the broken search</span> == The following commands fix the BlueSpiceExtendedSearch indexes: sudo docker <span class="nb">exec</span> <span class="nv">$container_name_or_id</span> /opt/docker/setwikiperm.sh /data/www/bluespice/w sudo docker <span class="nb">exec</span> <span class="nv">$container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/maintenance/update.php --quick sudo docker <span class="nb">exec</span> <span class="nv">$container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/maintenance/rebuildall.php --quick sudo docker <span class="nb">exec</span> <span class="nv">$container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/initBackends.php --quick sudo docker <span class="nb">exec</span> <span class="nv">$container_name_or_id</span> /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/rebuildIndex.php su</syntaxhighlight> [[en:{{FULLPAGENAME}}]] [[de:Setup:Installationsanleitung/Docker/Update]]
(10 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | {{DISPLAYTITLE: | + | {{DISPLAYTITLE:Updating docker images}} |
+ | ==Introduction== | ||
− | + | *Edition: BlueSpice free, distributed on Docker Hub as a Docker image. | |
+ | *Starting from version 3.1.13, BlueSpice Docker Hub release is able to upgrade itself automatically. | ||
− | + | ==Spinning up a new container with old data== | |
− | + | We assume you have a BlueSpice installation from Docker Hub. Also, this installation should have been done using an external data volume. | |
− | |||
− | + | Example:<syntaxhighlight lang="bash"> | |
− | + | docker run -d -p 80:80 -v {/my/data/folder}:/data bluespice/bluespice-free | |
+ | </syntaxhighlight> | ||
− | + | 1.Back up your current data folder:<syntaxhighlight lang="bash"> | |
− | + | sudo cp -Rf /my/data/folder /my/data/current | |
− | 1.Back | + | </syntaxhighlight> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | 2. Stop your current BlueSpice-free container:<syntaxhighlight lang="bash"> | |
− | + | docker container stop $your_container_id_or_name | |
− | + | </syntaxhighlight> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | = | + | 3. Remove the container (optional):<syntaxhighlight lang="bash"> |
+ | docker container rm $your_container_id_or_name | ||
+ | </syntaxhighlight> | ||
+ | |||
+ | 4. Fetch the new container image:<syntaxhighlight lang="bash"> | ||
+ | docker pull bluespice/bluespice-free:latest | ||
+ | </syntaxhighlight> | ||
+ | |||
+ | 6. Create a fresh container with the new image:<syntaxhighlight lang="bash"> | ||
+ | docker run -d -p 80:80 -v {/my/data/new}:/data bluespice/bluespice-free | ||
+ | </syntaxhighlight> | ||
+ | the BlueSpice DockerHub container will detect the old installation and execute necessary maintenance tasks in the background. | ||
+ | |||
+ | After the bootup, the Wiki will be up to date. | ||
+ | |||
+ | <br /> | ||
+ | ==Fixing the broken search== | ||
The following commands fix the BlueSpiceExtendedSearch indexes: | The following commands fix the BlueSpiceExtendedSearch indexes: | ||
− | + | ||
− | + | <syntaxhighlight lang="bash"> | |
− | + | sudo docker exec $container_name_or_id /opt/docker/setwikiperm.sh /data/www/bluespice/w | |
− | + | sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/maintenance/update.php --quick | |
− | + | sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/maintenance/rebuildall.php --quick | |
− | + | sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/initBackends.php --quick | |
+ | sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/extensions/BlueSpiceExtendedSearch/maintenance/rebuildIndex.php | ||
+ | sudo docker exec $container_name_or_id /usr/bin/php /data/www/bluespice/w/maintenance/runJobs.php | ||
+ | </syntaxhighlight> | ||
+ | |||
+ | [[en:{{FULLPAGENAME}}]] | ||
+ | [[de:Setup:Installationsanleitung/Docker/Update]] |