[mezzanine-users] Slow page load of Python 3 Mezzanine site on Webfaction
I'm having problems with my mezzanine site which is periodically very slow to load (TTFB up to 25 secs, sometimes). This usually happens immediately after restarting Apache, but also after a few hours' inactivity. The time seems to be spent waiting for the server to respond with the HTML: the static files (served by a separate nginx server) all come back quickly. I've tried WSGIImportScript in my httpd.conf and running mod_wsgi in daemon mode as suggested in various places but to no avail. I've also tried some of the debugging techniques described at https://code.google.com/p/modwsgi/wiki/DebuggingTechniques but because many of them are incompatible with Python 3, they don't help too much either. Webfaction's support don't seem to know how to help either. I'm using PostgreSQL as my database backend if that makes a difference. Does anyone with experience of running Mezzanine with Python 3 have any advice to give? Cheers, Christian -- 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.
[mezzanine-users] Using CDN in depolyment
Dear all,
I'm sorry to bother this list with what must seem like a trivial question,
but I've deployed my Mezzanine site on webfaction by following the
instructions at
https://community.webfaction.com/questions/10290/how-can-i-install-the-mezzanine-cms-for-django-on-webfaction
My website works, but it's very slow to load, and I got to thinking that
this is down to the use of local js and css files, e.g.
link rel=stylesheet href={% static css/bootstrap.css %}
Can I pull some of these from a CDN and if so, do I just need to change
base.html and put the necessary links outside of the {% compress css %}
block, or is there more to it? Is there a way to use local static files in
development but the CDN links in production?
I'd be grateful if someone could put me right if my thinking here is wrong.
Thanks,
Christian
--
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.
[mezzanine-users] Re: Using Mezzanine with Python 3: package compatibility
Thanks Josh and Graham, I'll stick with PostgreSQL then, but wait until the next Mezzanine release before upgrading Django. I'm just glad to have got my site online for now! Cheers, Christian On Friday, May 15, 2015 at 4:31:18 PM UTC-4, Graham Oliver wrote: Hi Christian In terms of MySQL vs PostgreSQL have a look at https://docs.djangoproject.com/en/1.7/topics/migrations When I read 'PostgreSQL is the most capable of all the databases here in terms of schema support' and 'MySQL lacks support for transactions around schema alteration operations, meaning that if a migration fails to apply you will have to manually unpick the changes in order to try again (it’s impossible to roll back to an earlier point).' I decided that PostgreSQL was the best option. Cheers g On Saturday, 16 May 2015 02:32:36 UTC+12, xnx wrote: Hello Mezzanine Users, I'm new to Mezzanine but not Django: I'm enjoying learning it a lot and it does a great job, but I've run into a couple of problems. I am trying to deploy Mezzanine under Python 3.3.5 and, although I have a working site, I have a couple of questions about compatibility with the packages I need. I'm using Anaconda 2.2.0. * Installing Mezzanine with `conda` automatically downgrades my Django version to 1.6.11: is there an upcoming release that will support Django 1.7+ under Python 3? I'd like to use django-migrations. * Is there any way of using MySQL in this stack? I found I could not install MySQLdb under Python 3 and this seems to be a requirement for Mezzanine using a MySQL backend but isn't provided by Anaconda. I'm using PostgreSQL like a grown-up instead, but my preference would probably be for MySQL. * The Mezzanine docs at http://mezzanine.jupo.org/docs/user-accounts.html suggest using AUTH_PROFILE_MODULE to implement user profiles in a Mezzanine site, but the Django docs at http://django.readthedocs.org/en/latest/releases/1.5.html#auth-profile-module say that this has been deprecated since 1.5. Am I missing something here? Thanks for reading, Christian -- 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.
