Re: [mezzanine-users] first steps with fabric deployment
Hi, 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 When one of these failed, I looked in the fabfile and copy/paste in a terminal to see where it failed. Step by step I managed to make it works. Hope it helps. ++ On Tuesday, February 25, 2014 3:34:00 AM UTC+1, Federico Bruni wrote: > > 2014-02-23 20:24 GMT+01:00 Ken Bolton >: > >> You might have luck with the Django's dumpdata and loaddata management >> commands. Alternatively, django-extensions has a dumpscript command that >> may work. >> > > Ok, I've used dumpdata and loaddata to move from sqlite to postgresql. > Now I'm still trying to make fabric work. I'm not that far away.. Now I > have the project folder copied inside the virtualenv, the postgresql > database on the server is set. > I've launched 'fab all', which _should_ have installed all the needed > packages. Then I launch 'fab deploy' and I get this error: > > File "", line 1, in > [xxx.xxx.xxx.xxx] out: ImportError: No module named django.conf > [xxx.xxx.xxx.xxx] out: > > I see that the virtualenv doesn't have any django package. fab failed? I > guess it was supposed to install also the pypi packages according to the > requirements file. In my settings.py the path is defined correctly: > "REQUIREMENTS_PATH": "requirements.txt" > > Anyway, I decided to do it manually on the server. > But I'm still far away from the end and tons of questions on how to make > the deploy. Now I have just 4 hours to sleep. > > I thought that deploying was the easier part. I was really wrong! > > -- 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.
Re: [mezzanine-users] first steps with fabric deployment
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 >: > >> 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.
Re: [mezzanine-users] first steps with fabric deployment
Did you try to run "python manage.py runserver" directly in your virtual env directory? And is there an error? I the port is in use you can try to stop the server by running supervisorctl stop all. ++ On Friday, February 28, 2014 1:08:44 AM UTC+1, Federico Bruni wrote: > > 2014-02-26 13:18 GMT+01:00 >: > >> 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. > > > Yes, I see that each time you run 'fab deploy' the git repository is > checked and pulled to get the updates. > I've followed your advice, added as many settings as possible and solved > an issue with the gunicorn file, see: > https://github.com/stephenmcd/mezzanine/issues/870 > > Now the server is serving the contents, but... the database is still > wrong. All the static and theme files are correct (favicon, homepage), but > all the rest (other pages and access to admin) is wrong. > Something went wrong with manage.py migrate. How can I find the problem? > In the output I see many "Nothing to migrate". > > -- 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.
[mezzanine-users] Re: IO Error in SSL uploadify alternative
Hello, I've got the same problem. I tried with the demo site. Upload works in HTTP not in HTTPS. Is there a solution to upload media with https? Thanks. On Friday, January 3, 2014 11:27:35 PM UTC+1, laperl wrote: > > Hi all! > > I am trying to put the mezzanine into a production server with apache, > serving static files with apache too. I am having problems trying to > uploading files in ssl mode. I recieve an I/O Error, but I can create > directories. > I read something about the certificates, but I create my own CA and I sign > the apache ssl certificates and import the CA into the "root trusted > certificate" of the firefox client but the result was the same. > > Finally I found that the problem is that mezzanine uses uploadify to > upload files and this is based in flash, and flash don't trust in > self-signed certificates. > > Do you know a workaround of this? can I use another software to upload > files that don't use flash? how? > > Thank you very much > -- 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.
