Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    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
    (maybe sunday will see)
    Gullit Miranda
    @gullitmiranda
    you tryed start again?
    Danni Friedland
    @BlueHotDog
    hey guys
    i'm keeping getting
    azk: Error: HTTP code is 500 which indicates error: server error - Driver aufs failed to remove root filesystem 5aa2ccb8a45b7e19a828ac3f36fb547402affa41d5431f6ecb5670c1e631475d: rename /mnt/sda1/aufs/mnt/5aa2ccb8a45b7e19a828ac3f36fb547402affa41d5431f6ecb5670c1e631475d /mnt/sda1/aufs/mnt/5aa2ccb8a45b7e19a828ac3f36fb547402affa41d5431f6ecb5670c1e631475d-removing: device or resource busy
    
    azk:     at /usr/local/Cellar/azk/0.17.0/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:218:17
    azk:     at getCause (/usr/local/Cellar/azk/0.17.0/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:246:7)
    azk:     at [object Object].Modem.buildPayload (/usr/local/Cellar/azk/0.17.0/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:217:5)
    azk:     at IncomingMessage.<anonymous> (/usr/local/Cellar/azk/0.17.0/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:193:14)
    azk:     at IncomingMessage.emit (events.js:117:20)
    azk:     at _stream_readable.js:944:16
    azk:     at process._tickCallback (node.js:448:13)
    Gullit Miranda
    @gullitmiranda
    hi @BlueHotDog
    you must use some command that is trying to remove some mount.
    what type of system?
    Dr Kim Foale
    @kimadactyl
    heya gonna poke a little today if you're about, will just be posting observations otherwise
    first thing is that that dns fix works fine but i have to edit my /etc/resolver/dev.azk.io file every load based on what docker loads as which isn't ideal but obv not ahuge problem
    the postgres thing is currently giving me this. looks like postgres exports ownership information in the dump file, really irritating :/
    azk:  .postgres [log] >  /docker-entrypoint.sh: running /docker-entrypoint-initdb.d/db.sql
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  CREATE EXTENSION
    azk:  .postgres [log] >  COMMENT
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  SET
    azk:  .postgres [log] >  CREATE TABLE
    azk:  .postgres [log] >  ERROR:  role "kim" does not exist
    azk:  .postgres [log] >  STATEMENT:  ALTER TABLE active_admin_comments OWNER TO kim;
    azk:  .postgres [log] >  ERROR:  role "kim" does not exist
    looks like -O -x gets rid of that tho
    Dr Kim Foale
    @kimadactyl
    anddd we are in business :D
    Dr Kim Foale
    @kimadactyl
    hmm now getting prompted for a login when i try and deploy. strange.
    getting prompted for "git@104.131.52.85's password:"
    so happy to get this working locally tho, got a few js related glitches but can get to them
    PR: azukiapp/docker-postgres#4
    Dr Kim Foale
    @kimadactyl
    ok gotta run out but now fixing those two things: 1, javascript not loading, perhaps due to rack-livereload. 2, getting this login prompt for deploy when it was working before (weird)
    Gullit Miranda
    @gullitmiranda
    hi @kimadactyl. thanks for the PR. I did merge them
    about javascript not loading. you already has checked the ignores?
    http://docs.azk.io/en/reference/azkfilejs/mounts.html#opts-optional
    about ssh: your ssh key has a password? another important thing to check is if it is mounted correctly in the system deploy
    Dr Kim Foale
    @kimadactyl
    ook about to get going on this
    hmm. i think im not quite clear how i should develop on this and what environment goes where. should i be doing my dev within the azk shell now? feel like idprefer to stick with my existing toolkit and just use azk for deploy
    ssh key shouldn't have a password. i followed the instructions on the digital ocean tutorial using an API key. it used to work, now doesn't.hmm
    the mount thing im shaky on tho, do you mean the ssh agent?
    Dr Kim Foale
    @kimadactyl
    and weird.im now getting this after a restart. cant figure out whats changed for the life of me. tried a bunch of old branches, no luck
    azk: ↓ stopping `postgres` system, 1 instances...
    azk: Run system `taichi-school` return: (1), for command: ["bundle","exec","rails","server","--pid","/tmp/rails.pid","--port=3000","--binding=0.0.0.0"]:
    azk:  .taichi-school [log] >  => Booting Puma
    azk:  .taichi-school [log] >  => Rails 4.2.6 application starting in development on http://0.0.0.0:3000
    azk:  .taichi-school [log] >  => Run `rails server -h` for more startup options
    azk:  .taichi-school [log] >  => Ctrl-C to shutdown server
    azk:  .taichi-school [log] >  Exiting
    azk:  .taichi-school [log] >  /azk/bundler/ruby/2.3.0/gems/railties-4.2.6/lib/rails/application/configuration.rb:115:in `rescue in database_configuration': YAML syntax error occurred while parsing /azk/taichi_rails/config/database.yml. Please note that YAML must be consistently indented using spaces. Tabs are not allowed. Error: (<unknown>): could not find expected ':' while scanning a simple key at line 11 column 1 (RuntimeError)
    grrrrrrrrrrrrrrr
    not changed that database file, not sure whats going on
    Dr Kim Foale
    @kimadactyl
    pretty sure for some reason its not executing the erb now
    Dr Kim Foale
    @kimadactyl
    yup im totally bewildered. gonna make lunch will check back soon. current azkfile https://gist.github.com/kimadactyl/098d87c0a8abedf1bfa1
    Dr Kim Foale
    @kimadactyl
    yeah idk whats going on, gone back a fair way and same problem
    uffff
    Dr Kim Foale
    @kimadactyl
    you around today @gullitmiranda ? :)
    Lucas Gertel
    @lgertel
    Possible to use azk with private repos on Github?
    Dr Kim Foale
    @kimadactyl
    what do you mean?azk doesnt really care about where you store things :)
    Dr Kim Foale
    @kimadactyl
    oh man i tried a purge as this makes zero sense and now everything messing up :( ill wiat for you to be back
    Gullit Miranda
    @gullitmiranda
    hi @kimadactyl. I'm back =D
    I'm going to review everything that you sent.