Closed ROBOKiTTY closed 4 years ago
Fresh install of CoffeeMUD, build and start server, go to http://localhost:27777/pub, click play now. 404 due to pathing/files not found, the issue being "/siplet/*" is expected when those files are in the same directory and not reachable with that pathing.
OK, want to make sure that I haven't already fixed this some other way... as I can't repro this quite yet.
First off, "http://localhost:27744/pub", by itself, SHOULD give a 404, because /web/pub/ is the root of the 27744 directory, and thus "http://localhost:27744/pub" should attempt to access the path /web/pub/pub/, which doesn't exist.
Do you have this line in your pub.ini file? MOUNT/=/web/pub/
Also, I have to ask: Are you using the SUN Java JVM, and not the OpenJVM? Weird unreproduceable problems have followed OpenJVM with CoffeeMud since the day it was invented.
Oh, it does give a 404 on the 27744 port. I've been accessing it via a link from Grinder homepage on port 27777, which links to http://localhost:27777/pub/. If I go to http://localhost.27744 and click Play NOW, then the original pathing works as well as the updated pathing in this pull request.
Is accessing via http://localhost:27777/pub/ not intended? If so, this PR is probably unnecessary, and only the links in /web/admin/index.cmvp need to be fixed.
To answer the other questions, MOUNT/=/web/pub/ is there as a default option. I'm using the Sun/Oracle JVM on JDK-14, running on a fresh copy of the repo from git.
I'm actually still using the stock pub.ini file settings. Besides, MOUNT/siplet=/siplet/ wouldn't work for me, since I don't have a /opt/coffeemud/siplet directory
Remember, the right-side of that mount "equation" is a full path from the Coffeemud root.
Oh, crap, I'm getting confused .. you are accessing 27777 -- the admin port. You are supposed to access 27744 to get to the public pages. try http://localhost:27744/ and then hit play
All the links to the public pages in /web/admin/index.cmvp point to host:27777/pub, so that's how I ended up there.
27744 works with both the original file paths and the paths in this PR.
This will be fixed in the next build -- checkin' coming soon.
If there's a bug or problem associated with this change, can you fill me in on how to recreate it?
On 4/12/2020 5:41 AM, ROBOKiTTY wrote: