rlewkowicz/docker-mediawiki-stack

Mediawiki Compose Stack

docker-mediawiki-stack's Issues

Just a note

@MichaelDarr I know this is goofy, I don't have a way to like message people though. I saw you forked this, and it probably still works. I think there's a better way to do this now though. Running this stuff via bitnamis stack is going to be WAY less overhead for you.

https://hireryan.today/2021/08/20/running-single-node-kubernetes-with-persistent-data/

I see you have some k8s stuff, so you probably can get this running. But this allows you single node k8s with persistent data. I'm still finishing this series, but I would recommend bitnamis stack on k8s

Bad Gateway

URL : https:///mw-config/index.php

When I click "Please set up the wiki first." I got an error

Output :
502 Bad Gateway

nginx/1.10.3

I rebuilt this and I think it's much better

Hey all, you're getting pinged (I hope you don't mind) because you've interacted with this project in some form. The master branch has been re-engineered so you can grab the latest version of MediaWiki as well as PHP. I'm not 100% sure on a migration path, I think you should be able to gracefully shut down the old instance, and just move the mysql folder. I think MediaWiki will then prompt you to upgrade. I would make backups though. The rebuild is pretty fresh, so there may be some snags, but it's a lot better (in some forms) than the old build.

@zakharovvi
@yanyanlong
@WFreelandEcon
@vylan
@vitlav
@versable
@sunwenquan
@sorenfidelis
@sjmoran
@rlewkowicz
@rbax
@ratijas
@nschonni
@mayel
@MaximeSoulie
@lmorillas
@leonpeek
@kghbln
@jackwen
@j717273419
@heathenpizzafairy
@hdkmraf
@g3rhard
@evleite
@emossman
@dylanvorster
@douglasmoraisdev
@danyill
@cwoodhams
@crest55
@coronin
@CoolHandDev
@chudnyi
@calnation
@alvarosaurus
@alisheikh
@addshore

Error when I run sudo ./runfirst.bash && \ command

Hi I am trying to run the mediawiki on docker but when I run the command sudo ./runfirst.bash &&
I got the follow problems:

user-MacBook-Pro:docker-mediawiki-stack user$ sudo ./runfirst.bash && \ dev
./runfirst.bash: line 9: service: command not found
./runfirst.bash: line 12: useradd: command not found
sed: 1: "/Development/images/doc ...": command i expects \ followed by text
chown: www-data.www-data: illegal user name

can't edit wiki with VirtualEditor

I set up the mediawiki stack use docker compose, and I configured my mediawiki successfully. But when I click 'Edit' tab to edit my wiki page, I hope the brower will open VirtualEditor, but a alter appeared, it said

"Error loading data from server: Could not connect to the server. Would you like to retry?".

Then I checked my brower console, there was a error message:

"https://restbase:7231/wiki/v1/page/html/Main_Page/10?redirect=false" net::ERR_NAME_NOT_RESOLVED
RESTBase load failed: error

I want to ask how to solve the problem, anyone has idea? thanks.

Adding Extensions

Beautiful work that actually works! Thank you so much for the effort and sharing.

Pardon the n00b question, but regarding extensions, can you provide some guidance on the appropriate way to pre-install of them? Or do you think it's better to install them later after initial deployment? Thanks.

HowTo?

Where are the instructions to install this?

Build on top of Laradock

Not sure if you looked at it or not, but building on top of Laradock can simplify the supporting this project (long-run) and also make the build more modular (more docker like).

On the side, I worked on making an additional Dockerfile based on the Jenkins file you have in core repo. I'll share it after I test it a bit, in case you're interested of course. My idea is to make the entire build more dynamic and portable and not depend much on version control. I know, extremism ;)

Error creating thumbnail: /bin/bash: /usr/bin/convert: No such file or directory

Imagemagick is not installed when using the docker-mediawiki-stack distribution.

how to contribute

Hi,

Thanks for the phab response on Mediawiki and docker. I've spent some time doing the same thing -- but more clumsily.

I have quite modest git, docker, mediawiki and jenkins skills but I've set myself the task of putting together a build which meets my requirements in about 5 days ;-)

I've cloned your git repositories and will work through creating Jenkins builds for the same pointing towards remarkably similar docker images. Then I need to try and augment to meet my own needs. If I feel there are items that might be of upstream value should I log issues or submit a pull request or let you cherry pick if interested? I think a PR might be a problem given that we're not pointing at the same container/build infrastructure.

Currently the to-do list is something like:

1. Get things up and running
2. Sort out caching
3. Add Elasticsearch/Cirrussearch
4. Sort out all the extensions/skins I need to migrate from my existing wiki including Semantic Mediawiki
5. Potentially add Mathoid or Graphoid

Interested in your thoughts and appreciate you making your work openly available.

Consider making the mediawiki folder a submodule

Would it not be a better idea to rather make the mediawiki folder a git submodule so that we can just pull the updates in that folder. Having all the source code of mediawiki duplicated here doesn't make sense if this tech stack wraps the media wiki project surely?