These are chat archives for azukiapp/azk

15th
Feb 2016
Bartek Kus
@Bartekus
Feb 15 2016 00:42
ok, scrap that, I’ve restarted from the begining, using digitalocean this time, however I’m having problem with installing the build…. is that a sure way to purge the containers node_modules and force reinstall?
Bartek Kus
@Bartekus
Feb 15 2016 01:17

ahh

$ azk shell r3stack -- rm -rf ./node_modules/*
$ azk start -Rvvvv

this did the trick :D

Bartek Kus
@Bartekus
Feb 15 2016 02:39
nope… so close, yet so far away lol
 Bart@Araphel~/Dev/BIN/ZONE/r3stack   master ● ?  azk start                                                                                          ✓  10152  19:26:32
azk: ↑ starting `rethinkdb` system, 1 new instances...
azk: ✓ checking `library/rethinkdb:latest` image...
azk: ◴ waiting for `rethinkdb` system to start, trying connection to port http/tcp...
azk: ↑ starting `r3stack` system, 1 new instances...
azk: ✓ checking `azukiapp/node:latest` image...
azk: ⎘ syncing files for `r3stack` system...
azk: ◴ waiting for `r3stack` system to start, trying connection to port http/tcp...
azk: Run system `r3stack` return: (1), for command: ["npm","run","start"]:
azk:  .r3stack [log] >  npm info it worked if it ends with ok
azk:  .r3stack [log] >  npm info using npm@3.3.12
azk:  .r3stack [log] >  npm info using node@v5.2.0
azk:  .r3stack [log] >  npm info lifecycle r3stack@1.0.0~prestart: r3stack@1.0.0
azk:  .r3stack [log] >  npm info lifecycle r3stack@1.0.0~start: r3stack@1.0.0
azk:  .r3stack [log] >
azk:  .r3stack [log] >  > r3stack@1.0.0 start /azk/r3stack
azk:  .r3stack [log] >  > NODE_ENV=production node ./src/server
azk:  .r3stack [log] >
azk:  .r3stack [log] >  /azk/r3stack/node_modules/babel-core/lib/transformation/file/logger.js:41
azk:  .r3stack [log] >      throw new Constructor(this._buildMessage(msg));
azk:  .r3stack [log] >      ^
azk:  .r3stack [log] >
azk:  .r3stack [log] >  ReferenceError: [BABEL] /azk/r3stack/src/server/server.js: Unknown option: base.Children
azk:  .r3stack [log] >      at Logger.error (/azk/r3stack/node_modules/babel-core/lib/transformation/file/logger.js:41:11)
azk:  .r3stack [log] >      at OptionManager.mergeOptions (/azk/r3stack/node_modules/babel-core/lib/transformation/file/options/option-manager.js:289:18)
azk:  .r3stack [log] >      at OptionManager.init (/azk/r3stack/node_modules/babel-core/lib/transformation/file/options/option-manager.js:486:10)
azk:  .r3stack [log] >      at File.initOptions (/azk/r3stack/node_modules/babel-core/lib/transformation/file/index.js:211:75)
azk:  .r3stack [log] >      at new File (/azk/r3stack/node_modules/babel-core/lib/transformation/file/index.js:129:22)
azk:  .r3stack [log] >      at Pipeline.transform (/azk/r3stack/node_modules/babel-core/lib/transformation/pipeline.js:48:16)
azk:  .r3stack [log] >      at Object.transformFileSync (/azk/r3stack/node_modules/babel-core/lib/api/node.js:118:10)
azk:  .r3stack [log] >      at compile (/azk/r3stack/node_modules/babel-register/lib/node.js:100:20)
azk:  .r3stack [log] >      at loader (/azk/r3stack/node_modules/babel-register/lib/node.js:128:14)
azk:  .r3stack [log] >      at Object.require.extensions.(anonymous function) [as .js] (/azk/r3stack/node_modules/babel-register/lib/node.js:138:7)
azk:  .r3stack [log] >
azk:  .r3stack [log] >  npm info lifecycle r3stack@1.0.0~start: Failed to exec start script
azk:  .r3stack [log] >  npm ERR! Linux 3.16.0-4-amd64
azk:  .r3stack [log] >  npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
azk:  .r3stack [log] >  npm ERR! node v5.2.0
azk:  .r3stack [log] >  npm ERR! npm  v3.3.12
azk:  .r3stack [log] >  npm ERR! code ELIFECYCLE
azk:  .r3stack [log] >  npm ERR! r3stack@1.0.0 start: `NODE_ENV=production node ./src/server`
azk:  .r3stack [log] >  npm ERR! Exit status 1
azk:  .r3stack [log] >  npm ERR!
azk:  .r3stack [log] >  npm ERR! Failed at the r3stack@1.0.0 start script 'NODE_ENV=production node ./src/server'.
azk:  .r3stack [log] >  npm ERR! Make sure you have the latest version of node.js and npm installed.
azk:  .r3stack [log] >  npm ERR! If you do, this is most likely a problem with the r3stack package,
azk:  .r3stack [log] >  npm ERR! not with npm itself.
azk:  .r3stack [log] >  npm ERR! Tell the author that this fails on your system:
azk:  .r3stack [log] >  npm ERR!     NODE_ENV=production node ./src/server
azk:  .r3stack [log] >  npm ERR! You can get their info via:
azk:  .r3stack [log] >  npm ERR!     npm owner ls r3stack
azk:  .r3stack [log] >  npm ERR! There is likely additional logging output above.
azk:  .r3stac
Gullit Miranda
@gullitmiranda
Feb 15 2016 18:01
@Bartekus in deploy system the path is /azk/deploy/.ssh:
azk deploy ssh
ls -alh /azk/deploy/.ssh/
@Bartekus about npm Err!: I believe that is happening any problem in the premises of the dependencies.
Gullit Miranda
@gullitmiranda
Feb 15 2016 18:07
@quintanilhar your application has the folder ./public?
the entrypoint of the image of the php-fpm is a "magic" to create dynamic nginx.conf file.
check the entrypoint to more details: https://github.com/azukiapp/docker-php-fpm/blob/master/5.6%2Frun.sh
Bartek Kus
@Bartekus
Feb 15 2016 22:36
I’m fairly certain that after switching to digital ocean the deployment is working despite the fact that
azk deploy ssh
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-71-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

  System information as of Sun Feb 14 19:57:14 EST 2016

  System load:  0.09               Processes:              93
  Usage of /:   10.2% of 39.25GB   Users logged in:        0
  Memory usage: 20%                IP address for eth0:    xxx.xxx.xx.xx
  Swap usage:   0%                 IP address for docker0: xxx.17.0.1

  Graph this data and manage this system at:
    https://landscape.canonical.com/

git@r3stack:~$ ls -alh /azk/deploy/.ssh/
ls: cannot access /azk/deploy/.ssh/: No such file or directory

when I go to the ip of my server I get:

No Application Configured

This domain is not associated with an application.

which to me means that the deploy is working fine, but the installation and the operation now is not

azk start now give me:
 Bart@Araphel~/Dev/BIN/ZONE/r3stack   master ● ?  azk start                                                                                        3 ↵  10180  15:30:42
azk: ↑ starting `rethinkdb` system, 1 new instances...
azk: ✓ checking `library/rethinkdb:latest` image...
azk: ◴ waiting for `rethinkdb` system to start, trying connection to port http/tcp...
azk: ↑ starting `r3stack` system, 1 new instances...
azk: ✓ checking `azukiapp/node:latest` image...
azk: ⎘ syncing files for `r3stack` system...
azk: ◴ waiting for `r3stack` system to start, trying connection to port http/tcp...
azk: Run system `r3stack` return: (1), for command: ["npm","run","start"]:
azk:  .r3stack [log] >  npm info it worked if it ends with ok
azk:  .r3stack [log] >  npm info using npm@3.3.12
azk:  .r3stack [log] >  npm info using node@v5.2.0
azk:  .r3stack [log] >  npm info lifecycle r3stack@1.0.0~prestart: r3stack@1.0.0
azk:  .r3stack [log] >  npm info lifecycle r3stack@1.0.0~start: r3stack@1.0.0
azk:  .r3stack [log] >
azk:  .r3stack [log] >  > r3stack@1.0.0 start /azk/r3stack
azk:  .r3stack [log] >  > NODE_ENV=production node ./src/server
azk:  .r3stack [log] >
azk:  .r3stack [log] >  /azk/r3stack/node_modules/babel-core/lib/transformation/file/logger.js:41
azk:  .r3stack [log] >      throw new Constructor(this._buildMessage(msg));
azk:  .r3stack [log] >      ^
azk:  .r3stack [log] >
azk:  .r3stack [log] >  ReferenceError: [BABEL] /azk/r3stack/src/server/server.js: Unknown option: base.Children
azk:  .r3stack [log] >      at Logger.error (/azk/r3stack/node_modules/babel-core/lib/transformation/file/logger.js:41:11)
azk:  .r3stack [log] >      at OptionManager.mergeOptions (/azk/r3stack/node_modules/babel-core/lib/transformation/file/options/option-manager.js:289:18)
azk:  .r3stack [log] >      at OptionManager.init (/azk/r3stack/node_modules/babel-core/lib/transformation/file/options/option-manager.js:486:10)
azk:  .r3stack [log] >      at File.initOptions (/azk/r3stack/node_modules/babel-core/lib/transformation/file/index.js:211:75)
azk:  .r3stack [log] >      at new File (/azk/r3stack/node_modules/babel-core/lib/transformation/file/index.js:129:22)
azk:  .r3stack [log] >      at Pipeline.transform (/azk/r3stack/node_modules/babel-core/lib/transformation/pipeline.js:48:16)
azk:  .r3stack [log] >      at Object.transformFileSync (/azk/r3stack/node_modules/babel-core/lib/api/node.js:118:10)
azk:  .r3stack [log] >      at compile (/azk/r3stack/node_modules/babel-register/lib/node.js:100:20)
azk:  .r3stack [log] >      at loader (/azk/r3stack/node_modules/babel-register/lib/node.js:128:14)
azk:  .r3stack [log] >      at Object.require.extensions.(anonymous function) [as .js] (/azk/r3stack/node_modules/babel-register/lib/node.js:138:7)
azk:  .r3stack [log] >
azk:  .r3stack [log] >  npm info lifecycle r3stack@1.0.0~start: Failed to exec start script
azk:  .r3stack [log] >  npm ERR! Linux 3.16.0-4-amd64
azk:  .r3stack [log] >  npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
azk:  .r3stack [log] >  npm ERR! node v5.2.0
azk:  .r3stack [log] >  npm ERR! npm  v3.3.12
azk:  .r3stack [log] >  npm ERR! code ELIFECYCLE
azk:  .r3stack [log] >  npm ERR! r3stack@1.0.0 start: `NODE_ENV=production node ./src/server`
azk:  .r3stack [log] >  npm ERR! Exit status 1
azk:  .r3stack [log] >  npm ERR!
azk:  .r3stack [log] >  npm ERR! Failed at the r3stack@1.0.0 start script 'NODE_ENV=production node ./src/server'.
azk:  .r3stack [log] >  npm ERR! Make sure you have the latest version of node.js and npm installed.
azk:  .r3stack [log] >  npm ERR! If you do, this is most likely a problem with the r3stack package,
azk:  .r3stack [log] >  npm ERR! not with npm itself.
azk:  .r3stack [log] >  npm ERR! Tell the author that this fails on your system:
azk:  .r3stack [log] >  npm ERR!     NODE_ENV=production node ./src/server
azk:  .r3stack [log] >  npm ERR! You can get their info via:
azk:  .r3stack [log] >  npm ERR!     npm owner ls r3stack
azk:  .r3stack [log] >  npm ERR! There is likely additional logging out
how do I just scrap the whole thing, like erase all the files but my source and force a clean install?
Bartek Kus
@Bartekus
Feb 15 2016 22:42
I think the ask restart is great, but perhaps there could be azk reboot, which basically scraps everything but the config files and rebuild everything from the ground up. Since at this point everything is good to deploy and should be working, but discrapencies within the docker are causing the installation/opperation to fail
Bartek Kus
@Bartekus
Feb 15 2016 22:53
I guess the next best thing seems to be azk start —rebuild