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

Provide a docker-compose.yml #63

Open
jtagcat opened this issue Dec 26, 2020 · 8 comments
Open

Provide a docker-compose.yml #63

jtagcat opened this issue Dec 26, 2020 · 8 comments

Comments

@jtagcat
Copy link

jtagcat commented Dec 26, 2020

I'm quite sure the container needs to communicate with the outside world, but how? Is it supposed to be on a domain somewhere? Can I put it behind a reverse proxy? Port 80, 8000, 8080? How do the CLI/GUI apps communicate with the server part?

@jtagcat
Copy link
Author

jtagcat commented Dec 26, 2020

Running /app/main config create, or the default server start doesn't do anything in the mentioned.

Looking at logs, it tries connecting to a localhost db, what doesn't obviously exist. The location could probably be changed in configs, but I still haven't found a config. Can't jump in to the container either, as it's in a restart loop.

@jtagcat
Copy link
Author

jtagcat commented Dec 26, 2020

Seems we need /app/data in addition to /app/files

@jtagcat
Copy link
Author

jtagcat commented Dec 26, 2020

Ok, I've reached the highly illegal dark web. Nice.

@jtagcat
Copy link
Author

jtagcat commented Dec 26, 2020

new user created, stats gives 404

@jtagcat
Copy link
Author

jtagcat commented Dec 26, 2020

it's still overwhelming to see the structure, intended use.. even though I have interacted with tds, my own, and other fs-s.

@jtagcat
Copy link
Author

jtagcat commented Dec 26, 2020

Other instances spotted https://files.jojii.de https://very.highly.illegal-dark-web-server.xyz are 502
looking at commit history, seems kind of a dead project

using it myself sounds like maintaining it

@jtagcat
Copy link
Author

jtagcat commented Dec 26, 2020

notes to self at this point..

@JojiiOfficial
Copy link
Member

Those instances are the same. The 502 is caused by another unrelated error I've been too lazy to fix. It is still maintained, but simply not that actively developed anymore like before.
I haven't touched the docker container for a while so I can't tell you just now what you missed. It's probably time to rework the Readme. If you have suggestions, feel free to share your ideas but please keep it in one comment.

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

2 participants