i don't see any changesets in pyramid_tm repo related to this functionality
>>> pkg_resources.get_distribution('pyramid_tm').version '2.2.1' >>> from pyramid_tm import reify Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: cannot import name 'reify' from 'pyramid_tm'
transactionpkg have some internal things for solve conflicts http://dpaste.com/2H0DWSY
old tyle was something like:
for attempt in transaction.manager.attempts(): with attempt as t: ...
also zope.sqlalchemy have defined
but now example how use it :P as i understand, it will fire only if you use
WebSauna is featured in the Jul 8, 2019, PythonBytes podcast.
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-benderbuilds images from ansible plays: https://blog.tomecek.net/post/building-containers-with-buildah-and-ansible/
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?