I'm debating 1. Rolling up a Rails instance coding the minimum to meet the features 2. Looking for an open source member management system (checks on github are unsuccessful so far) 3. Paying for a monthly service.
Does anybody have any leads on points #2 or #3?
[1] - https://www.phpbb.com/
What are the two problems?
• https://blog.codinghorror.com/regular-expressions-now-you-ha...
It was a joke. I was trying to take a cheap shot at PHPBB.
I suppose another solution that is lighter weight and battle hardened, assuming one just wanted identity management would be to put Lam Pro (paid app) in front of OpenLDAP. That way you can support any extensions required.
for several reasons:
- looking for this kind of software (and most kinds) sucks
- these systems always seem overpriced
- they never seem to do what you want
- while they always do way too much
- community gardens are cool, so deserve their own type of system
- airtable and the like are awful (imo), unless you truly need them
- you can open-source the software if that's your thing
- and you can provide the .com saas hosting if that's your thing
i did a quick look for multi-tenant ruby saas boilerplate, and saw the usual list of things that don't quite do that, but all of them seem to do at least single-tenant -- and prob most would claim they do multi-tenant if you just add 5 or 50 hours of dev:
i don't know anything about these particular guys.
but my thinking is, you can get to (what seems like) 80 or 90% in a few hours, but that final 20 or 10% takes 50 hours more, plus ongoing maintenance/support/etc.
i'd pledge $5 at six months from now (possibly more) to see it done - just to try to kickstart it.
Disclaimer: I am the developer.
I'd say that coding something custom is likely to be a big ongoing burden unless it's really simple.
- admins --> ability to assign gardens, create users - users --> can log into their account and see the status of their account, which garden they are assigned to, and if they are in good standing