esitarski/RaceDB

"Localhost" share not possible

Closed this issue · 5 comments

Try to share DB access to another laptop on same network, but no access granted. Changed "Localhost" with main laptop ip address, but still no access possible. Before I moved over to the docker network, I was able to share access for example (http://192.168.0.1:8000/RaceDB/) to another laptop on the same network in order for that person to capture info or assist with registration.

One of the benefit of docker is one can assign the port to which a website can respond to anything. By default, port 80 is mapped to port 8000 in the container:

ports:
- "80:8000"

Point your clients on your local network to http://192.168.0.1 - http is port 80 by default. No need to specify a port (and I even set a redirect /RaceDB because I got annoying to have to attempt to type that in on a iPad).

I've used this setup in a race environment, so it does work. Used laptops and tablets for "staff" to help with reg.

In my browser the server link is: http://localhost:8000/RaceDB/ - did I set it up wrong when I installed the docker? I tried to access: http://192.168.0.1/RaceDB/ but no luck.

How did you install RaceDB? Using the racedbcontroller (windows) to get the docker image? or did you install it the old way from source code? The docker image won't respond to port 8000 on the local system or anywhere else.

Also, if you are using Windows, you might have to open up the firewall to allow external systems to connect (or just turn it off).

If you respond, please give full details of you setup (how you installed racedb, one what system, version of docker desktop if using that, etc..).

Thank you and I manage to sort this out (my knowledge of networks and network addresses were not so good). The quick solution is to open a CMD window and run 'ipconfig'. The Wireless LAN Adapter Wifi: IPv4 Address = Localhost address. Once I inserted that address in the address field and shared, the local RaceDB could be accessed by other laptops and assist with registration. I am closing this issue now.