peclink

4 ms·

1. 1.▲
   by peclink 6y ago

   The most interesting concept is "Build & Deploy" and it's a pity that it isn't described even on conceptual level. I think the "Build & Deploy" for configuration management is the right thing, but it lo
2. 2.▲
   by peclink 8y ago

   Do not use wkhtmltopdf for this, use weasyprint instead. Markdown → Pandoc → HTML → weasyprint → PDF works great, paged media support in weasyprint is good enough and much, much better than in wkhhtmltopdf.
3. 3.▲
   by peclink 10y ago

   What a great idea, thanks for sharing! BTW, why using shell scripts to write migrations is so unpopular? We have lots of language/framework specific solutions or some «language agnostic» tools using plain SQL, both ways are rather limi
4. 4.▲
   by peclink 10y ago

   There is Bullet http://bulletphp.com , that inspired us, but it is too simple and lacks some important (for us) features, e.g. recursion. There are nested routes in Express and some Golang libraries (see gongular near on HN), but
5. 5.▲
   by peclink 10y ago

   > But quite frequently I want to answer this question with just the source code. Exactly. And that is also a benefit if routes are fetched dynamically from database, e.g. for content application, so your database is really content reposi
6. 6.▲
   by peclink 10y ago

   All these routing libraries are just wrong level of abstraction. In HTTP you have resources, and resources are not flat, they are hierarchical. And hierarchy of resources defines some connection between then, and some common properties (dat