Hi Guillaume, it is working here, too. I've got 3 comments, though:
1. You don't need to explicitly install git in the genieacs-base image, the node image provides common debian packages, including git. 2. Why do you use the old node:0.10 and not the current LTS node:4.4? 3. Why do you use ruby and not rails as the base image for the genieacs- gui image? I could imagine it's because of size. rails:4.2 has already 837.1 MB and the genieacs-gui image has 823.3 MB. I've got some points on my agenda to further improve the genieacs docker setup to get it ready to be used for development and production: - easy transition from development to production - easy import of custom genieacs configuration - easy use of a specific git branch of genieacs - replace WEBrick for production What do you think about these points? Greetings, Oliver On Wed, May 25, 2016 at 09:53:24PM +0200, Guillaume Mazoyer wrote: > OK so I'm starting to get somewhere interesting. > I managed to fix the bug (see [1]) I mentioned in my previous email by > using a node docker as base for the genieacs-base container. > > In case anyone is interested, feel free to test the setup and report > back to me any issue. > I have tested it with a simple CPE doing inform and it seems to work > properly. It appears in the GUI too. _______________________________________________ Users mailing list [email protected] http://lists.genieacs.com/mailman/listinfo/users
