Problems accessing MusicBrainz over local network

jesus2099 · December 5, 2020, 12:51pm

I need to change all //localhost:5000/ generated links to either //192.168.0.99:5000/:

Or, even better, to just /:

Even if I prefer the patch, to test it quicker first, I changed musicbrainz-server/lib/DBDefs/Default.pm:

metabrainz/musicbrainz-server/blob/d26817421ff6a632821a220c271221a43afc1793/lib/DBDefs/Default.pm#L102


      
          
          ################################################################################
          # HTTP Server Names
          ################################################################################
          
          # The host names used by the server.
          # To use a port number other than 80, add it like so: "myhost:8000"
          # Additionally you should set the environment variable
          # MUSICBRAINZ_USE_PROXY=1 when using a reverse proxy to make the server
          # aware of it when generating things like the canonical url in catalyst.
          sub WEB_SERVER                { "localhost:5000" }
          # Relevant only if SSL redirects are enabled
          sub WEB_SERVER_SSL            { "localhost" }
          sub SEARCH_SERVER             { "search.musicbrainz.org" }
          sub SEARCH_ENGINE             { "SOLR" }
          # Whether to use x-accel-redirect for webservice searches,
          # using /internal/search as the internal redirect
          sub SEARCH_X_ACCEL_REDIRECT   { 0 }
          # Used, for example, to have emails sent from the beta server list the
          # main server
          sub WEB_SERVER_USED_IN_EMAIL  { my $self = shift; $self->WEB_SERVER }

~~sub WEB_SERVER { "localhost:5000" }~~
sub WEB_SERVER { "192.168.0.99:5000" }

Then I restarted sudo docker-compose up but it was not enough.
What do I need to do first, so that my change to Default.pm is taken into account?

Would it be the same action for the @yvanzo patch to be taken into account, as well?

Sorry for newbie questions.