A full stack Python application framework for building consumer and business web services from the scratch
WebSauna is featured in the Jul 8, 2019, PythonBytes podcast.
https://pythonbytes.fm/episodes/show/138/will-pyoxidizer-weld-shut-one-of-python-s-major-gaps
Hi @miohtama , I contacted @clickio with a similar question and I made this observation(s)
The benefit of Docker is a "disposable" development environment; where
disposablemeans that you can quickly (re)start from known working state?
Then, reflecting on my own, very preliminary, experience setting up web sauna:
I think the challenge is that web sauna incorporates multiple components, depending on what you want to do with it (hence the use of cookie cutter in the
getting startedwhich is unusual.
Uncommon, but not necessarily a problem.
I wonder if the solution might be to embellish the ansible repo with some plays for getting started and maybe some plays for building images. The advantage of ansible is that you can concatenate many steps or recompose them into a different combinations
I would defer to the wisdom of the group on this.
ansible-bender builds images from ansible plays: https://blog.tomecek.net/post/building-containers-with-buildah-and-ansible/The result could be to have a number of images with permutations of features, created automagically as part of the release process.
the dockerized code is: https://github.com/ErnstHaagsman/djangodocker/tree/dockerized
OK, I can tell that I reallly want to use web sauna for my current two projects... Doing a multi-stage Dockerfile will reduce the size of the final image. I don't yet know enough to suggest the structure of the Docker image(s). However, it does seem like we would want three distinct use cases, and I'll use pseudo-code for convenience:
make demo to produce a default cookiecutter project and running dev server so that a user can access a working project without making any decisions.make dev to produce a installed project with optional modules and a data volume to overlay the source directory.
make stage to produce a production-ready project, importing secrets and user accounts during the intermediate build stages.
.... does anyone in this group run Websauna on k8s or perhaps OpenShift?
Honestly, I have a love/hate relationship with Ansible... it's like vim in the sense that it is idiosyncratic, unintuitive and inconsistent.... until you try the alternatives.... So, I am trying to promote good devops practices at work these days and have some to the conclusion that:
For automating processes on the local machine:
Makefile.... For automating processes on remote machines:Ansible
websauna security orientation, I would recommend using podman instead of Docker because it does not require any root privilege. Again, for the purpose described by @clickio , I think is best to have a very opinionated "hello-world" default (maybe a swagger pet-shop app) make demo and then one file to place any custom vars and then make dev (where the Makefile triggers the ansible playbook). I am just a visitor here so please let me know what is most feasible in this community.
We want to add
websauna in our benchmarking project => the-benchmarker/web-frameworks#1904@clickio @ericof do you consent on such a thing ?