Closed sbrl closed 5 years ago
Once it's setup, we'll want to add a "try the beta!" button.
We'll also want to make sure that the localStorage
values for the beta don't clash with the production version.
Clearly the error is a permissions thing. (File "data/settings.toml" cannot be read.)
Not sure about try the beta button - makes it easier to get too but since the interface is public would you want, potentially, 100s of hits throwing up potential errors? Perhaps just message @channel, when a new beta is available, with a link.
Definitely should have a beta site but like Brian, think it's address should be invisible and given only to the people we want to invite. No security required but no encouragement for lots of people to try something before it is reasonably tested. The location we are discussing is more like an alpha test than a beta. Who knows - we maybe need both.
I had similar thoughts re-alpha/beta they can share the same database.
Hmmm, perhaps.
Yeah, really I mainly opened this issue at all because it was late last night and I wanted to go to bed, but also wanted to note the error message down for later pondering :P
And fixed! The new beta version is now live over here:
I assume this is using the live database at the moment.
Indeed it is, @BNNorman. We should open another issue about a testing DB I think.
A staged rollout is the best approach I think.
We should setup a beta testing version of this web interface that runs the very latest from the
dev
branch.Much of the work to do this has already been completed (you can see the WIP here, but currently we're getting an error in the logs:
I've had this before when setting up the production version, but I can't for the life of me remember what the solution was right now. I'll have to think on it and come back to it.
It probably doesn't help that we're dealing with multiple levels of symbolic links, which are probably complicating matters somewhat here.