News for hackers. Stuff that matters.
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.
Re:WordPress 3.6 arrives with better post locking, built-in ... by e12e on Friday August 02, 2013 @08:58PM (#6150589)
You would need extra configuration in order to run cron under the same docker container as your website?