BUG: Expose a way to specify custom port while starting riven in docker #925
Comments
arao
added a commit
to arao/riven
that referenced
this issue
Dec 1, 2024
…ariable This is useful if multiple instance of riven are require to run in same space. One such usecase is to have separate instance for separate torrent profiles. In current setting space, multiple profiles cannot be specified. [Testing] - Changes tested by running two separate instance in same space at different port folders
arao
added a commit
to arao/riven
that referenced
this issue
Dec 7, 2024
…ariable This is useful if multiple instance of riven are require to run in same space. One such usecase is to have separate instance for separate torrent profiles. In current setting space, multiple profiles cannot be specified. [Testing] - Changes tested by running two separate instance in same space at different port folders
arao
added a commit
to arao/riven
that referenced
this issue
Dec 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
entrypoint.shcurrently does not pass down port information to server. Add a way to pass down port number to actual server.The text was updated successfully, but these errors were encountered: