Hello MRBS developers,
We are a library of a large urban university. We would like to
use MRBS to track instructional lab room bookings.
We would like to expose the bookings for read-only to the public
Internet on port 80 outside our institutional firewall, like
but we do not want port 80 to allow any login prompts at all.
All login prompts for schedule editing should be handled inside
the firewall on another port, say
So is stock MRBS authentication intended to work this way? I'm
wondering if essentially two websites would be the answer: One
on port 80, the other on port 8080, both pointed to the same
database, with the port 80 site run with all user support shut
down? Then the 8080 site answers for schedule editing..? Would
there be any problem with database conflict between two such
ganged MRBS websites?
My skill set with web servers is very small, so please forebear!
Thank you very much..
-- Calvin Miracle, UofL Libraries