4 ms·
I have been using the unofficial fork Fabric3 (https://pypi.org/project/Fabric3/ https://pypi.org/project/Fabric3/ == https://github.com/mathiasertl/fabric/ htt
by ivan_ah 6y ago
I have been using the unofficial fork Fabric3 (https://pypi.org/project/Fabric3/ https://pypi.org/project/Fabric3/ == https://github.com/mathiasertl/fabric/ https://github.com/mathiasertl/fabric/) for many years with great success (completely automated the IT infrastructure of a medium-sized startup on AWS including provisioning using boto, system config, and app deploy), all with a couple of hundred lines magic-less, easy-to-read scripts, but sadly Fabric3 is no longer updated either, which causes security concerns.
I wish someone would pick that up and continue it — rather then the official version and split into Invoke (which I still don't understand despite a whole week of energy invested).
Honestly fabric was the best thing ever... I still depend on it for personal projects, but sad I can't use it for work projects anymore.
UPDATE: I just found `fab-classic` which is an actively maintained fabric fork with the old API: https://github.com/ploxiln/fab-classic/releases https://github.com/ploxiln/fab-classic/releases everyone rejoice, for civilized devops is once again upon us, and with the paramiko that is new!
- drcongo 6y agoThanks for the fab-classic link. I too spent a week inside Fabric2 / Invoke trying to port our extensive Fabfile and ran in to so many problems that I'd pretty much given up too.