This is what everybody can see in my Git repository
In this case, it does not really matter because it is part of tutorial.
How do Wapplers go about hiding this information?
This is what everybody can see in my Git repository
In this case, it does not really matter because it is part of tutorial.
How do Wapplers go about hiding this information?
Well if you are going to publish this as sample project on a public github repo, then you should replace the credentials with xxxx in both server connect connections and database manager, before comitting it to public. Then in your read me make sure you explain how people should enter their own credentials there.
Note that if you have previous commits - the credentials might already be there as well. So it is better for the final project to use a clean github repo without any previous history,
Maybe we should improve this somehow in Wappler, so that credentials are auto cleared on commit but then when cloning a sample project, the user should be prompt for them … ideas are welcome!
Secrets manager support.
Which Secrets Manager do you mean? There are so many and each cloud provider has its own …
All of them! Joking!
Self-hosted:
Docker swarm secrets manager. Given the increasing amount of docker containers you are providing(app, db, redis, traefik…) a swarm might be in order.
Hashicorp vault
Other lightweight FOSS alternatives
Cloud:
There is also:
https://docs.github.com/en/actions/security-guides/encrypted-secrets
but that is more for the github actions authorization.
Will let you build soon a lot of extensions
only such things as secrets are pretty much Wappler wide, so it will be good to have a generic solution indeed.
For the app/ui/desktop also???
Sidenote: I think Wappler app/ui/desktop needs a new name for disambiguation. How about Wappler Studio?
well we will be starting with Server Connect and App Connect extensions where you can define property UI en even frameworks and we will see after that
it does sounds good
Nice.
For secrets manager this project is trending hard and quick.
Roadmap looks very nice and there are integrations for frameworks, selfhosted stacks and cloud servers.