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
    something more I can do for you?
    Dr Kim Foale
    @kimadactyl
    i think now im kinda wondering about environments and the like. ive switched to your database.yml and now working how to orchestrate local/staging/production dbs
    but thats a big question :)
    Everton Ribeiro
    @nuxlli
    I recommend using the DATABASE_URL
    check this for more informations: http://12factor.net/config
    Dr Kim Foale
    @kimadactyl
    ook
    so basically everything in my azkfile at the moment is for my dev environment, correct? and i should start developing in there?
    then i need to add my digital ocean key for live?
    Everton Ribeiro
    @nuxlli
    yes
    Dr Kim Foale
    @kimadactyl
    great ok. ill have a poke. maybe monday :D
    thanks so much for your help this is the most insane support haha
    Everton Ribeiro
    @nuxlli
    I who thank, whenever you need only contact
    one more question:
    how you met the azk?
    Dr Kim Foale
    @kimadactyl
    i tweeted digital ocean and they suggested azk :)
    i tried capistrano but man every time i have to configure psql i want to stab someone
    Everton Ribeiro
    @nuxlli
    nice
    Dr Kim Foale
    @kimadactyl
    also i want everything to be one press
    feels like every time i have to go to a remote shell to do something im failing
    Everton Ribeiro
    @nuxlli
    capistrano is good, but it is not easy
    Dr Kim Foale
    @kimadactyl
    anything that tells me to install like 5 gems is a bit... wtf
    Everton Ribeiro
    @nuxlli
    haha
    Dr Kim Foale
    @kimadactyl
    im a drupal dev really trying to switch to rails. and i really miss drush its like the best thing about it
    rails is so fun to dev in but deploying it feels like pullling teeth
    Everton Ribeiro
    @nuxlli
    deploy rails compared with php is really complicated and boring
    Dr Kim Foale
    @kimadactyl
    no joke
    ruby feels like building on sand to begin with as it is
    Everton Ribeiro
    @nuxlli
    @kimadactyl I'm sorry, but really need to go, thanks and []s
    Dr Kim Foale
    @kimadactyl
    have a great weekend :) thanks again
    back on monday most likely!
    Gullit Miranda
    @gullitmiranda
    @kimadactyl sorry for delay.
    I'm doing a form for documenting in the image
    Dr Kim Foale
    @kimadactyl
    no hurry man its friday :)
    Dr Kim Foale
    @kimadactyl
    holy crap dude :D
    Gullit Miranda
    @gullitmiranda
    don't work?
    Dr Kim Foale
    @kimadactyl
    lol no just amazed at this support :D
    that was an exclamation of thanks
    Gullit Miranda
    @gullitmiranda
    ow. sorry for not understanding, unfortunately I and the @nuxlli we are the weakest English team :(
    Dr Kim Foale
    @kimadactyl
    haha do not worry at all :)
    im northern too my english is weird
    Gullit Miranda
    @gullitmiranda
    now I'm doing the second section (### Auto import using Azkfile)
    rsrs ok
    but when something is not clear, you can talk me, after all I'm still learning =D
    Dr Kim Foale
    @kimadactyl
    sure :)
    if you can test and review I will tank you profusely
    Dr Kim Foale
    @kimadactyl
    sure, back shortly :) had some wine now might be a bit less lucid :D
    Gullit Miranda
    @gullitmiranda
    rsrs no problem =D
    Gullit Miranda
    @gullitmiranda
    when you revise, you can do this in PR azukiapp/docker-postgres#3
    Dr Kim Foale
    @kimadactyl
    kim@chips:~/git/taichi/taichi_rails$ azk restart
    azk: ↓ stopping `taichi-school` system, 1 instances...
    azk: ↓ stopping `postgres` system, 1 instances...
    azk: ↑ starting `taichi-school` system, 1 new instances...
    azk: ↑ starting `postgres` system, 1 new instances...
    azk: ✓ checking `azukiapp/ruby:2.3.0` image...
    azk: ◴ waiting for `postgres` system to start, trying connection to port data/tcp...
    azk: An error occurred. It will stop all instances already running. See details below.
    
    azk: System `postgres` not running
    azk: System `taichi-school` not running
    azk: Run system `postgres` return: (3), for command: ["/azk-entrypoint.sh","postgres"]:
    azk:  .postgres [log] >  The files belonging to this database system will be owned by user "postgres".
    azk:  .postgres [log] >  This user must also own the server process.
    azk:  .postgres [log] >  
    azk:  .postgres [log] >  The database cluster will be initialized with locale "en_US.utf8".
    azk:  .postgres [log] >  The default database encoding has accordingly been set to "UTF8".
    azk:  .postgres [log] >  The default text search configuration will be set to "english".
    azk:  .postgres [log] >  
    azk:  .postgres [log] >  Data page checksums are disabled.
    azk:  .postgres [log] >  
    azk:  .postgres [log] >  fixing permissions on existing directory /var/lib/postgresql/data ... ok
    azk:  .postgres [log] >  creating subdirectories ... ok
    azk:  .postgres [log] >  selecting default max_connections ... 100
    azk:  .postgres [log] >  selecting default shared_buffers ... 128MB
    azk:  .postgres [log] >  selecting dynamic shared memory implementation ... posix
    azk:  .postgres [log] >  creating configuration files ... ok
    azk:  .postgres [log] >  creating template1 database in /var/lib/postgresql/data/base/1 ... ok
    azk:  .postgres [log] >  initializing pg_authid ... ok
    azk:  .postgres [log] >  initializing dependencies ... ok
    azk:  .postgres [log] >  creating system views ... ok
    azk:  .postgres [log] >  loading system objects' descriptions ... ok
    azk:  .postgres [log] >  creating collations ... ok
    azk:  .postgres [log] >  creating conversions ... ok
    azk:  .postgres [log] >  creating dictionaries ... ok
    azk:  .postgres [log] >  setting privileges on built-in objects ... ok
    azk:  .postgres [log] >  creating information schema ... ok
    azk:  .postgres [log] >  loading PL/pgSQL server-side language ... ok
    azk:  .postgres [log] >  vacuuming database template1 ... ok
    azk:  .postgres [log] >  copying template1 to template0 ... ok
    azk:  .postgres [log] >  copying template1 to postgres ... ok
    azk:  .postgres [log] >  syncing data to disk ... ok
    azk:  .postgres [log] >  
    azk:  .postgres [log] >  Success. You can now start the database server using:
    azk:  .postgres [log] >  
    azk:  .postgres [log] >      postgres -D /var/lib/postgresql/data
    azk:  .postgres [log] >  or
    azk:  .postgres [log] >      pg_ctl -D /var/lib/postgresql/data -l logfile start
    azk:  .postgres [log] >  
    azk:  .postgres [log] >  
    azk:  .postgres [log] >  WARNING: enabling "trust" authentication for local connections
    azk:  .postgres [log] >  You can change this by editing pg_hba.conf or using the option -A, or
    azk:  .postgres [log] >  --auth-local and --auth-host, the next time you run initdb.
    azk:  .postgres [log] >  ****************************************************
    azk:  .postgres [log] >  WARNING: No password has been set for the database.
    azk:  .postgres [log] >           This will allow anyone with access to the
    azk:  .postgres [log] >           Postgres port to access your database. In
    azk:  .postgres [log] >           Docker's default configuration, this is
    azk:  .postgres [log] >           effectively any other container on the same
    azk:  .postgres [log] >           system.
    azk:  .postgres [log] >  
    azk:  .postgres [log] >           Use "-e POSTGRES_PASSWORD=password" to set
    azk:  .postgres [log] >           it in "docker run".
    azk:  .postgres [log] >  ****************************************************
    azk:  .postgres [log] >  waiting for server to start....LOG:  database system was shut down at 2016-03-25 21:43:29 UTC
    azk:  .postg
    Dr Kim Foale
    @kimadactyl
    logging off for tonight thanks again :) back on monday