d8sychain

Members
  • Content Count

    51
  • Joined

  • Last visited

Community Reputation

3 Neutral

About d8sychain

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I just got Mayan-EDMS running a few hours ago, although I have only tested it with consuming one file in a monitored folder. This might help
  2. 1. Installing Docker Compose Add the following to /boot/config/go in order to install docker-compose on each boot: COMPOSE_VERSION=$(curl -s https://api.github.com/repos/docker/compose/releases/latest | grep 'tag_name' | cut -d\" -f4) curl -L https://github.com/docker/compose/releases/download/${COMPOSE_VERSION}/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose chmod +x /usr/local/bin/docker-compose 2. Persisting user-defined networks By default, UnRAID will not persist user-defined Docker networks. You'll need to enable this setting in order to av
  3. This Elasticsearch docker version is built from the official Elasticsearch docker with minimal changes tailoring it for easier use on Unraid and for the purpose for use with Nextcloud. *Minimal support will be provided for this docker. 99% of this docker is based from the Elasticsearch official docker https://hub.docker.com/_/elasticsearch with very minimal charges made. Example of provided support: Requesting that the base image get bumped to a newer version of Elasticsearch and tested before releasing Help with installation incase something in the dir
  4. BTW to everyone, The MediaWiki Maintenance utility has be in d8sychain/mediawiki:edge since it was published. The current 'Edge' version (2020-02-19 v1.33.2-db8 yep almost be a year) is considered finalized as far as I'm concerned. The only reason I never merged it into 'Latest' was because I never finished all of the documentation explaining the added features and their instructions and updating any instructions that may have changed. From SSH terminal, login to UnRaid, then 'docker exec -it docker name /bin/bash' then 'maintenance' or On the UnRaid UI go to the Doc
  5. @EwanL Fixing the extension will be easy 😁 1) On the UnRaid UI go to the Docker page and click the icon for the MediaWiki docker, then click Console 2) Type 'bash' enter, then 'maintenance' enter then you should see this: BTW: Feel free to make a backup before continuing. 3) You want to Option: 1) Extension Manager and then Option: 3) Remove Extension 4) Find the MobileFrontend extension in the list and enter the number for it then press enter again to skip Verbose (done, this removes all the files and any lines in the LocalSettings.php that con
  6. From the MediaWiki MobileFrontend extension page (https://www.mediawiki.org/wiki/Extension:MobileFrontend) The following skins are compatible with MobileFrontend: Skin:Minerva Neue (stable, default on WMF wikis) Skin:Vector (default desktop skin, uses an experimental responsive mode for mobile) Skin:Timeless (experimental skin) To start with, its probably best if you undo what you've tried so far. With out going into a step by step, what changes did you make and I'll try to advise the quickest/easiest way to undo them, unless you just want to yourself.
  7. I did a quick test and put MobileFrontend and the MinervaNeue skin on one of my 'production' wikis. It works with out any errors, however the skin doesn't seem to work correctly, as in, the page loads but any link/action doesn't respond. That could just be due to something not configured, I didn't look that deeply into it. I can say that the mobile Timeless skin works as far as viewing pages but you can't edit. With all of that being said. I can walk you through getting the extension and skin loaded if you want. (Saving myself from explaining each step incase you're not still inter
  8. @EwanL if I remember correctly that skin used to be built into the MobileFrontend extension until 1.34 and then it was removed and needed to be installed separately. So with 1.33 you just need the extension. I'd have to double check to be sure though.
  9. @KDP I realize it might be a little late for this, but MW has an Export pages and Import pages feature. They're listed under 'Special pages'. You can export pages, modules, ect as a XML file and then import it to a different wiki.
  10. Looks like I might need to brush the dust off of the project, make some changes and put out a MW v1.35. It comes with some nice changes to the MW core. Now that Parsoid has been ported to PHP, Node.js is no longer needed and can be dropped from this docker. Also MediaWiki 1.35 is the current stable long-term support release of MediaWiki and its end-of-life will be September 2023 https://www.mediawiki.org/wiki/Version_lifecycle In addition Alpine 3.12 was released May 2020
  11. @KDP The log looks normal. I don't see that it is trying to serve any pages. Example, after the last line in your log file should be followed with something like this: {"log":"- - 19/Oct/2020:03:40:00 +0000 \"GET /Main_Page\" 200\n","stream":"stderr","time":"2020-10-19T03:40:01.934684746Z"} {"log":"- - 19/Oct/2020:03:40:01 +0000 \"GET /load.php\" 200\n","stream":"stderr","time":"2020-10-19T03:40:02.644460091Z"} {"log":"- - 19/Oct/2020:03:40:01 +0000 \"GET /load.php\" 200\n","stream":"stderr","time":"2020-10-19T03:40:08.060153582Z"} {"log":"- - 19/Oct/2020:03:40:08 +0000 \"GET /load.php
  12. Get the Container ID number (you can this in the UnRaid UI docker tab, shown in advanced view) Use the following: cp "$(find /var/lib/docker/containers -name "Container ID*.log")" /mnt/user/appdata The log file will be located in the appdata folder