Am just trying to get to grips and understand how everything fits together in terms of Gits, Wappler, Docker and AWS. I’m just a bit lost, to be honest, and I just wondered if someone could give me a high-level overview of how everything fits together.
I’ve done a diagram to show my understanding so far… and I’m sure its wrong…
1 - Wappler is the builder that builds projects
2 - Projects can be stored in a Docker Project, which is a mirror image of the local project with all the files it needs to run independently
3 - Docker can store your Project into GITs, so your code is stored in a repository
4- You can push changes to the project to AWS from the GIT with certain commands.
5 - Users access your app say in AWS EC2 Cloud
Any edits or changes that are made are reflected in the chain.
Github repository and pushing updates from Github to AWS EC2 is not necessarily. I’m doing same without Github directly from Wappler.
I would put Wappler between Github and Docker instance, because Wappler manages them both
MySQL or any other DB is also a Docker image
Your website content is also Docker image. If you’re developing your project using Docker and Window - open Docker for Windows and you’ll see all your images
Docker:
a) Development environment and/or
b) Deployment source
Git:
a) Versión control
AWS: Cloud hosting
So that GIT would be joined directly to Wappler. Not in between docker and AWS.
However, out of Wappler’s context a remote GIT repository can also be used as a deployment source, but there is no native integration for this in Wappler. You would handle the deployment outside of Wappler.
I think that is what got you confused and why you added it in between docker and aws. If you used GIT as a deployment source you would substitute docker for GIT. But you could still use docker as a development environment.
