search

interledger-deprecated / ilp-kit-docker-compose

Deploy a complete ILP Kit in one command
3 stars 5 forks source link

fix: add CONNECTOR_AUTOLOAD_PEERS to true #11

Closed michielbdejong closed 7 years ago

michielbdejong commented 7 years ago

This variable defaults to true in ilp-kit-cli, but to false in ilp-connector, that's why it needs to be added here explicitly. The app.json (for heroku deploy), and dev/test env.list also all have it like this.

michielbdejong commented 7 years ago

Same for CONNECTOR_MAX_HOLD_TIME, see https://github.com/interledgerjs/ilp-kit-cli/blob/master/src/configure.js#L121

ghost commented 7 years ago

I had to run $ sudo service nginx stop when I encountered error



ERROR: for letsencrypt  Cannot start service letsencrypt: driver failed programming external connectivity on endpoint letsencrypt (af4c7e991b327b5d7271a818b8a3e2d3203ad1d4dd04307ff2
6a7b08d2392e1a): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
ERROR: Encountered errors while bringing up the project.```

After that the homepage to login launched properly to
http://grifiti.web-payments.net:3010/login
but GUI buttons were unresponsive.
michielbdejong commented 7 years ago

@peterjkrey good point! moved your remark to a separate issue

ghost commented 7 years ago

Enougn `pkrey@supermicro4u:~/ilp-kit-docker-compose$ ILP_DOMAIN='grifit.web-payments.net' ILP_EMAIL='peterjkrey@gmail.com' ILP_CURRENCY='USD' ILP_SECRET='3ABRFSNHXKLoCa552yrZGPMlRSsF0XflsUkssOFK9j4' docker-compose up -d ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable. pkrey@supermicro4u:~/ilp-kit-docker-compose$`

Command to launch on README needs to be prepended with sudo pkrey@supermicro4u:~/ilp-kit-docker-compose$ sudo ILP_DOMAIN='grifit.web-payments.net' ILP_EMAIL='peterjkrey@gmail.com' ILP_CURRENCY='USD' ILP_SECRET='3ABRFSNHXKLoCa552yrZGPMlRSsF0XflsUkssOFK9j4' docker-compose up

Ran fine.

michielbdejong commented 7 years ago

Command to launch on README needs to be prepended with sudo

That depends on how you installed docker, the recommended way is to add your own user to the docker group, so you don't need to use sudo

sharafian commented 7 years ago

Won't it need root privilege to bind port 443/80 ?

michielbdejong commented 7 years ago

the docker-compose command doesn't open a port, it just talks to the docker daemon, see https://docs.docker.com/engine/installation/linux/linux-postinstall/ for more info on running docker client as a non-root user.