@robertgendler commented on GitHub:
Updated with stderr redirect
@stefanbenten commented on GitHub:
We could make it so that the binary per default listens on 8080 without specifying the flag at all, right? Then setting the env variable should help, or one…
@stefanbenten commented on GitHub:
Issue is fixed. A new account limit on the Storj backend was introduced, causing uploads to fail.
@wisinfun commented on GitHub:
hello @wisinfun , not sure I understand what you mean
like this,It would be better to have a search box <img width="1401" alt="CleanShot 2022-04-05 at 14 24…
@paolafrancesca commented on GitHub:
I was aware of the hardcoded listener value before in the Dockerfile and not so happy about it but I didn't want to remove since it could break a lot of…
@paolafrancesca commented on GitHub:
the problem is that such feature makes sense only in self-hosted and single upload user case
@stefanbenten commented on GitHub:
Hello @flavorgold1,
the port is fixed inside of the container, see here: https://github.com/dutchcoders/transfer.sh/blob/b30b296ac838c73a4bcb83e394e6d9dac1b7…
@paolafrancesca commented on GitHub:
hello @wisinfun , not sure I understand what you mean
@flavorgold1 commented on GitHub:
I understand that but, I'm in a situation where I have to use network_mode: host in docker-compose.yml. So, if there's a way through which it can respect…
@paolafrancesca commented on GitHub:
ENTRYPOINT ["/go/bin/transfersh"]
cli.StringFlag{
Name: "listener",
Usage: "127.0.0.1:8080",
Value: ":8080",
EnvVar:…
@paolafrancesca commented on GitHub:
doh @flavorgold1
I did't think about the most obvious solution: overriding the entrypoint (either on docker-compose or with --entrypoint on docker…