β New space
A customer's own campus: a display name, an id for the link, a note for you. The id is the door β
/c/acme β and it never changes unless you change it. Each space keeps its own
state β its map, its crowd, its locks β from the moment it is made.
Which maps β tick the ones to bring; doorways between them are re-joined here
β loading the spaceβ¦ β
ποΈ What this space has, and who may run it
What this space has
Switched off means off β the campus refuses it, not just hides the button. Every space made
before this keeps everything on.
Passwords for this space
Each one opens the host desk and the Maker for THIS space only, never the campus itself.
Leave a box empty and no password is made. At least 10 characters.
A custom domain. The door works under any domain pointed at this app. On Heroku:
heroku domains:add campus.yourdomain.com, then a CNAME at your registrar to the DNS target it prints,
and Heroku's ACM issues the certificate. After that a customer's link reads
https://campus.yourdomain.com/c/acme-q4. (This page cannot do that step for you β it is your Heroku account and your DNS.)
π« Spaces
Each row is one persistent campus. Live means it is in memory right now with people in it; a space nobody is in is put to sleep and wakes the moment its link is followed β nothing is lost.
π Unnamed rooms
Campuses opened from a plain "open the campus" link, by random id. Name one to turn it into a space (its id stays, it gets a /c/ door). Each one is a saved document in the database (its locks, chat, where its pickups lie) β a few kilobytes apiece, and nothing keeps them but you: delete the ones nobody uses.