Please describe the problem.
reprostim@reproiner:/data/reprostim/Videos$ ps auxw | grep webapp
reprost+ 25249 0.0 0.0 9892 2100 pts/5 S+ Jan05 0:00 git annex --debug webapp --listen 0.0.0.0:8888
reprost+ 25250 5.4 0.2 1074346616 65556 ? Ssl Jan05 60:39 /usr/bin/git-annex --debug webapp --listen 0.0.0.0:8888
reprost+ 224039 0.0 0.0 6332 2116 pts/6 S+ 10:55 0:00 grep webapp
reprostim@reproiner:/data/reprostim/Videos$ lsof -i :8888
reprostim@reproiner:/data/reprostim/Videos$ lsof -i | grep git-annex
git-annex 25250 reprostim 14u IPv4 129033 0t0 UDP *:55556
git-annex 221230 reprostim 14u IPv4 129033 0t0 UDP *:55556
reprostim@reproiner:/data/reprostim/Videos$ git annex version
git-annex version: 10.20230126
done --Joey
--listen takes an IP address (or hostname), it does not let you specify the port. I've clarified the documentation about this.
I don't reproduce the behavior you show, when I try that the process runs but does not bind to any port, and in .git/annex/daemon.log, I see:
This may be an OS or resolver difference. If "0.0.0.0:8888" somehow resolves to an IP address on your system, then the webapp will listen on that IP address I suppose. But it's not expecting that to specify a port.
The webapp outputs the full url, including the port it chose. Since that url also includes an auth token that is required to use the webapp, specifying the port for it to listen on does not seem very useful.
What's your use case for wanting to specify a port?
it was to have some static port I could keep an ssh redirect pointing to so I could investigate behavior of the remote running annex webapp.
My 1c: Since AFAIK no ADDRESS could have
:(unless somesshbased "server:/path/to/socket" which I do not think supported) so might be better to just crash (not just have it a matter of documentation) if:\d+part is found to be specified?IPv6 would beg to differ about
:\d+Actually, it may be that your address:port was treated as some IPv6 mixed IPv4, iirc something like that is a thing.
You would still need to copy over the url though to get the access key for the webapp..
I found an old todo about the same thing, Make webapp port configurable.
The idea there was, they were using docker and wanted to open only a specific port selected for the webapp. So basically the same kind of thing.
I think that this should be a separate --port option, to avoid needing to try to parse something that may be an ipv6 address or hostname, or whatever.
I don't think that using --port should prevent the webapp from needing the `?auth=' part of the url, as output when using --listen.
Probably it does not make sense to use --port without also using --listen, but if the user does use it, I don't think --port needs to output the url the way --listen does.