Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tarekmoz
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
tarekmoz
13y ago
yeah the build is staled on readthedocs ... trying to see how to fix that. They will eventually show up sorry. You can find them in the docs/ directory in the repo
32.
▲
by
tarekmoz
13y ago
Mostly portability: you can provide a single configuration to manage your stack no matter what the system is It's also easier to run in the user space if you are not root
33.
▲
by
tarekmoz
13y ago
> First question, what is a typical use case for wanting multiple instances of a specific process? distribute the load. For example I can run several "redis workers" that gets jobs to do in a redis queue. > Second question,
34.
▲
by
tarekmoz
13y ago
Supervisor is solid and mature, that's for sure. If not for the sockets feature, I would say that you would want to move to Circus if: - you need python 3 - you have a complex start/stop sequence where you need to add some custom
35.
▲
by
tarekmoz
13y ago
Yes thanks - I have fixed this and triggered a build - it should appear in a little bit
36.
▲
by
tarekmoz
13y ago
Yeah we did not ship a plugin for e-mail alerting - the builtin plugins are : http://circus.readthedocs.org/en/latest/for-ops/using-plugin... But writing a new plugin is very easy, see : http://cir
37.
▲
by
tarekmoz
13y ago
That's great to see Supervisor is moving forward on the Python 3 support. Scott is actually the person who ported Circus to Python 3, so double kudos for him.
38.
▲
by
tarekmoz
13y ago
Author of Circus here. Major differences: * Circus uses ZeroMQ, Supervisor uses XML-RPC. * Circus is Python 3 compatible, Supervisor is Python 2 only * Circus will let you manage sockets - see http://circus.readthedocs.org/e
39.
▲
by
tarekmoz
13y ago
same here
40.
▲
Nobel Peace Prize 2013 : OPCW
(nobelprize.org)
3 points
by
tarekmoz
13y ago
|
5 comments
41.
▲
by
tarekmoz
13y ago
The first app that comes to my mind is using those for a secured messaging protocol.
42.
▲
by
tarekmoz
13y ago
yeah that's why I mentioned it. Back in college, right before the year 2k, we had a special Cobol course they added just to get people some 2k jobs. I recall one guy who's still doing Cobol most of his time, working on old softwar
43.
▲
by
tarekmoz
13y ago
It's not listing Cobol.
44.
▲
by
tarekmoz
13y ago
If you speak french, this is way funnier: funny review about a giant swiss army knife - http://www.amazon.fr/Wenger-19201-Couteau-suisse-g%C3%A9ant/...
45.
▲
by
tarekmoz
13y ago
I have been remote for 10 years. The secret not to get nuts is to interact online with colleagues as often as possible. "From the employer’s perspective, you’re risking burning yourself out if you work 50-60 hours a week" mmm... 50 hours is
46.
▲
Thoughts on Mercurial and Git
(gregoryszorc.com)
14 points
by
tarekmoz
13y ago
|
2 comments
47.
▲
by
tarekmoz
14y ago
> I guess the idea here is to aggregate Circus events in a multiserver environment. Yeah that's the basis for it. We're planning to add a cross-server feature, so a single CLI can handle processes across several boxes transparently Ther
48.
▲
by
tarekmoz
14y ago
Whatever the python socket module supports, we can support.
49.
▲
by
tarekmoz
14y ago
Circus author here. I am interested in any form of feedback on the issues you had. Falsely detecting a work crash sounds very weird and unprobable because Circus uses the system PID list to check on processes - so I wonder what happens in y