Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Everton Ribeiro
    @nuxlli
    about the error: "//bin/bash godo not found", it's a bug in Docker <= 1.3.1: docker/docker#5135
    but has already been mapped, and we have to fix the release tomorrow: azukiapp/azk#197
    Daniel Durante
    @durango
    Actually neveermind, I may have messed up my stuff with the persistant storage
    I see
    Everton Ribeiro
    @nuxlli
    the correct syntax is azk start <mysistem> -R
    order is important
    Daniel Durante
    @durango
    ok and if i want to wipe out my <mysistem> entirely and start from scratch what would be the best way to do that?
    Everton Ribeiro
    @nuxlli
    rm -Rf .azk && azk start
    @durango, you are using Mac OS X?
    Daniel Durante
    @durango
    @nuxlli yessir
    panic: dial tcp 127.0.0.1:5432: connection refused seems like postgres is not being linked :/
    Everton Ribeiro
    @nuxlli

    It seems the application is trying to connect to the database on the same machine, In azk this should be done through environment variables. Think about the machine that is running your app and the database as separated machines, and the connection would occur by a network between them, the variables will guide you in this path.

    Your Azkfile.js no longer available in https://gist.github.com/durango/6f8800709af8d8a96812, can give a new look to guide you better about what variables?

    Daniel Durante
    @durango
    It should still be there
    Gullit Miranda
    @gullitmiranda
    Currently how is the connection to the database?
    Gullit Miranda
    @gullitmiranda
    So that the application can communicate you need to make a connection URI parse that was exported. This link has an example of how to parse https://gobyexample.com/url-parsing
    on line 78 of your Azkfile.js is where it is defined the connection URI called DATABASE_URL
    Daniel Durante
    @durango
    Yeah thts what im using actually :/ well... its more along the lines of loading a YAML file with the $DATABASE_URL
    setting up agent now
    λ Daniels-MacBook-Pro gambit → λ git master → azk start
    azk: Manifest not valid (see http://doc.azk.io), error:
    azk: ReferenceError: env is not defined
    azk: at eval (eval at template (/usr/local/Cellar/azk/0.7.1/node_modules/lodash/dist/lodash.js:6305:22), <anonymous>:13:10)
    λ Daniels-MacBook-Pro gambit → λ git master
    even weirder error now
    its ok guys, i dont mean to cause this much trouble :/
    Gullit Miranda
    @gullitmiranda
    You are not causing any problems, you actually report their difficulties and problems is extremely important pair that we can improve AZK as a whole.
    @durango Have you made any change in Azkfile.js leaving it different from available gist?
    This error usually occurs when using env instead ofenvs to load the environment variables.
    Daniel Durante
    @durango
    i dont think so ill double check though in about 50 minutes, have a meeting to go into
    Gullit Miranda
    @gullitmiranda
    No problem, if the test is still occurring problems can warn here.
    Daniel Durante
    @durango
    do provisions work on the workdir or before the workdir? I'm presuming before"
    Gullit Miranda
    @gullitmiranda
    the provision uses the workdir as path for command execution
    Gullit Miranda
    @gullitmiranda
    the provision uses the workdir as path for command execution
    Daniel Durante
    @durango
    Oh
    OK, and for exposing port 3000 it's just as simple as ports: {http: "3000/tcp"}, ?
    Ah, nvm ill ask once i stop getting errors, was getting timeouts for godeps (probably an error on my end with our network)
    Gullit Miranda
    @gullitmiranda
    this error occurs in the provision or application start?
    Daniel Durante
    @durango
    Application start
    yeha keep getting timeouts.. https://gist.github.com/durango/30abcb7c2090d929c8eb weird
    Everton Ribeiro
    @nuxlli
    @durango if you switched network while the azk agent was running, recommend to run azk agent stop && azk agent start, and then try to run the start again
    Daniel Durante
    @durango
    @nuxlli that's interesting, this time it no longer gave me a network error but now im back to being godep: command not found thing
    Would be nice to have that in the FAQ btw (the network thing especially for us laptop users :D)
    Daniel Durante
    @durango
    I'm thinking that I should just make a dockerfile that's public with all of these things attached to it already and just use azk as an orchaestration tool rather than build + that
    Everton Ribeiro
    @nuxlli
    @durango in the very near future we will support Dockerfiles directly in Azkfile.js
    but not only that, we also support virtual machines and other container systems
    Daniel Durante
    @durango
    yeah I saw that PR
    or .. w/e it was mentioned lol.. waiting fo rthat feature :D
    Everton Ribeiro
    @nuxlli
    about the error godep: command not found, I'm doing some tests with this image to identify what can be
    Daniel Durante
    @durango
    @nuxlli thanks man, tbh it's probably just a shitty image.. but multiple tutorials used it so I figured it was at least on the "decent" level
    Everton Ribeiro
    @nuxlli
    not know much about go, but I believe the installation go get -u github.com/tools/godep is not adding a binary godep in /gopath/bin as would be expected
    Daniel Durante
    @durango
    @nuxlli yeah thats the issue, the weird thing is.. when i do azk shell and manually type in the go get -u .. everything works as expected
    im wondering ifprovisions is getting all of the necessary environment variables such as $GOROOT and $GOPATH (which is set by the image itself)
    Everton Ribeiro
    @nuxlli

    @durango the error is a bit more complicated than I was expecting. Did some testing here with the image.

    You are right, the error is not in the image but on provision steps implementation. In my tests they get fail sometimes (mainly to get code from bitbucket) until complete all steps.

    A workaround for this (at least until we dont have an "advanced provision") is running all provision commands manually:

    $ azk shell gambit
    # executar os comandos do provision

    So let us know if you are getting get a minimally viable environment.

    We know this is not the best way, after all the provision is there to facilitate this, but it's our chance to debug it better to an environment where we have not done extensive testing in the case of the golang.