Hi!

I am an embedded systems guy so this is new territory for me. I want to be able to host my own userbase somewhere, mainly I just want to figure out how they work. But all i can find are closed solutions that have some amount of pricing or are obscured. I also feel like it’d be wrong to re-write something like this myself.

I’ve tried googling around a bit but keep getting similar results so I am assuming I am asking the wrong question. What I want: Ideally some kind of dockerized setup where a user can navigate to a website to create an account, which I can then query through php or some other API. Stuff like password reset or stripe would be nice but is secondary as that can most likely be added another way.

I found stuff like usernbase which seems interesting and even includes something like subscriptions, but I’d like to self host it and not rely on something like the AWS.

Ideally I want to get OAUTH2.0 to work as well, to learn how exactly it works.

Any pointers would be greatly appreciated!

  • chiisana@lemmy.chiisana.net
    link
    fedilink
    English
    arrow-up
    3
    ·
    28 days ago

    I think it would be a good idea to take a step back and ask what is it that you’re trying to achieve.

    Userbase, the service linked, is a backend as a service platform that offers you authentication and basic database that you can access via their api. You’d then code your own front end web app to interact with their service and store data there. You pay only per storage used by their storage tiers, which are frankly fairly fair priced. If that is something you’d need, that’s a good idea, but you’d be coding the front end yourself.

    If you’re only looking for authentication with OAuth, and then coding your own API backend, then something like Authentik would be a nice self hosted authentication provider. Others that commonly gets mentioned but I’ve got limited/no experience with worlds new keycloak, or fusionauth. Managed services here would be your Auth0, Okta, etc.

    If you’ve got a specific use case in mind, then it may be a good idea to say what service you’re thinking about, and the community may be able to suggest prebuilt solutions that good better and require less lift.