Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

127.0.0.1 #52

Open
daw0lverine opened this issue May 25, 2019 · 2 comments
Open

127.0.0.1 #52

daw0lverine opened this issue May 25, 2019 · 2 comments

Comments

@daw0lverine
Copy link

Running this inside a docker and couldn't access the webui because the flask setup refers to 127.0.0.1 which I think is only possible for running on the same PC
Changed to 0.0.0.0 works for me, maybe expose the config ? Could be good to expose the port as well

@mettamyron
Copy link

mettamyron commented Jul 7, 2019

How do I map the download path on my host?
I have a config.txt file with
PUTIO_SYNC_TOKEN=MYTOKEN
PUTIO_SYNC_ARGS=-f /Movies/*
/volumes/putio_download=C:

And I pass this into my docker run
docker run --env-file=config.txt putio-sync

But the files don't seem to to be saved anywhere (even though the put.io shows that the have been downloaded).

@mszoernyi
Copy link

You mount a volume and use that one as value for the environment variable. i.e. /volume1/docker/putio-sync/conf:/volume/conf and then set the env PUTIO_SYNC_SETTINGS_DIR to /volume/conf

version: "3.6"

services:
  putiosync:
    container_name: putiosync
    build: ./putio-sync
    restart: always
    volumes:
      - /volume1/media-center/downloads:/volume/putio_download
      - /volume1/docker/putio-sync/conf:/volume/conf
    ports:
      - "7001:7001/tcp"
    environment:
      PUTIO_SYNC_TOKEN: "..."
      PUTIO_SYNC_SETTINGS_DIR: "/volume/conf"
      PUTIO_SYNC_ARGS: "-q -w /volume/putio_download --temp-dir /volume/putio_download --log /volume/conf/putiosync.log"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants