Hi,
I was wondering why you have to use 2222 an 4443 ports,
as far as I understand docker is more than lxc
and I added some way of setting up the network with bridge in this page
https://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/LXC
It's what I used in jenkins buildbot.
It could be interesting to replace this with docker if it's possible to
use snapshot function
to roll back after every test, instead or reseting the database as we do.
Did you investigate the snapshot function ? is it available
Christian
P.S. :I tested that doker package can be built on wheezy
Le 19/03/2014 17:01, Olivier Berger a écrit :
Hi.
You may have heard about Docker [0], a "lightweight containers" solution
which is becoming quite popular.
I've experimented a bit with it to be able to install FusionForge inside
a docker container, instead of having to run a full fledged VM [1].
I've documented the results in
https://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/Docker
I've tested this using my Debian jessie/testing laptop, so YMMV.
In principle, this allows to run FusionForge over Apache2 and PostgreSQL
inside a container, and even allows sharing files between the host
(where you run you text editor, etc.) and the guest (where you may
immediately test the changes, provided you got rid of permission
conflicts).
It's not yet a complete procedure, as some personalization steps are
required inside the guest to make sure everything runs smoothly, but
that's a start, at least for basic plugin work in PHP over the DB.
Any comments and improvements much welcome.
Best regards,
[0] https://www.docker.io/
[1]
http://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/Virtual_machine_development_environment
_______________________________________________
Fusionforge-general mailing list
[email protected]
http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
