Merge branch 'master' of https://git.charlesreid1.com/docker/d-mediawiki

* 'master' of https://git.charlesreid1.com/docker/d-mediawiki:
  update charlesreid1 config to include jinja templates
  clarify
  update charlesreid1-config submodule in d-mediawiki
  update charlesreid1 config to latest commit
  add notes on how to upgrade skins
  bump charlesreid1-config to latest (new navbar)

Dockerfile

@@ -20,30 +20,16 @@ RUN apt-get update && \
 
 # Copy skins, config files, and other particulars into container
 
-# This is the most phenomenally stupid clash of idiocy I have ever encountered
-# in my entire *nix career. MediaWiki needs everything, everything, to be in one folder.
+# WARNING: DOCKER STUPIDITY AHEAD
+# MediaWiki needs everything, everything, to be in one folder.
 # Docker is totally incapable of mounting a file in a volume.
-# I cannot update LocalSettings.php without clearing the cache
-# I cannot clear the cache without reinstalling all of latex
-# SO STUPID
-# I can't bind-mount the skins dir, because then it's owned by root
-# I can't fix the fact that all bind-mounted dirs are owned by root, because I can only add commands in THIS DOCKERFILE
-# and when you run the commands in this dockerfile, YOU CANNOT SEE THE BIND-MOUNTED STUFF
-#
-#
-#
-# WHAT THE HELL MAN
-#
-#
-#
-# DOCKER
-
-# IS
-
-# SO
-
-# STUPID
-
+# I cannot update LocalSettings.php without clearing the cache.
+# I cannot clear the cache without reinstalling all of latex.
+# I can't bind-mount the skins dir, because then it's owned by root.
+# I can't fix the fact that all bind-mounted dirs are owned by root, 
+# because I can only add commands in THIS DOCKERFILE.
+# and when you run the commands in this dockerfile, 
+# YOU CANNOT SEE THE BIND-MOUNTED STUFF.
 
 
 

Skins.md

@@ -0,0 +1,29 @@
+To update the MediaWiki skin:
+
+- See the long angry rant in the Dockerfile
+- You have to rebuild the whole container. Yup, stupid.
+- Rebuild the MW container while the docker pod is still running (won't effect the docker pod)
+- When finished rebuilding the MW container, restart the docker pod.
+
+```
+# switch to main poddirectory
+cd ../
+
+# rebuild all containers
+docker-compose build
+
+# restart the pod
+sudo service dockerpod-charlesreid1 restart
+```
+
+To verify that the skin has correcty been installed, you can check
+the skin file inside the container. First, get a shell in the container:
+
+```
+docker exec -it podcharlesreid1_stormy_mw_1 /bin/bash
+```
+
+Once inside the container, the main web directory is `/var/www/html/`,
+so the skins should be in `/var/www/html/skins/`. You can use `cat` to
+print the file to the screen and verify it is correct.
+