How should prepare such a project that requires:
What server model should be used (PHP, NodeJS, ASP, ASP.NET)?
What database should be used?
Are you using user permissions? What permissions are needed, where?
What CMS do you require - for Blog, Store, CRM … etc. ?
With that many options and only these 4 questions - almost every person would have completely different setup and requirements. So, in your opinion, what project setup will be the one that fits all the different options?
Teodor, yes.
Yes, all of it 
Can you clarify please? What do you mean by all of it?
@Teodor I hear what you are saying, personal I think NodeJS would be the way to go as a starter because while PHP is still widely used I think most things are starting to go to NodeJS. Folks using ASP or ASP.NET will have or know why they are going that route and have more of a developer background.
So here would be my list from someone with no real developer background.
From that I believe you can build many applications ranging from CMS, Stores, CRMs, etc…
This really just to get people over the hump and get them into building their application quickly.
@ben, you right by this. As I find it easier to understand Brian’s way of doing the registration-login-logout from the security server actions but I enjoy how you lay out your login-registration setup. Please take no offend but when following your security server actions, I don’t even know what salt is, nor do I understand why it is need and what makes your method more secure then Brian’s even if it is or isn’t. Or is Brian’s method secure enough for a website with payment data on it.
So I have been reserve engineering Brian’s security methods into your page/modal setup
There are many roads that lead to Rome. Some like to get there quickly, others prefer to meander while taking in the scenery. Which is the correct one? I respect one’s choice.
The best way to learn is to look it up. One such a search gave me
I have used something similar in the past. Don’t forget that Brian and I are old rats in the business.
The way I see it is! Wappler needs to add auth0 sdk to its list of security provider this way we can easy integrate the auth0 service to manage security login, page restriction, etc.
the more vote Please Please Integrate Auth0 In Wappler for Node.js this gets the more chances @George will consider it. Building your own authentication system shouldn’t be just left to what Wappler offer out of the box as security Provider Auth0 is simple thing that Wappler can to its list of security provider currenty there Single, Static and Database, but why not add Auth0 https://auth0.com/single-sign-on.
“Nope” what?
“From the way I see it, having these options pre-filled would make you dependent on Wappler.” Is this an opinion or a fact?
“ You can stop your subscription today, and still keep your project working as it is.…” True, with a template or with no template…
So is there a dependence or not?
Of course any app can be built from scratch or with any stack of libs but if one wants to use Wappler it is then a dependency.
Depends on my work schedule. Ideally before the end of Nov
As Teodor mentioned there any many tech stacks possible and I have reasons to have more than one:
NodeJS & PHP
SQLite - MariaDB - Baserow
Admin - Users
CMS
To cover all of my use cases
I’m looking forward to it! Hopefully this time someone is able to deliver as this is a recurrent request. This and an airbnb clone.
Doesn’t really fit Wappler’s record of integrations as they usually go for open source self-hostable software.
I believe the only two exceptions are stripe and ngrok for obvious reasons.
There are promising open source alternatives to auth0 like Keycloak, Authentik and Supertokens.
How hard do you think it would be for Wappler to add any of those integration you suggested and do you think its a good idea to add a way in Wappler security provider list so we can connect external authentication services such as auth0 and the alternatives you suggested?
I believe I’ve asked a few times to the team to improve Server Connect extensibility to be able to tap into Security Provider to add custom providers.
I’ve also suggested revamping the authorization model and integrate something like Casbin.
I like that I will add my vote to it. Yes it’s extremally annoying that we can’t even use any of the these services api to protect even the simplest of node.js routes without blowing up the entire Wappler out of box security provider way.
Have you checked authelia?
You can self-host it and protect any endpoint you want. It supports nginx, traefik and other common reverse proxies. It’s lightweight and performant.
Thanks for sharing this I will read up on now. Never heard of it before still. Have you tried it before with Wappler? I am desperate for an authentication API service that behave well with Wappler auth provider that can protect my endpoints because building your own auth system requires too much ricks in my opinion when the wheel has already been invented and accessible via API calls.
Not for Wappler apps specifically. For some selfhosted apps I have on a home server that I want to give access outside of my local network.
hot dog!! I have copied over my register page from Ben’s tutorial into Brian’s tutorial. Then I did it again without also most looking at my test project.
that felt good