A few days ago in #mediawiki ^demon made a comment about php 5.4 having a built-in webserver. After a little bit of looking at that we found that when MediaWiki was combined with a standalone copy of 5.4 and the webserver and sqlite support built-in it was possible to startup a quick and easy development instance of MediaWiki with nothing but the MW code and an isolated copy of php. (ie: no real extra dependencies besides what you'd expect on a unix-like OS setup to be able to compile something)
I threw together some bash scripts that will download the latest php 5.4, configure and install it into maintenance/dev/php/, install an sqlite based install of MediaWiki, and startup php's built in development webserver on localhost.
Anyone have a problem with these bash scripts being committed to /trunk/phase3/maintenance/dev/ for anyone checking out MW to use?
On 06.11.2011 2:23, Daniel Friesen wrote:
A few days ago in #mediawiki ^demon made a comment about php 5.4 having a built-in webserver. After a little bit of looking at that we found that when MediaWiki was combined with a standalone copy of 5.4 and the webserver and sqlite support built-in it was possible to startup a quick and easy development instance of MediaWiki with nothing but the MW code and an isolated copy of php. (ie: no real extra dependencies besides what you'd expect on a unix-like OS setup to be able to compile something)
I threw together some bash scripts that will download the latest php 5.4, configure and install it into maintenance/dev/php/, install an sqlite based install of MediaWiki, and startup php's built in development webserver on localhost.
Anyone have a problem with these bash scripts being committed to /trunk/phase3/maintenance/dev/ for anyone checking out MW to use?
That is really interesting. I wish browsers were able to communicate to daemonized applications (like php 5.4 in web-server mode) via system sockets (this option is available to mysql daemon) instead of listening to IP ports. Because having standalone full-featured web application let's say at USB stick or at optical disc would be really cool, if not the possible issues with multiple daemons / applications trying to share the same 127.0.0.1:80 address/port :-( Perhaps some different browsers based on WebKit or another HTML rendering core can be developed to communicate to PHP via sockets? It is strange that nobody has come to implementation of such idea in years. Also, many would like to run Extension:SMW in such way but I doubt it supports sqlite.. Anyway, a good news! Dmitriy
That is really interesting. I wish browsers were able to communicate to daemonized applications (like php 5.4 in web-server mode) via system sockets (this option is available to mysql daemon) instead of listening to IP ports. Because having standalone full-featured web application let's say at USB stick or at optical disc would be really cool, if not the possible issues with multiple daemons / applications trying to share the same 127.0.0.1:80 address/port :-( Perhaps some different browsers based on WebKit or another HTML rendering core can be developed to communicate to PHP via sockets? It is strange that nobody has come to implementation of such idea in years. Also, many would like to run Extension:SMW in such way but I doubt it supports sqlite.. Anyway, a good news! Dmitriy
You can use a dynamic port.
wikitech-l@lists.wikimedia.org