Hello Guys!
I would like to share a link [1] with you, it is a little help for those
who want to use the Pyramid with the Docker.
Basically it is a microservices structure, divided into backend and
frontend, using the Pyramid on the backend and Caddy [2] (yes, it golang
behind) taking care of the
Thank you so much for pointing me in the direction of these resources. This
is a huge help!
On Tuesday, November 10, 2015 at 3:35:41 PM UTC-5, Jonathan Vanasco wrote:
>
> For your described needs, you should not be using "render" multiple times.
> Mako supports the following:
>
> * Defs and Blo
For your described needs, you should not be using "render" multiple times.
Mako supports the following:
* Defs and Blocks - http://docs.makotemplates.org/en/latest/defs.html
* Template Inheritance
- http://docs.makotemplates.org/en/latest/inheritance.html
* Template Namespace and
Inclusion: ht
Combining renderers to reduce code repetition.
I'm looking for a way to ensure that I don't have to repeat boilerplate
HTML in my renderers. So far the best that I can find is something along
these lines:
@view_config(route_name='home', renderer='base.mako'):
body_text = render("home.mako")
On Tuesday, November 10, 2015 at 11:58:22 AM UTC-5, Jeff Dairiki wrote:
>
> I'm not arguing that this is the best way, but as a data point, here's
> what I do.
>
I'm mad I didn't think of this! It's a great solution for me, because we
already have a `fabric` script do much of the same as par
I'm not arguing that this is the best way, but as a data point, here's what
I do.
I use buildout to generate app.ini, as well as other config files,
including for uwsgi and supervisord, from templates (using
collective.recipe.template.) I have several top-level buildout config
files, all of which
