Yes, I think fab create has to restart from the beginning. One more advice, be sure that all Fabric settings in settings.py are completed (or as much as you can). I tried to leave the field REPO_URL empty and fab deploy didn't work until I set a real git repository. ++
On Wednesday, February 26, 2014 1:15:21 AM UTC+1, Federico Bruni wrote: > > 2014-02-25 11:47 GMT+01:00 <our...@gmail.com <javascript:>>: > >> I have just deployed my first Mezzanine project and I agree with what >> you say: the deployment was clearly the most difficult part. >> I used fabric too, but it's not very easy but once it works it really >> saves you a lot of time. I have the feeling that when a step goes wrong in >> fab deploy, it begins to do strange things. >> So, instead running fab all, I run: >> * fab install >> * fab create >> * fab deploy > > > Thank you, it helped a lot. > I'm trying to make 'fab create' work until the end. I've made many step > forward, but now I'm getting this error: > > django.db.utils.OperationalError: fe_sendauth: no password supplied > > This is probably because I haven't defined DB_PASS in settings.py. > What's the secure way to define these sensible variables (passwords, > secret keys, etc.) out of the source repository (even if it's private)? > > Another important question: if 'fab create' fails and I want to run it > again, it seems that I have no other option than accepting the removal and > start again from the beginning. A huge waste of time and resources. There's > no other way? > > -- 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/groups/opt_out.
