The Shaving Data System has been updated to v1.0.2. Even more brands to pick from (if you have a brand that’s not included please submit an issue on GitLab or PM me).
I also added functionality to track razor uses similar to blade uses. This will let you keep track of how many shaves since honing, etc. It displays in parentheses just like a blade count, like “Koraat Moarteen (15)”.
I have a similar tracker in Airtable that I started a few years ago, but I outgrew their free plan a while ago (4000+ rows). I’ve been looking at SeaTable, NocoDB, and Baserow to migrate my data to recently, but keep running into various limitations. I like what you are doing here with the self-hosted option.
Oh cool. I just ran across Baserow and ran with it. I did at Airtable and saw it had limitations on rows. It seems like Airtable is probably more capable/polished/has fewer bugs, but Baserow seems to work great and it’s open source, etc. Self hosting still locks down a lot of features without a subscription, but row limits isn’t a problem.
Would you mind if I played around with importing some of the data from Airtable into your Baserow instance? I’m not sure if the instance has any hard constraints, so I don’t want to just port the whole thing over.
If so, feel free to use any of that data that is pertinent for the SDS.
The Shaving Data System has been updated to v1.0.2. Even more brands to pick from (if you have a brand that’s not included please submit an issue on GitLab or PM me).
I also added functionality to track razor uses similar to blade uses. This will let you keep track of how many shaves since honing, etc. It displays in parentheses just like a blade count, like “Koraat Moarteen (15)”.
Onboarding instructions are found here https://gitlab.com/walden_/shaving-data-system
I’ll go take a look at this. I use a complex multi-sheet Excel workbook I built years ago. It tracks a lot of info that I no longer care about.
I think you’ll feel right at home with my Shaving Data System™.
I have a similar tracker in Airtable that I started a few years ago, but I outgrew their free plan a while ago (4000+ rows). I’ve been looking at SeaTable, NocoDB, and Baserow to migrate my data to recently, but keep running into various limitations. I like what you are doing here with the self-hosted option.
Oh cool. I just ran across Baserow and ran with it. I did at Airtable and saw it had limitations on rows. It seems like Airtable is probably more capable/polished/has fewer bugs, but Baserow seems to work great and it’s open source, etc. Self hosting still locks down a lot of features without a subscription, but row limits isn’t a problem.
Maybe I’ll peak at the other ones you mentioned.
Would you mind if I played around with importing some of the data from Airtable into your Baserow instance? I’m not sure if the instance has any hard constraints, so I don’t want to just port the whole thing over.
If so, feel free to use any of that data that is pertinent for the SDS.
Sure, feel free! What type of data are you referring to?
There aren’t many constraints on self-hosted Baserow… No row limits, etc. Just a bunch of other paywalled stuff.
The SSD in my server is pretty large so I don’t imagine any baserow databases making a dent.