parent
5a31cc627c
commit
429ec79d4e
|
@ -16,6 +16,23 @@
|
|||
"message": "recheck",
|
||||
"revId": "929bea02ae4c237ff9a2fb196cc2055c0d95e591",
|
||||
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
||||
},
|
||||
{
|
||||
"unresolved": false,
|
||||
"key": {
|
||||
"uuid": "8db10b71_5f2bdce8",
|
||||
"filename": "/PATCHSET_LEVEL",
|
||||
"patchSetId": 1
|
||||
},
|
||||
"lineNbr": 0,
|
||||
"author": {
|
||||
"id": 24824
|
||||
},
|
||||
"writtenOn": "2022-01-12T09:01:23Z",
|
||||
"side": 1,
|
||||
"message": "Confirmed that the images and CSS files are served correctly with this change.\n\nDjango docs explain that they expect static files to be served by a web server of choice (NGINX in our case) but it does indeed serve them when DEBUG\u003dtrue:\nhttps://docs.djangoproject.com/en/4.0/howto/static-files/#deployment\n\"During development, if you use django.contrib.staticfiles, this will be done automatically by runserver when DEBUG is set to True (see django.contrib.staticfiles.views.serve()).\"\nhttps://docs.djangoproject.com/en/4.0/howto/static-files/deployment/#serving-static-files-in-production\n\nI also see some tracebacks in the snap.microstack.horizon-uwsgi.service log https://paste.opendev.org/show/812059/ which I suggest addressing in a different change.",
|
||||
"revId": "929bea02ae4c237ff9a2fb196cc2055c0d95e591",
|
||||
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
||||
}
|
||||
]
|
||||
}
|
Loading…
Reference in New Issue