; *From: *Roger van Schie
> *Sent: *Friday, February 21, 2020 9:45 AM
> *To: *mezzanine-users@googlegroups.com
> *Subject: *Re: [mezzanine-users] Are fabric deployments popular?
>
>
>
> Hi Ed
>
>
>
> I believe the included fab files decreases the learning curve for ne
@googlegroups.comSubject: Re: [mezzanine-users] Are fabric deployments popular? Hi Ed I believe the included fab files decreases the learning curve for new users dramatically, and it would be great to keep it in, not only to make it easier for new users to get going, but to avoid unnecessary traffic
Hi Ed
I believe the included fab files decreases the learning curve for new users
dramatically, and it would be great to keep it in, not only to make it
easier for new users to get going, but to avoid unnecessary traffic on the
forums. I would suggest having multiple fab files though, for
Hi,
I do make use of a (modified version) of the included fabfile. However, I'm
using Python 3.6 on my dev and server machines, and use Fabric3 to do the
deployment. It works pretty well.
If this could be the supported version for Python3, that would be great.
Seeya. Danny.
On Wed, 19 Feb 2020
Ed
I really appreciate your work and love Mezzanine and Fabric.
I would like to see the fabfile kept in Mezzanine and enhanced slightly
by removing repo specifics to make it repo-agnostic.
I use and support a number of Subversion repos. I have done this for
more than a decade and although I
I love the fab file that ships with Mezzanine.
My first vote would be extraction into a separate package.
Second vote: keeping it in Mezzanine.
Third, point to the Django deploy docs or ship Mezzanine with a docker file
(I wish I had time contribute a docker file).
Thanks for all the great work!
