This is an alternative to Ansible, which is an agentless system administration tool.
You define a set of tasks, explain how they should run and on which servers, and run on a potentially large set of computers via SSH. Nothing is installed on the remote nodes you are targeting.
A typical scenario would be "install php on web servers, fill this nginx configuration template then push it to /etc/nginx/site-available/, make a link from /etc/nginx/sites-enabled, on database servers only install PostgreSQL, etc. etc."
I think this tool is promising, as ansible is quite slow and error-prone. But with software alternatives there's always the problem of feature coverage and community adoptions and support.
Thank you for this comment, I had a hard time pinpointing exactly what made me feel uneasy about all those answers justifying the audience behavior or explaining that they were setup for violence because various harmful objects were present.
It is indeed the same way of thinking.
If you murder someone, I don't see how you could blame them for being too close to a knife or gun. Having the opportunity to do something does not systematically justify doing it.
edit: this logic does not apply even if the person brought the harmful object with them, the decision to do the harm is ultimately not made by the victim.
I am sorry if this is not the place to discuss it and will remove my comment if needed, but seeing websites "highly recommending" the use of Chrome seems like bad taste nowadays, especially with what's going on with WEI.
> A fast, compliant alternative implementation of Python
Performance without compromising too much on compatibility seems to be the main benefit. There is a talk on the YouTube channel «Pycon Sweden» from 5 years ago where the host showed some impressive speed gains for his workload (parsing black box dumps from planes).
This post is a funny coincidence as I tried today to speed-up a CI pipeline running ~10k tests with pytest by switching to pypy.
I am still working on it but the main issue is psycopg support for now, as I had to install psycopg2cffi in my test environment, but it will probably prevent me from using pypy for running our test suite, because psycopg2cffi does not have the same features and versions as psycopg2. This means either we switch our prod to pypy, which won't be possible because I am very new in this team and that would be seen as a big, risky change by the others, or we keep in mind the tests do not run using the exact same runtime as production servers (which might cause bugs to go unnoticed and reach production, or failing tests that would otherwise work on a live environment).
I think if I ever started a python project right now, I'd probably try and use pypy from the start, since (at least for web development) there does not seem to be any downsides to using it.
You define a set of tasks, explain how they should run and on which servers, and run on a potentially large set of computers via SSH. Nothing is installed on the remote nodes you are targeting.
A typical scenario would be "install php on web servers, fill this nginx configuration template then push it to /etc/nginx/site-available/, make a link from /etc/nginx/sites-enabled, on database servers only install PostgreSQL, etc. etc."
I think this tool is promising, as ansible is quite slow and error-prone. But with software alternatives there's always the problem of feature coverage and community adoptions and support.