Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Rocky Assad
    @CodisRedding
    hey all, if I create a dev env using fuge for all of our frontend, services, and db’s, how can I spinup only the services, db’s that I need for the dev task at hand? Is there a way to say fuge run front-end, svc1, svc2, redis1
    or better yet fuge run <some-alias> (runs the above, but aliased)
    Rocky Assad
    @CodisRedding
    Do you all run into issue when referencing local (i.e. artifactory) npm modules within a Dockerfile?
    Rocky Assad
    @CodisRedding
    nvm, needed to ADD ~/.npmrc ~
    Rocky Assad
    @CodisRedding
    hi @mitchellparsons
    Mitchell
    @mitchellparsons
    hello
    S McDowall
    @sjmcdowall
    So am I missing where any / all the documentation for fuge is? Intro — examples — etc. etc?
    Adrian Rossouw
    @AdrianRossouw
    there isn’t much of it. sadly.
    it was on my list before i got sucked into module curation
    it should be pretty self explanatory once you get a new system set up with fuge generate system
    in your current dir, it will create a new system with 2 seneca based services, a hapi or express based REST layer on top of them, and a static file server for hosting your client side app on
    you can then run it using fuge shell fuge/system.yml and start
    the readme is relatively up to date, but the animated gif on that page is not,. it still shows an old version of the generators being run
    Adrian Rossouw
    @AdrianRossouw
    fuge 0.6.4 released - adds seneca 2.0 as basis for all services.
    Ghost
    @ghost~559d399815522ed4b3e3a63a
    Hi. I want to launch hello world and follow README and face this:
    compiling...
    starting proxy...
    proxy frontend 10000 -> 192.168.8.100:20000
    proxy api 10001 -> 192.168.8.100:20001
    proxy service1 10002 -> 192.168.8.100:20002
    proxy service2 10003 -> 192.168.8.100:20003
    container not found
    container not found
    container not found
    client error: 10000 -> 192.168.8.100:20000 => ECONNREFUSED
    please retry operation
    Adrian Rossouw
    @AdrianRossouw
    try running ‘fuge shell fuge/compose-dev.yml'
    also killall node first
    if you tried to run it bnefore, it might still be running in the background
    Ghost
    @ghost~559d399815522ed4b3e3a63a
    Sorry, doesn't work: http://pastebin.com/fqtvEd4Y
    Does it require Docker?
    Ah, ok, I have started processes from shell, now it works
    Jun Matsushita
    @jmatsushita
    Hi @AdrianRossouw I ran into the same problem than @ilyaigpetrov but in my case running fuge shell ./fuge/compose-dev.yml did work. It seems that processes run fine as node but I can't find how to (or figure out if fuge is meant to) run services locally as docker containers. I assume the runDocker config key is for adding other services, but I assumed it would be useful to use fuge to also test a docker compose deployment.
    Maybe I just need to add the images names after building them with docker-compose build in the docker-compose.yml file? Or docker run as the defaults.run command in fuge-config.js ?
    Jun Matsushita
    @jmatsushita
    Adding fuge_* image names and changing runDocker to true does seem to bring up the docker services into the fuge shell but starting them bumps into a hapi error about a missing port. I guess I'm on the right path though...
    Jun Matsushita
    @jmatsushita

    I think the error comes from the fact that apparently ENV variables are not passed to docker run. Instead something strange happens with the 10000 variable being set to 20000 :)

    running: PROXY_HOST=127.0.0.1 SERVICE_HOST=0.0.0.0 frontend_PORT=10000 api_PORT=10001 service1_PORT=10002 service2_PORT=10003 SERVICE_PORT=20000 SERVICE_HOST=0.0.0.0 SERVICE_PORT=20000 PROXY_HOST=192.168.99.100 frontend_PORT=10000 api_PORT=10001 service1_PORT=10002 service2_PORT=10003 exec docker run --name frontend -p 10000:20000 -e 10000=20000 fuge_frontend

    Maybe related to #18
    William P. Riley-Land
    @wprl
    Is there a way to add a custom generator to fuge?
    Dean McDonnell
    @mcdonnelldean
    @/all Just to note, we have a big ol’ example repo that uses fuge, it’s a great repo to work through and see a sample of how we use it. https://github.com/nodezoo/nodezoo-system
    @/all You should also see a little more activity here going forward too :D
    S McDowall
    @sjmcdowall
    @mcdonnelldean Woot +1 .. Good to hear more will be done.. I’ve been following Fuge for a while now and am excited
    Dean McDonnell
    @mcdonnelldean
    We are just moving bodies around to make this happen so give me. Week 😉
    RB
    @BhaskaranR
    i am not able to get fuge work with windows. looks like issue has been raised
    apparatus/fuge#81. Has any one tried it out with windows?
    Khánh Trần
    @rualatngua
    hi all, how can I use dotenv in a service?
    or should I use it?
    Dustin Deus
    @StarpTech
    Hey @all anybody who run into an issue with whitespaces in paths like "program files" on windows see apparatus/fuge#95
    Khánh Trần
    @rualatngua
    @StarpTech I think you should find a way to install NodeJS and NPM outside of C:\Program Files
    there is permission problem also
    Adrian Rossouw
    @AdrianRossouw
    @rualatngua you can specify env_file: in the docker compose config
    that will actually use dotenv to preload the config for you
    Khánh Trần
    @rualatngua
    thank @AdrianRossouw
    Stuart Fenton
    @grandmore
    Do you have any preferred method for debugging? I'm on OS X and have done some experiments with Webstorm, VSCode and node-debug but cannot find an ideal setup. What do you use to develop and debug with?
    chris-gpc
    @chris-gpc
    Is there anyway to change the font color selections when tailing a process? Every now and again I get black font on my default black background in my shell.
    Christian Rijke
    @crijke
    i cannot get 'fuge build' to run on a new system i generated when running "fuge build ./fuge", the error is "Cannot read property 'topology' of undefined". i found that 'system' should be generated by the "xeno" module, but it's undefined. what am i missing here? is this the correct way to run fuge build in the first place?
    Adrian Rossouw
    @AdrianRossouw
    you need to run fuge build fuge/system.yml
    or the direct path to the file
    Christian Rijke
    @crijke
    ah ok, thanks. but there is no system.yml.. i tried "fuge build fuge/compose-dev.yml" but then i get ‘no build script'
    Adrian Rossouw
    @AdrianRossouw
    that is right
    you will need to add a build script, i think
    check how it’s done in nodezoo