Re:WordPress 3.6 arrives with better post locking, built-in ...
by e12e on Thursday August 01, 2013 @11:22PM
(#6145160)
Ironically, you could wind up without any where to run your cron jobs in such a setup as well... (eg: running scheduled tasks in the container as the db/cache/webapp uid).
This is of course fixable, but still interesting given the context.
Re:WordPress 3.6 arrives with better post locking, built-in ...
by justincormack on Friday August 02, 2013 @05:15AM
(#6146051)
How? Crown is just a process that sleeps for a minute at a time, checks the config file, forks a process if needed and repeats plus some logging. The only reason WP does not implement that is because shared hosting will kill long running processes.
On the topic of new stacks from the OS on up, Docker[1] (and lxc in general) and CoreOS[2] are really cool. It's a much more elegant and long term solution to packaged, yet controlled, environments.
[1]: http://www.docker.io/
[2]: http://coreos.com/