Generally speaking, all of the content that would appear in displayable_links.js is tied to a particular "site" record in the database, and will only be displayed if the hostname you're accessing the site with in your browser matches the hostname for the "site" record in the database.
For that to work, you'll need to ensure nginx and uwsgi are correctly sending the HTTP_HOST header to the Django app, and that the correct host name is configured in the "sites" section of the admin. I've never used uwsgi, but you can see where this is configured in the default nginx config supplied with Mezzanine: https://github.com/stephenmcd/mezzanine/blob/7bee9d8ca29321ef018a0ea4d5f26c06bb77037f/mezzanine/project_template/deploy/nginx.conf.template#L30 On Tue, May 30, 2017 at 9:54 PM, Lucas Corso <[email protected]> wrote: > There is an important detail when I raise the project in production with $ > python manage.py runserver if it works and it generates the > displayable_links.js but when I lift it with nginx and uwsgi then it fails, > and it gives 404 in the url. > > Which makes me think that it may not be a source code error if not some > erroneous or missing configuration. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Stephen McDonald http://jupo.org -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
