These are chat archives for apparatus/fuge

1st
Feb 2016
iadknet
@iadknet
Feb 01 2016 00:43
ah, sorry, yes, I had tried docker-compose and it worked. This is OSX with docker 1.9.1.
Dave Heath
@davehimself
Feb 01 2016 13:45
@iadknet sounds like a bug in fuge. think you can put together an issue?
also, are you sure the container name is influxdb?
David Mark Clements
@davidmarkclements
Feb 01 2016 14:34
@davehimself @iadknet so.. currently the way we're working with fuge is to create an infrastructure.yml file - this specifies any containers that we need for local development (e.g. databases etc.). then the compose-dev.yml file specifies services that we're developing. At the moment, we only use fuge to start and stop services in compose-dev.yml, but use docker-compose for infrastructure. I think there's a need to document this (and/or augment fuge to start infrastructure or something)
Dave Heath
@davehimself
Feb 01 2016 15:32
@davidmarkclements yeah, bruh. that
iadknet
@iadknet
Feb 01 2016 17:07
ah, okay. @davidmarkclements I was using fuge generate dashboard - which I don't think is a documented feature, but looked interesting. That was the script that generated the compose-dev.yml file.
iadknet
@iadknet
Feb 01 2016 17:12

I'm interested in fuge because currently we have a combination of Vagrant + Docker (for infrastructure) and a complicated gulp script that handles checking out the code for the various microservices and compiling/running them.

The gulp part of that equation is a bit unreliable, and if I could replace the Vagrant side with fuge as well.. that would be an awesome bonus.

David Mark Clements
@davidmarkclements
Feb 01 2016 17:13

ah yeah - no so we put the infrastructure services in the compose-dev file as well - then fuge is aware of them (allows it to put the networking layer in place for each service)

when a service starts it has some environment variables injected - say you have a container called mysql, you'll get a process.env.MYSQL_PORT in your services - so you can connect

so it's best if it goes in both infrastructure and compose-dev - the dashboard btw essentially sets up services to use https://www.npmjs.com/package/seneca-msgstats and includes a vidi dashboard service https://www.npmjs.com/package/vidi-dashboard so that we can visualise messages in the transport
@iadknet - happy to talk more about this, if we can get fuge working for you use case I think that'll be a plus for everyone
iadknet
@iadknet
Feb 01 2016 17:19
btw, the current release of vidi-dashboard has a problem with package versions that prevents npm install from succeeding. It's been fixed, but the fix is not in the latest release... so it takes some manual hacking of package.json to succeed.
thanks for the help, I'll do some more poking around and see if I can get some of our services working
David Mark Clements
@davidmarkclements
Feb 01 2016 17:25
PR ? :D