Skip to content

Latest commit

 

History

History
44 lines (33 loc) · 1.21 KB

README.md

File metadata and controls

44 lines (33 loc) · 1.21 KB

BlueSpice "Cache" service

This currently is just a regular Memcached server. In the future we may switch to another backend like Redis.

Using it within BlueSpice or MediaWiki

Given you have this service running at localhost:11211, you can configure the BlueSpice cache like this:

$GLOBALS['wgMemCachedServers'] = [ 'localhost:11211' ];
$GLOBALS['wgMainCacheType'] = CACHE_MEMCACHED;
$GLOBALS['wgSessionCacheType'] = CACHE_DB;

HINT: It is not recommended to store user sessions in Memcached, as it may cause session loss.

How to release a new version

Build a new version of the image

docker build -t bluespice/cache:latest .

Apply proper tags

HINT: We align the image tags with the version of BlueSpice that it is compatible with.

Example:

docker tag bluespice/cache:latest bluespice/cache:4
docker tag bluespice/cache:latest bluespice/cache:4.4
docker tag bluespice/cache:latest bluespice/cache:4.4.1

Push the image to the registry

Example:

docker push bluespice/cache:latest
docker push bluespice/cache:4
docker push bluespice/cache:4.4
docker push bluespice/cache:4.4.1

Testing

Install trivy and run trivy image bluespice/cache to check for vulnerabilities.