Hey Eduardo, I've taken a look at your project and I think I may have already done this, but as a gist instead of a project?
On the gist there is a modified fabfile, with comment instructions at the top and a Gunicorn service file to add to the deploy directory. Following your instructions, the user would amend the 'real_project_name' after creating the Mezzanine project. In mine, I've suggested they change the default template files, so 'real_project_name' is automatically populated when the Mezzanine project is created. You are right, changing the fabfile to automatically deploy to more distros than Debian will add complexity. I was thinking of handling this by creating a function that considers which distribution the fabfile is being run against, by referring to /etc/redhat-release and equivalents, then runs other fabric files for each type of distro, separated in a package directory. This would be a way to divide the complexity into manageable parts -- what do you think? cj -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
