Welp, I think I just finished creating and testing what I like to call a Shaving Data System using Baserow (self hosted). You can manage your den and create SOTD formatted text blocks.
It also logs your shaves so you can go back and filter things like “how many times have I used synthetic brushes compared to boar”, or whatever.
It also has an option to rate your razor/blade combo, so with enough data you can sort and see your favorites.
I could set up basic authentication using Nginx Proxy Manager, but that adds some workload for me when people forget their passwords.
Authentication with 3rd party services is behind their paywall. I have very little experience setting up such things, so I’m not sure if there’s some sort of work around.
There is a bit of functionality built in already that requires users to log in for the SOTD app, but that’s going to be a v1.1 feature, if a feature at all. I looked at it briefly and it didn’t make sense to me, so it’ll require some more digging.
Welp, I think I just finished creating and testing what I like to call a Shaving Data System using Baserow (self hosted). You can manage your den and create SOTD formatted text blocks.
It also logs your shaves so you can go back and filter things like “how many times have I used synthetic brushes compared to boar”, or whatever.
It also has an option to rate your razor/blade combo, so with enough data you can sort and see your favorites.
I created an onboarding document here https://gitlab.com/walden_/shaving-data-system
Let me know if you’d like to try it, as there’s a manual process on my end to assign you a URL.
Edit: I figured out authentication for the SOTD page! Woohoo! Just have to update the template.
Very cool!
FWIW you could probably put something like Auth0, workOS, or something similar in front of the individual frontends for more robust authentication.
I’m sure you’d stay well within their free tier and should be pretty straightforward to implement.
I could set up basic authentication using Nginx Proxy Manager, but that adds some workload for me when people forget their passwords.
Authentication with 3rd party services is behind their paywall. I have very little experience setting up such things, so I’m not sure if there’s some sort of work around.
There is a bit of functionality built in already that requires users to log in for the SOTD app, but that’s going to be a v1.1 feature, if a feature at all. I looked at it briefly and it didn’t make sense to me, so it’ll require some more digging.
Hey cool, I figured it out. Will update the template to enable it.
Nice! What route did you end up going with?
The built in auth functionality. It’s not very polished, but it works! I just have to update the documentation on how to set it up.