Hello,
I was looking at some statistics of school students ( < 17 years ) participation from my state in Open Source program like Google Code In, and it is ~0. The Government here has initiated a project to distribute Raspberry Pi for school students[1], and it would be great to have them setup a Mediawiki development environment with the Pi so that they can contribute.
The Pi's have 1 Gig ram, and I got a docker container of Ubuntu ( arm ) running smooth. There are few blockers to install MW-Vagrant or the LXC container, which are:
1. <bd808> The puppet config for mw-vagrant needs a 64-bit Ubuntu 14.04 container to run inside 2. <bd808> mv-vagrant has a lot of bells and whistles that make it really want a lot of ram and CPU 3. <bd808> hhvm is too ram hungry
and lot more. The other option will be to setup a LAMP stack, which would need to be automated ( need scripts ). I wanted to know if this porting would be feasible, and worth the development hours, and specifically - if someone is interested.
[1] http://gadgets.ndtv.com/others/news/kerala-launches-learn-to-code-pilot-will...
Thanks, Tony Thomas http://blog.tttwrites.in/ ThinkFOSS http://www.thinkfoss.com
*"where there is a wifi, there is a way"*
Congratulations on the container, mention it on mw.org somewhere. It seems with that you've got half the battle won. MediaWiki-vagrant's roles let you easily add features to a development wiki, but maybe instead of trying to get all MediaWiki-vagrant's vagrant and puppet machinery running in your image, you could publish different containers and your recipe for making more of them. I imagine some of the roles like browsertests would bring an RPi to its knees, so you would have to blacklist some of them.
The most useful day-to-day MW-vagrant feature IMO is `git-update`, it would be good to offer that as standalone script.
(Last time I looked the docker catalog had dozens of MediaWiki containers, I don't know how people choose one). On Sep 29, 2015 10:05, "Tony Thomas" 01tonythomas@gmail.com wrote:
Hello,
I was looking at some statistics of school students ( < 17 years ) participation from my state in Open Source program like Google Code In, and it is ~0. The Government here has initiated a project to distribute Raspberry Pi for school students[1], and it would be great to have them setup a Mediawiki development environment with the Pi so that they can contribute.
The Pi's have 1 Gig ram, and I got a docker container of Ubuntu ( arm ) running smooth. There are few blockers to install MW-Vagrant or the LXC container, which are:
- <bd808> The puppet config for mw-vagrant needs a 64-bit Ubuntu 14.04
container to run inside 2. <bd808> mv-vagrant has a lot of bells and whistles that make it really want a lot of ram and CPU 3. <bd808> hhvm is too ram hungry
and lot more. The other option will be to setup a LAMP stack, which would need to be automated ( need scripts ). I wanted to know if this porting would be feasible, and worth the development hours, and specifically - if someone is interested.
[1]
http://gadgets.ndtv.com/others/news/kerala-launches-learn-to-code-pilot-will...
Thanks, Tony Thomas http://blog.tttwrites.in/ ThinkFOSS http://www.thinkfoss.com
*"where there is a wifi, there is a way"* _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
(Last time I looked the docker catalog had dozens of MediaWiki containers, I don't know how people choose one).
Hopefully that will be resolved soon. Negative24
On Tue, Sep 29, 2015 at 11:39 AM, S Page spage@wikimedia.org wrote:
Congratulations on the container, mention it on mw.org somewhere. It seems with that you've got half the battle won. MediaWiki-vagrant's roles let you easily add features to a development wiki, but maybe instead of trying to get all MediaWiki-vagrant's vagrant and puppet machinery running in your image, you could publish different containers and your recipe for making more of them. I imagine some of the roles like browsertests would bring an RPi to its knees, so you would have to blacklist some of them.
The most useful day-to-day MW-vagrant feature IMO is `git-update`, it would be good to offer that as standalone script.
(Last time I looked the docker catalog had dozens of MediaWiki containers, I don't know how people choose one). On Sep 29, 2015 10:05, "Tony Thomas" 01tonythomas@gmail.com wrote:
Hello,
I was looking at some statistics of school students ( < 17 years ) participation from my state in Open Source program like Google Code In, and it is ~0. The Government here has initiated a project to distribute Raspberry Pi for school students[1], and it would be great to have them setup a Mediawiki development environment with the Pi so that they can contribute.
The Pi's have 1 Gig ram, and I got a docker container of Ubuntu ( arm ) running smooth. There are few blockers to install MW-Vagrant or the LXC container, which are:
- <bd808> The puppet config for mw-vagrant needs a 64-bit Ubuntu
14.04
container to run inside 2. <bd808> mv-vagrant has a lot of bells and whistles that make it really want a lot of ram and CPU 3. <bd808> hhvm is too ram hungry
and lot more. The other option will be to setup a LAMP stack, which would need to be automated ( need scripts ). I wanted to know if this porting would be feasible, and worth the development hours, and specifically - if someone is interested.
[1]
http://gadgets.ndtv.com/others/news/kerala-launches-learn-to-code-pilot-will...
Thanks, Tony Thomas http://blog.tttwrites.in/ ThinkFOSS http://www.thinkfoss.com
*"where there is a wifi, there is a way"* _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi,
On 09/29/2015 10:04 AM, Tony Thomas wrote:
and lot more. The other option will be to setup a LAMP stack, which would need to be automated ( need scripts ). I wanted to know if this porting would be feasible, and worth the development hours, and specifically - if someone is interested.
MediaWiki-schroot[1] is a lightweight alternative to MediaWiki-Vagrant, which sets up a LAMH (HHVM, not PHP) stack.
[1] https://www.mediawiki.org/wiki/MediaWiki-schroot
-- Legoktm
On 9/29/15, Tony Thomas 01tonythomas@gmail.com wrote:
Hello,
I was looking at some statistics of school students ( < 17 years ) participation from my state in Open Source program like Google Code In, and it is ~0. The Government here has initiated a project to distribute Raspberry Pi for school students[1], and it would be great to have them setup a Mediawiki development environment with the Pi so that they can contribute.
The Pi's have 1 Gig ram, and I got a docker container of Ubuntu ( arm ) running smooth. There are few blockers to install MW-Vagrant or the LXC container, which are:
- <bd808> The puppet config for mw-vagrant needs a 64-bit Ubuntu 14.04
container to run inside 2. <bd808> mv-vagrant has a lot of bells and whistles that make it really want a lot of ram and CPU 3. <bd808> hhvm is too ram hungry
and lot more. The other option will be to setup a LAMP stack, which would need to be automated ( need scripts ). I wanted to know if this porting would be feasible, and worth the development hours, and specifically - if someone is interested.
[1] http://gadgets.ndtv.com/others/news/kerala-launches-learn-to-code-pilot-will...
Thanks, Tony Thomas http://blog.tttwrites.in/ ThinkFOSS http://www.thinkfoss.com
*"where there is a wifi, there is a way"* _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
If you're looking to reduce resource usage, and its generally expected that there's not very much concurrent access to the wiki, you might want to consider using sqlite instead of mysql.
-- -bawolff
On 2015-09-29 4:55 PM, Brian Wolff wrote:
On 9/29/15, Tony Thomas 01tonythomas@gmail.com wrote:
If you're looking to reduce resource usage, and its generally expected that there's not very much concurrent access to the wiki, you might want to consider using sqlite instead of mysql.
In fact php has a built-in minimal development server.
And some time ago I wrote a series of scripts into maintenance/dev/
Running `maintenance/dev/install.sh` will install MediaWiki using `install.php` with a sqlite database and then startup a php based webserver. I don't even have a LAMP stack on my laptop. mediawiki/dev/ is what I used to test nearly all my contributions to MediaWiki since I wrote it.
</shamless-plug>
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
Thank you devs for the heads-up.
On Wed, Sep 30, 2015 at 5:50 AM, Daniel Friesen daniel@nadir-seen-fire.com wrote:
Running `maintenance/dev/install.sh` will install MediaWiki using `install.php` with a sqlite database and then startup a php based webserver. I don't even have a LAMP stack on my laptop. mediawiki/dev/ is what I used to test nearly all my contributions to MediaWiki since I wrote it.
This one is really interesting, and I wish it was documented somewhere. I will try it up soon in the Rpi and check how it goes. Cloning the entire mediawiki-core doesn't look like a good idea, as the Pi has a SD card disk space of ~ 8 Gig.
https://www.mediawiki.org/wiki/MediaWiki-schroot looks great too. Hope it goes well with arm.
Thanks, Tony Thomas http://blog.tttwrites.in/ ThinkFOSS http://www.thinkfoss.com
*"where there is a wifi, there is a way"*
On Tue, Sep 29, 2015 at 7:04 PM, Tony Thomas 01tonythomas@gmail.com wrote:
Hello,
[CUT]
- <bd808> hhvm is too ram hungry
If I'm not mistaken, hhvm won't compile on anything but an x86-64 architecture. So you definitely need to fall back to zend.
Cheers,
G.
wikitech-l@lists.wikimedia.org