Ken, thank you for posting the link to the Effective Django tutorial. Looks
really useful.
--
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
Correct, my DNS records on Digital Ocean are set up as follows (I'm faking
some of the information here):
example.com
A record: @ 192.168.123.123
NS: NS1.DIGITALOCEAN.COM
NS: NS2.DIGITALOCEAN.COM
NS: NS3.DIGITALOCEAN.COM
example.com is in the ALLOWED_HOSTS list.
It sounds like you may not have
I don't have it on github, but it basically follows the pattern of the
deploy/ngnix.conf file in the mezzanine project. Here's what it looks like:
upstream example {server 127.0.0.1:8001;}server {listen 80;listen
443 ssl;server_name example.com;client_max_body_size
Looks like this was a caching issue on the browser. After going into Chrome
dev tools and disabling the cache, the shop information showed up in the
admin.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and
Rather than the IP address of the host, have you tried your live hostname
(e.g. www.example.com or example.com)? My sites are hosted on Digital
Ocean and that's what needed to be in the ALLOWED_HOSTS list. Same for the
server_name in the ngnix configs.
--
You received this message because you
Hi all, I've successfully deployed Mezzanine with Cartridge to a VPS.
However, I don't see the shop information in the admin. It's showing up in
the dev server, though.
I don't see any errors showing up in the logs, so I'm not really sure
what's happening. Stuff I've checked:
- gunicorn logs
Simplifying the local_settings.py seems to have resolved this problem; I'm
using the defaults for STATIC_ROOT and STATIC_URL that are already in
settings.py, with the configuration for nginx as listed above.
Of course, now I'm getting a different error, but the problem with the
permission
I made some progress on understanding this, but haven't quite gotten past
the problem. One thing I learned was that I mixed up the use of the
STATIC_ROOT and STATIC_URL, but fixing it didn't seem to do much.
Here are what appear to be the relevant configs.
local_settings.py:
STATIC_URL =
I think you're probably right, Ross. I noticed that when we did some
updates to the theme locally and some static files were accidentally
missing, internally the dev server produced a 404 error as evidenced by the
server output. However, on the browser it showed up as a 500 error. I
suspect
Good thought, I had been running collectstatic as part of the fabric
deploy. This time I ran the command by itself.
It correctly copied everything into the location specified by the static
root, so it's putting them where I expected. I'm still not seeing any new
error messages in the ngnix
Could you post the exact contents of your INSTALLED_APPS list? I'm
guessing, but it looks like there may be a typo either in what you posted
here (ValueError: u'django.contrib.admin' is not in list) or your
INSTALLED_APPS list.
--
You received this message because you are subscribed to the
I've been poking at static files on Mezzanine for several days trying to
tease out what is wrong. Here's what I think I know:
I am using Fabric to deploy Mezzanine onto a Vagrant VM.
I have been getting an Internal Server Error message when setting DEBUG =
False. When DEBUG = True, the site
I tried forwarding a port from my host machine and got the same result.
With localhost:8080 forwarded to 80 on the guest machine, I get the message
from ngnix. Forwarding localhost:8080 to 8000, I get no response.
--
You received this message because you are subscribed to the Google Groups
I'm hoping someone can help me. I've been trying for months to get
Mezzanine running on anything other than local (I gave up on it a while ago
and finally decided to try again recently). I've been following Ken
Bolton's excellent instructions, which introduced me to Vagrant (and for
which I'm
14 matches
Mail list logo
