/
the-one-true-way-of-doing-django-deployments.json
26 lines (26 loc) · 1.43 KB
/
the-one-true-way-of-doing-django-deployments.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
{
"alias": "video/4035/the-one-true-way-of-doing-django-deployments",
"category": "PyCon AU 2015",
"copyright_text": "creativeCommon",
"description": "...doesn't exist. (Sorry)\n\nThe power and flexibility of Django comes with drawbacks. One of the\ntoughest for project management is working out how to deploy your Django\napplication. If you ask five different authorities on how you should do\nit, you'll get six different answers.\n\nAnd if someone says \"Just use fabric!\": they're not helping.\n\nRelease management, dependency wrangling, virtualenv care and feeding;\nto .whl or .deb? To containerize or Heroku-ize? Do you really have to\nallow your servers unconstrained Internet access just to build your\nvirtualenv?\n\nAs a Django user, you might end up writing more deployment solutions\nthan Django projects. I know I have.\n\nThere's no one true way of doing Django deployments, but some work\nbetter than others. Maybe I can show you.\n",
"duration": null,
"id": 4035,
"language": "eng",
"quality_notes": "",
"recorded": "2015-08-04",
"slug": "the-one-true-way-of-doing-django-deployments",
"speakers": [
"Tom Eastman"
],
"summary": "",
"tags": [],
"thumbnail_url": "https://i.ytimg.com/vi/1ABPQyANid0/hqdefault.jpg",
"title": "The one true way of doing Django deployments...",
"videos": [
{
"length": 0,
"type": "youtube",
"url": "https://www.youtube.com/watch?v=1ABPQyANid0"
}
]
}