mediawiki/setup.sh

#!/bin/bash

if [[ ! -h /app/skins ]]; then
    mkdir -p /var/lib/mediawiki/skins
    cp /app/skins/* /var/lib/mediawiki/skins
    rm -rf /app/skins
    ln -s /var/lib/mediawiki/skins /app/skins
fi

if [[ ! -h /app/images ]]; then
    mkdir -p /var/lib/mediawiki/images
    cp /app/images/* /var/lib/mediawiki/images
    rm -rf /app/images
    ln -s /var/lib/mediawiki/images /app/images
fi
We need to set up the volume when the container runs, not when it is built, because mounting a volume over /var/lib/mediawiki will shadow the contents of that directory in the image. 2014-11-24 00:41:30 -06:00			`#!/bin/bash`

if we deploy a new image on top of an existing install then it will overwrite the symlinks going to the shared volume, so check if the file is a symlink and if not then create the link 2014-11-24 02:00:05 -06:00			`if [[ ! -h /app/skins ]]; then`
here we go 2014-11-24 02:05:01 -06:00			`mkdir -p /var/lib/mediawiki/skins`
			`cp /app/skins/* /var/lib/mediawiki/skins`
			`rm -rf /app/skins`
			`ln -s /var/lib/mediawiki/skins /app/skins`
We need to set up the volume when the container runs, not when it is built, because mounting a volume over /var/lib/mediawiki will shadow the contents of that directory in the image. 2014-11-24 00:41:30 -06:00			`fi`
if we deploy a new image on top of an existing install then it will overwrite the symlinks going to the shared volume, so check if the file is a symlink and if not then create the link 2014-11-24 02:00:05 -06:00
			`if [[ ! -h /app/images ]]; then`
here we go 2014-11-24 02:05:01 -06:00			`mkdir -p /var/lib/mediawiki/images`
			`cp /app/images/* /var/lib/mediawiki/images`
			`rm -rf /app/images`
			`ln -s /var/lib/mediawiki/images /app/images`
if we deploy a new image on top of an existing install then it will overwrite the symlinks going to the shared volume, so check if the file is a symlink and if not then create the link 2014-11-24 02:00:05 -06:00			`fi`