Update fabfile.py to Fabric 2.6 and Python 3.6, resolves #1957

[jmorsecode]

Summary of Major Changes:

• fabric.api.env no longer exists. Although there are some methods such as "from_v1" they seemed to be more problematic than helpful when trying to target py3.6+. This has been converted to local dictionary for now.
• Functools decorator wraps removed and standard function with similar functionality placed inside where previously decorated. Caused issues with checks in v2 API "Context" object parsing.
• Almost all functions and methods need to be passed the connection context object created at runtime.
• Interactive prompts seem to be awkward sometimes so added checks before disabling root login after sudo user creation.
• Several new custom functions to replace those previously used now removed in v2+.

Notes

• Fabric 2+ CLI usage is mostly the same except for commands that need arguments, which is now:
  fab run --command="id" or fab pip --packages="needed_pkg_name" etc. fab -h will display proper usage but still figured it was worth mentioning.

[jerivas]

Hi @jmorsecode. As part of the Mezzanine 5.0 release process I have made the difficult decision to remove built-in fabric support from Mezzanine, largely because maintaining the fabfile requires a lot of time and attention (which I don't have anymore). I encourage you to create your own package based on the code on this branch. I actually did something similar when I used to deploy Mezzanine to Webfaction: see jerivas/mezzanine-webf.

If you do, feel free to open a PR adding your package to the list of Third-party Plugins. Thanks for your contribution!

[github-actions]

🎉 This issue has been resolved in version 5.0.0-rc.1 🎉

The release is available on:

• GitHub release
• v5.0.0-rc.1

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 5.0.0 🎉

The release is available on:

• GitHub release
• v5.0.0

Your semantic-release bot 📦🚀