They're not perfect, I still don't like them, but I can't think of a
good solution right now. I'm going to thinking about the best way of
doing web stuff for some time.
There is a new config field: Authorization.Locked.
I am a little bit sorry for how actually the lock is implemented. I've added the check on almost every handler there is. Good luck maintaining that ❤️
It allows for interactive creation of admin account from the terminal
for new wikis. Because we have a chicken-and-egg problem here with the
user panel -- you need an admin account to appoint someone as an admin,
right?
Important changes:
- UseFixedAuth is now UseAuth and toggles all kinds of authorization and
registration
- UseRegistration is now AllowRegistration to better reflect the meaning
- LimitRegistration is now RegistrationLimit because it's not a boolean,
it's a value (not "limit registration?", but "registration limit is
...")
- registered-users.json is now users.json, because all users are stored
there
- user.AuthUsed is dropped in favor of new cfg.UseAuth which has the
same meaning
I hope I have not forgotten anything.
Store it at the static folder, like before.
I created a new config field for that originally, but then I understood that it is to be thrown away anyway when the Structure comes, so decided to keep it the old way.
assets.qtpl is no more! Now you can just add files to static/ folder,
make sure the extension is registered in static.go (a shortcoming
that'll be addressed in future Go versions), and you're done! It
searches the local file system first, then falls back to the files
embedded with the binary (in the static/ folder).
