Le 12/01/2019 à 18:31, Christer Enfors a écrit :
Thanks for the help, but just 2 minutes before you posted it, I
figured it out myself (short version: I had multiple versions of
fabric install, none of which were the *right* version).
Now I'm having a different problem with "fab all", because it failed
part-way through, and now when I try to run it again, it fails because
certain things have already been done (failed to add database user
because it already exists). Now I'm trying to figure out how to clean
up what "fab all" did, so I can start it over. I'll post again if I
can't figure it out.
"fab remove" ?
Den lördag 12 januari 2019 kl. 17:43:18 UTC+1 skrev Kenneth Bolton:
Hi Christer,
I'm not sure it makes a difference, but I am curious why you
didn't try the full import in the python shell: `from
mezzanine.utils.conf import real_project_name`. It is possible
that would have yielded enlightenment. (Also, not using
`shell_plus`, part of django-extensions, is a fireable offense.)
I think the fastest solution might be to start a new mezzanine
project, copy your code into place, and try the deploy again.
Don't delete your existing project! Python/Django apps are cheap
to build and test locally, so do that until you have *confidence*.
I deploy to local VM or container to help build that confidence.
These are a few of the hard-won lessons I can share.
-ken
--
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 mezzanine-users+unsubscr...@googlegroups.com
<mailto:mezzanine-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
