mmerickel

39 ms·

31.
by mmerickel 11y ago
"just building an API" does not mean you need something more lightweight. It means you have different requirements from a standard full stack web application. You are not dealing with cookies, forms or template rendering but you a
32.
by mmerickel 11y ago
Yeah I mean it's hard to digest comments like "it's not a particularly opinionated framework" against things like "put the ball entirely in your court". They seem to be saying the same thing except you have a d
33.
by mmerickel 11y ago
Well as one of the primary maintainers of Pyramid I'll just say that it's laughable to me all the comparisons to Django as it's much more similar to Flask. The main difference is that it comes with several more "pay only
34.
by mmerickel 11y ago
LucidCharts has a decent import feature for a PostgreSQL schema.
35.
by mmerickel 12y ago
Am I correct in assuming that this is focused only on source distributions right now?
36.
by mmerickel 12y ago
It's unfortunate that this article focuses on running the playbooks/salt states locally. The use of ssh by ansible was the killer feature for me. Configuring a remote cluster without requiring a persistent master. There are valid
37.
by mmerickel 12y ago
Well from a 12-factor app perspective, having each container dump its output to stderr/stdout is basically perfect as long as docker has a pluggable mechanism for dealing with that output. The "docker attach" API is all that
38.
by mmerickel 12y ago
Currently docker can only mount folders from the host VM into your container. On OS X your host will most likely be VirtualBox. Thus you need to sync the folders from your mac into the VM, and from there into docker. The hack that docker-os
39.
by mmerickel 12y ago
I've never seen a recipe documenting whether docker can handle a logrotate. Most daemons require you to HUP them after rotation. In general logrotate is a complete hack in the way it interacts with daemons.
40.
by mmerickel 12y ago
In general you ought to just be able to "docker run" in the foreground from your systemd script, and then stdin/stdout will go into the journal where you can handle things like any other file. This works now, except that the
41.
by mmerickel 12y ago
There are docker commands (docker logs) that are dependent on this format. The primary issue is that if you deal with logs yourself via attaching to the container and piping them somewhere, the logs are still duplicated to these json files.
42.
by mmerickel 12y ago
I'm glad to see docker stabilizing but it's very disappointing to not see any changes addressing the logging support that was promised in 1.0 ( https://news.ycombinator.com/item?id=7712138 reply by shykes). The inf
43.
by mmerickel 12y ago
nix ( http://nixos.org/nix/ ) seems to be the solution with the most potential in this area, solving all dependencies at the project level and removing the need for language specific build environments.
44.
by mmerickel 12y ago
It seems you could just pass the stores into the components as data - that's really what they represent. I'm not clear why this approach is eschewing that basic principle in favor of singletons.
45.
by mmerickel 12y ago
That's great to hear - I've dove pretty hard into docker and love it but the logging story has been a dealbreaker for production. Decoupling "create" and "start" has been great when using the Remote API because
46.
by mmerickel 12y ago
Yes, I've read all of that. I consider this a blocker for production use of docker and releasing a 1.0 RC without solving this is disconcerting (at least as a process wrapper, it still works fine for wrapping an init system that handle
47.
by mmerickel 12y ago
If this is an RC, will docker have a way in 1.0 to properly handle stdout/stderr logs captured on the host without just allowing a giant json file to fill up? I'm not aware of a way to do it right now without handling logs in the
48.
by mmerickel 12y ago
This is a neat little optimization which can help you avoid needing to convert everything into utf-8 underneath the hood - leaving things in their raw/encoded forms. This may help in certain cases but would probably also make the C-api
49.
by mmerickel 13y ago
On the contrary, Objective-C is one of the only languages that actually gets header files right and subsequently they are a wonderful feature. They are very readable since it's now possible to write them to perfectly describe your publ
50.
by mmerickel 13y ago
CFFI works fine with CPython, and ctypes loads shared libraries without issue as well.
51.
by mmerickel 13y ago
For hysterical reasons, pip has never supported binary eggs. Wheels are the replacement of the future!
52.
by mmerickel 13y ago
While pip does not support binary eggs, easy_install still does. If you want binary distribution with pip you need to use wheels (as you are, of course).
53.
by mmerickel 13y ago
As far as a REST API supporting etags and if-none-match headers, it's pretty unexpected that if I supply an if-none-match to the request, the server may keep the connection open for an arbitrary amount of time. I'd expect that beh
54.
by mmerickel 13y ago
Yes, totally. It is completely lacking any mechanism that allows collection-level operations. If you want to create a bunch of resources you have to abandon the supported headers and return a list of ETags in the body, removing any niceties
55.
by mmerickel 14y ago
I don't understand why the library chooses to require gevent. That's a large dependency for an API that might be useful otherwise. That should really be up to the user since it looks like it'd work fine in its own thread or standalone.
56.
by mmerickel 15y ago
Yes but while implicit route ordering works a lot of the time, I'll gladly keep Pyramid's concept of explicit ordering, which is the main source of verbosity in the Pyramid setup which separates routes from views.
57.
by mmerickel 15y ago
The ordering of your patterns matters, so that is done at config time. However it's very common to want to have unrelated code executed depending on the type of request to a URL. Pyramid will do this lookup for you, rather than polluting a