search

rlewkowicz / docker-mediawiki-stack

Mediawiki Compose Stack
http://binaryoasis.com:8000
39 stars 16 forks source link

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

Closed evleite closed 7 years ago

evleite commented 7 years ago

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

rlewkowicz commented 7 years ago

Ah yea, This is written for linux. I wanted to do one for mac, but this project on Mac is essentially unusable (Really to me docker on mac is unusable all together) given the way that Mac handles file system mounts: https://github.com/docker/for-mac/issues/77 It's like Reeeeealy slow.

rlewkowicz commented 7 years ago

But I just realized, that you may have already worked around those limitations with some of the syncing plugins.

rm -f $DIR/mediawiki/includes/installer/LocalSettingsGenerator.php \cp $DIR/distribution-files/LocalSettingsGenerator.php $DIR/distribution-files/mwcore/mediawiki/includes/installer/LocalSettingsGenerator.php

Is mostly what you would need. I handle users across containers via the local passwd shadow and group files. I would have to go look again at how that is handled on mac. I was thinking about changing this to use a container just for user management, but then local host permissions can get weird.

I'll leave this open, and try to figure a way to manage a startup script on Mac

evleite commented 7 years ago

Thank you very much for your help.

I was wondering if this can be handle by entry point file, what you think? This way the user and group will be set directly on container.

evleite commented 7 years ago

Another suggestion is to expose the extension folder on docker compose file, in order to upload extensions easily.

rlewkowicz commented 7 years ago

Currently the whole wiki is exposed under mwcore. All files that are needed to operate the wiki are fully exposed

beckbg commented 7 years ago

Checking in on this - thanks!

rlewkowicz commented 7 years ago

@beckbg given the architecture differences between mac and linux and my time constraints I think I'm going to file this under will not fix (at least not personally. Some people have been forking and someone may put something together). Also https://github.com/docker/for-mac/issues/77 is a huge deal given the way my stuff is exposed. They have work arounds, but at this time docker for mac, in my opinion is absolutely not production ready.

At some point I want to redo all this. A guy recommended basing it on laradock I'm not going to use that base, but I think I will emulate the way they do builds. Then it should just kinda work on mac by default.