You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll leave this here. Don't know where else I should go with it. I'm working on a website for my extended families shared vacation home. It's intended to host a bunch of basic administrative infos, as well as periodic updates and a collection of email addresses and phone numbers of all parties involved.
As of now we have a general site-wide password in place. This works ok, but security is admittedly very low. Is there a simple FOSS way of implementing user profiles for a case like this? Imo this would make it quite a bit more secure. Not too sure where I should start. There are some payed wordpress-like options which I would very much like to avoid.
Any opinions?
All the best.
The text was updated successfully, but these errors were encountered:
If you are willing to do a little coding yourself, I already have CSRF, users, and sessions done on my minimal Go web framework. I think you could adapt what I made fairly easily to support a staff role and protect pages based on if the current user is staff or not.
Edit) You'll want to just clone the current master branch. It has gotten better since the last release.
Hi all,
I'll leave this here. Don't know where else I should go with it. I'm working on a website for my extended families shared vacation home. It's intended to host a bunch of basic administrative infos, as well as periodic updates and a collection of email addresses and phone numbers of all parties involved.
As of now we have a general site-wide password in place. This works ok, but security is admittedly very low. Is there a simple FOSS way of implementing user profiles for a case like this? Imo this would make it quite a bit more secure. Not too sure where I should start. There are some payed wordpress-like options which I would very much like to avoid.
Any opinions?
All the best.
The text was updated successfully, but these errors were encountered: