Day 2 Lightning Talks

This video is from DjangoCon Europe 2026 in Athens, Greece.

Day 2 Lightning Talks
0:43:27
Published October 26, 2026
177 views

A video collection of all the lightning talks from Day 2 of DjangoCon Europe 2026

Follow DjangoCon Europe on social media:
*X - https://x.com/DjangoConEurope/
*LinkedIn - https://www.linkedin.com/company/djangocon-europe/
*Mastodon - https://fosstodon.org/@djangoconeurope

#django #djangocon #djangoconeurope #djangoconeurope2026

Transcript

6,376 words · auto-generated · en Show

Automatically transcribed, so expect mistakes in names and technical terms.

0:03

Speaker 1: And now I'm going to pass it on to that guy, Andy. Uh he's here again. So we're we're going to have lightning talks and then we'll we'll have the after party. So everybody that has an accepted lightning talk Let's gather on that side of the room so that you're closer to the podium and that we can do things more quickly today. Let's optimize the process, you know, step by step. Um would you like this? No. Really? Okay. So yeah. You know people will not be happy to stay here and listen to you Andrew if you

0:50

Speaker 2: technical difficulties are resolved.

0:54

Speaker 1: Okay.

0:55

Speaker 2: Okay. Everything is fine. Nothing is gonna go wrong man. At all. Space hours. The first talk we have is Andy Miller on developing Django's community.

1:18

Speaker 3: This is me. Uh I am a consultant with Software Crafts, Solo Django. I'm co-founder of Hamilton Rock. I'm doing the tech side. I am Nano Republica, most places online, and in the Django community, I'm the Online community working group chair, hands up if you know what a working group is. Just so Num few, how about half the room? I'm also the admin on Discord, one of the admins, and I organize Django Social in Cambridge. I also helped John do the conference one. I love Django, I love Django Con, you are my people. Um it's my third in Europe, I wanna keep coming. Um there's clear value here in the room, in the hallway track, the conversations you can't have anywhere else. That developing of a relationship. But

2:04

Speaker 3: it cost me a thousand euros to get here. It probably cost everyone that's probably a rough mean I'm taking. That's very expensive, right? For we're a global community. Um, so it's exclusive to those that can afford it and can afford the time to be here. So what can we as a community do about that? So I said we're global. Most of it is online. This is the list of places that you can hang out online. There's the forum, there's Discord, there's GitHub track, you've got the list there. Um I recommend Mastodon and uh personal blogs. That's where the hot takes happen. So I proposed the online working group to help improve the online

2:51

Speaker 3: community. It's a DSF working group, so we meet monthly. We're actually looking for new members. It's about four or five of us. We coordinate with the Code of Conduct Working Group because we're moderators and admins, so we deal with both the positive and the negative. or the online spaces. And I just wanted we've got a repo like the New Features repo. It's ideas to improve the community online. That's a QR code to the GitHub repo. I want to see I'll get to that, but we're looking for members. Um some of the ideas that I have or we've had is on Django Profile. com, Django Project. com, everyone has a profile. Currently it just says if you've raised tickets and if you've merged PRs. I think we could have links to socials.

3:36

Speaker 3: It could be the center of the community online, of like knowing what someone who someone is, what teams they're on, where they've been, what conferences they've been to, that kind of thing. Um we can help operate a bit more like a company. If you you're in a company, you have Slack, you've got tickets coming in, pull requests coming in. We could have that and you give visibility to what's actually happening. We've got Django News, but this is the next step, I think. Um we could have virtual social events Um a couple of years back I organised a virtual sprint. It worked, but the best thing about it was just all of us on a call talking across the world. We had America, we had Europe, we had someone from Australia All in a one call and it was just nice. It was here

4:22

Speaker 3: but online. Um some of these ideas won't work, but that's fine. It's about experimentation, it's about just improving the community for everyone, absolutely everyone who cannot be in the room. So go to the repo, suggest your own ideas, react to the ones that are there. If you want to help, please do. It's going to be less intimidating than the actual contribution process. Do Django. It's new ideas, it's bots, it's improving the website, it's fresh ideas. Anything goes almost, it's not going to be straight. So thanks.

5:05

Speaker 2: twenty seconds left so you can't leave have you got anything else to say? No? Okay, that's great. Thank you. Thank you very much. And by the way, I think we can all appreciate the importance of that, can't we? Another round of applause, please So uh my current working method for figuring out who's uh next is looking on the message I sent to Zulip. And uh Zulip is is really easy to use, so it's it's actually no problem to do that. Um it's a fantastic Django project that uh I really I really like. Uh does anyone know who's next? I'm really struggling. Benedict. Benedict is next, allegedly. Hey.

5:50

Speaker 4: And you have some slides or not? Yes, I send them by email. Uh-huh. Which was it called? Uh DJ W

5:58

Speaker 2: T. Mm-hmm. And I'll just do this. I just want to point out this is not technical difficulties, this is just necessary. necessary technical procedures to change to change between, okay? There we go. And it works. A round of applause, please.

6:39

Speaker 4: Thank you very much. Um I want to talk a bit about JWT. Um is it all auto forwarding? Um so JWT or not to JWT, basically giving the uh benefits and not benefits of JWT. I found this really good picture here of a billboard that's not really fitting on the on the screen because I think JWT is not for everyone and doesn't fit every use case. So let's first start. What is JW2 actually? It's actually a token, a base X4 encoded uh string. Three parts header payload signature. It's not encrypted. You can encrypt it, but 99% of the time it's not. Um smug is stateless, um but um revocation

7:24

Speaker 4: always needs to happen in the back end and you need to change the code the secret code and if you uh store it a secret for every user then you have to do a back end call and do an j uh do a database call and then it's not actually stateless anymore Um so let's start with the positive things. Why might you want JWT? Um the number one reason to use JWT is if a third party Key cloak, Amazon, something like that. If they give you an JWT token, then use it. You don't have any other choice anyway. Um the other option is The main benefit is that it's has storage in the token itself. You can save database queries with that. You can put your profile information like the user picture or the user information inside the token.

8:13

Speaker 4: So you don't need to read the database for that. You can also put permissions and other stuff in there, but I would be very careful with that because it's cannot be uh revoked at any time. Um you have to wait until the token expires and then or you have to do other database queries, so not great anyway. Um supports offline mode for mobile or desktop applications. Um you can store lots of stuff into the token, all the permissions, all the um menus available. If you store that in the token, you don't have to do a database query for that. Everything works fine. But again, if anything changes on these things, if you need to change a permission, if you need to change uh a menu item and it's store it in your token, you have to wait until the token expires It's had a very long t expiry time, it doesn't work really well and it's not stateless anymore.

9:01

Speaker 4: Um reasons for using something else. JW2s are immutable. You cannot change the token once you give it to the user. If the user has it, it's there. You cannot change it. Um it remains valid until expiration and then you have to refresh it and do another database call. If you set the expiration time really short. You can do really really fast updates, but then you lose all the benefits of JWT. You could use just another server-side token. Um state-level revocation is impossible. You cannot revoke the token by just sending a message to the user. The user has the token, it has an expiry date in it, and it stays until it's expired. Um you cannot lock individual users out, you can only lock out the whole session. And

9:46

Speaker 4: if you store like a one session key or one secret key for all your JWT tokens for all your users And you have like two million users, then you have to revoke all users at once. Um yeah. There's no working way to implement a logout from all devices stuff like You might see in all the social media apps you can click on the button and log out all your devices. That's not possible with JWT as a stateless implementation. Um yeah, so TLDR. Um use JBLT if it requires if by if it's required by third party providers. Prefer session or cookie authors uh for web apps and use uh long-lasting or opaque tokens for web mobile and desktop apps like Auth or something like that.

10:32

Speaker 4: You do not need JWT for that Yeah, so that's my talk. If you want to see the slides of uh

10:45

Speaker 2: great talk, thank you very much. Uh Paolo is next. Uh

10:55

Speaker 5: give it over, give it over. Sweet I can talk, yeah. Oh can I talk?

11:04

Speaker 2: Is that gonna be possible, uh Carlton?

11:06

Speaker 5: Oh I'll see if I can manage it. Can you can you change the deck

11:11

Speaker 2: Like this. Um

11:12

Speaker 5: so I can I know what the lightning talks about, so I can just start and we get a few extra seconds. We want to talk to you about Django on the Med, which is a um sprint experience, sprint-only experience for Django. Conferences like this one are amazing and on Saturday we've got a sprints day and on Sunday we've got a sprints day but I can't be here for the second day of the sprints because I've got to go home. I'm also I'm here for the first day of the sprints, that's great, but I'm also gonna be exhausted. I'm exhausted already. Day two. So the reality is that after a conference like this, we get some stuff done at the sprints, but we can't get as much done at the sprints as we want to. Hang on, that's gotta load. Um So Paolo came up with this idea about having core developer sprints where we get together and it you can tell how long it took to get this idea going, right?

11:58

Speaker 5: Because it used the word core developer, that was a decade ago Where we would get together and have time to work on Django together. So we where were we? Dublin. 2025. Paolo and I are like, right, we're gonna make this happen. So in Palafouger where I live, we did Django on the Med last September and you see the pictures there. This is us sprinting in the morning and then we'd have lunch somewhere. Did the picture of lunch come up Paolo yet I don't know. We had lunch, it was nice. Then we'd go to the beach or we'd explore and we'd have the evening together and we'd carry on the thing. We got more done in three days on Django than you can imagine possible Marish is here managed to land a 10-year ticket on the ORM to introduce DB native cascades. delete an object and it's got a billion child objects.

12:44

Speaker 5: We're no longer going to have to bring that into memory and delete all of those in Python. We'll be able to do it in the in the D B. Marish said something he put up a wonderful quote that simply wouldn't have been possible without Django on the med, without that dedicated time. So there's the pitch for you to come, there's the pitch for your company to send you if your company builds on Django. You we will get stuff done at Django on the Med that simply wouldn't be possible either. And there's a pitch for your partners to come and join you too, because we only sprint in the morning and the afternoon is for you know being on the med. So that was all in Parapuget and in um September this year we're going to do it in Pescara which is in Italy. If you've got a nice uh oh look go on go back show the animation There we are. It's in the the east coast of Italy.

13:31

Speaker 5: Is that the Adriatic next to it? Yeah, it might be. Anyway, we're gonna go and do it there, and we invite you all to come. The dates are No, we gotta wait for the animation to finish. There's a direct flight from Pescara to everywhere, but there's also trains from Rome. If you can't fly to Pescara, you can get the train from Rome. There's the trains, look amazing. Brilliant. And there's a website with it. You just go and fill your name in in the box there and we'll send you loads of emails about it. There it is. It's gonna be in Pescari in Italy on the 23rd to the 25th of September this year. Do come. It's phenomenal But not everywhere is on the beach. So I'm just gonna hand off to Paolo quickly. Okay.

14:15

Speaker 6: So you can scan the QR code if you want to uh to see the website. I have two minutes to talk for something uh uh related but not it's PyConitalia. I'm talking about you because we are hosting something very similar to Django on Demands The name is Django Off the Med, because we are not b on the Mediterranean Sea. In this way we can organize everywhere in the world from uh South Pole to everywhere. And The first day of PyCon Italia, the conference where we have 1,000 people last year It's a day free for everyone. We host workshop for beginners, Django

15:01

Speaker 6: girls, public speaking and we all have also Django of the med. To show people what we are going to do in Pescara in September. This will be the 27 of May, and you can go on the website and join for free without the the conference ticket but if you want you can also be there for the conference because Pyconitalia also have a lot of interesting things to to show i collected some images also in we will be in bologna and we last year we did a lot of interesting things we also celebrated the the birthday of um of Django. We had some fun

15:47

Speaker 6: music. We played some Django Rainer music. We have the swim swimming pool, a lot of s talks as every conference, but we also have a lot of social events and good people we also uh went around the w with the city in a tour so a lot of interesting Uh sorry, interesting things to do. This is the QR code if you want to join PyConitalia from 27 to 30. The first day is free for everyone. And we host Django off demand. We are very happy if you want to join us and see you in one of these two events. Thanks.

16:39

Speaker 2: Thank you very much. I think everyone's now clear that you must go to Django on the Med or Django Off the Med or PyCon Italia or both or all three. Um you don't really have a choice as far as I understand. So next up we have a to it's Anthony, right? Anthony, we I I don't know your last name.

16:55

Speaker 7: Rico. Anthony Rico.

16:57

Speaker 2: Anthony Rico and this is I just looked on my phone. Generated fields. Yeah, Django generated fields. So let's have a look

17:07

Speaker 7: Uh while it loads. Who has heard of uh generated field? If you can raise your hand. Oh not that many. Uh keep your hand up if you've used it on a project. A few more less hands. I will not be talking about generated fields in general because it's a lightning talk. Hello, I'm Anthony, I'm from France. I've been doing back-end and frontend for more than 20 years. I discovered Django 18 years ago and I'm in love ever since. Um two ways I've used a generated field doing a rewrite. As I said Generated field. I'm not gonna talk about it too much. There's documentation.

17:54

Speaker 7: Or you can search generated field and Paolo. 'Cause he has done where is he he has done many uh blog posts and talks about uh the subject. A bit of context about the project I've used it on. It was urban planning for the French government. So I'm gonna mention cities and procedures for the models. It was an iterative rewrite to avoid a long feature freeze so we can implement stuff on the existing stack and the new stack. The existing stack was not in Django, and I'm not gonna name the technology but we have drinks afterwards. And uh there was a new Django stack. Both of those were live in production.

18:40

Speaker 7: Uh but the existing stack, and that's one of the reasons of the rewrites, had no automated tests and very poor database modeling. The first use. So as I said, a procedure is a model with many fields. I'm only showing the archived field, a Boolean field. You can think of it as sub -delete. Um and we discovered that some of the procedures were archived because there were actually duplicates of other procedures. And we want to uh track that information but we can't with just a boolean. So let's add a field and that field is called duplicate of. It's a one-to-one field on its own on the same table, where

19:27

Speaker 7: which and it's gonna point to the canonical procedure that we want to keep around. Um in the existing stack a lot of code was uh ignoring archived procedures like a self-delete. Um And now that we've introduced that new field, we also want to ignore the duplicate self. But I told you that there's no automated test on the existing stack, so it feels Risky to change every place where there's requests for procedures and to ignore them. What if the database could help? That's what generated fields can give us. So um wait. Yes, sorry. Um the first thing before introducing the

20:12

Speaker 7: um generated field We've renamed the archived field from archive to soft delete because it better represents what it meant. And then we introduced an archived field which is our generated field. First, the output field explains that it's gonna be a Boolean field in the end. dB per systiquant through is will depend on the database you use, but we needed to use that value. Uh and the important part is the expression and in the expression we oh let me scroll on my notes. That's Yes, the expression. We want archive to be true whenever self delete is true

20:58

Speaker 7: or there 's a value in duplicate of. And using that approach, we can write automated tests in the Django stack that verify that we've written the right expression and do all of the thing we want and every part of the existing stack or legacy stack if you want that used that um looked at the archived field will benefit and ignore the duplicates of because of the generated field. That's it for the first use. The second use. We have a many-to-many table that links cities to procedures. But it's not that easy. We have a city code and a city type.

21:45

Speaker 2: You have one minute.

21:46

Speaker 7: Oh okay. You might be thinking about composite primary keys. We didn't do that. Lightning talk, no explanation for why we didn't do that Um the CT model has an ID that is a car field in the format uh on the right. And We uh added a generated field to the city procedure. Um this time it's a car field output and the expression concatenates the city code, underscore, and then the city type. But there's still no foreign key in sight. And I looked up the documentation and found foreign object. Which allows us to connect to the CT model.

22:34

Speaker 7: Um and this was a concept introduced for composite primary keys. We say CTID and ID are the fields to connect on each side. Now that I've said all of this, don't use it. Uh for an object is an internal API, it's not covered by the duplication API. The documentation says that. I see someone say The documentation says it's inter internal. Uh document, but it was used soon for us because it's an existing system. And that's helpful. Uh thank you very much.

23:13

Speaker 2: You were actually twenty seconds over, but it was quite interesting, so I I allowed that. Thank you very much. Uh next up we have uh Fabian Fabian, one of them. Um So I I said people must use my laptop uh for their slides. And uh we found an edge case which is he wants to use his laptop but without slides. Um so you know there's always an edge case isn't there. Someone has to be difficult. There we go. Round of applause, please.

23:51

Speaker 8: I'm Fabian. I'm one of the two Django CMS fellows, which mostly means I'm spend a lot of time maintaining systems where we've re reinvented quite a few things over the years. Sometimes more than once. Interestingly, at this Django con I realized I'm not all alone on that. And let me connect this to a slightly personal story. Uh I myself learned programming in the 80s on a system called Eumel. Which, in hindsight, might have set some unrealistic expectations. Eumel was built around some very strict ideas Isolation by default, no implicit access on anything.

24:38

Speaker 8: Everything had to be explicit by communication, between processes, anything. As a beginner, that just felt normal. I didn't know anything else. Um you couldn't accidentally break many things. You could screw up the systems, but you couldn't break it really. The system didn't allow it. So um later then I encountered more mainstream systems. Suddenly we have shared states, global access, need for locks, permissions layered on afterwards. And a lot of more things, ways to break things, which I assume was uh progress, I guess. Fast forward to today, working on Django systems, we keep reintroducing things.

25:26

Speaker 8: Plugin and app boundaries, permissions with inheritance, we heard today. Content isolation for subprocesses, stable islands. And we call this good architecture, and it certainly is. But it also looks pretty familiar. And here's the part that changed how I thought about this. These ideas earlier didn't appear, they didn't fail, they shipped Oimel became L3, L3 became an operating system, a microkernel called L4. Systems based on L4 have run in billions of mobile devices. And in any modern iPhone, the secure enclave, the part that handles keys, biometrics, and encryption runs on an OS based on L4.

26:15

Speaker 8: So we didn't just forget about building secure systems. We just moved those ideas somewhere else else where we really needed them. In the systems where the failure was not acceptable. So for me, that has been a slightly strange experience. Um going back to Django, growing up having grown up in systems that enforce strict constraints, and now I work and have to sometimes add them back in. They were successful and that's a good thing. So reinventing some things when we work on Django is a good thing when we do it, when we need it. Thank you.

27:05

Speaker 2: Any questions? Someone has to ask a question? Carlton? Yeah, yeah, okay, we'll have drinks. No questions, only drinks. Thank you very much. Thank you, Fabian. I uh for tomorrow I'm gonna have all the slides on one computer and then all the slides that require an extended display on on one. uh sequence and then all the others

27:50

Speaker 2: on another sequence. I'm learning all the time. By the end of the conference it will be really good. Unfortunately that's not very helpful, but there we go Okay, round this is this is right? Round of applause, please. Um yeah.

28:17

Speaker 7: Yeah hi, so I'm Alyssa. Um the I don't see my title slide on there, but yeah. Um sorry.

28:30

Speaker 2: Technical difficulties again.

28:33

Speaker 7: They always tell you not to turn around and look at the beamer, but

28:41

Speaker 2: do we have an advantage Uh we use this adapter maybe. No, to get to get

28:44

Speaker 1: to get to get don't do anything.

28:45

Speaker 2: Uh it's on now. And enter fault. I will restart your time as a courtesy.

28:54

Speaker 7: Yeah, thank you. Yeah. So um I've talked about this on the last um DjangoCon actually where I basically just said we will publish that and we now actually published a library on as open source on GitHub. So um What we want to do is like we have media files in our application. We need to store some pictures, some PDFs and other stuff. And media file is basically any data that is stored as a file and that's accessible to users as a file.

29:25

Speaker 8: And uh usually how you do that in Django is you use file fields

29:29

Speaker 7: and um this way you can store files that are attached to a model or to an object.

29:34

Speaker 8: And

29:35

Speaker 7: the default in Django is to use the local file system as a default. You can also use things like min

29:40

Speaker 8: I. O.

29:40

Speaker 7: or S other S3 solutions or things like that. But um for most projects

29:46

Speaker 8: the local file system is just a

29:48

Speaker 7: completely sufficient solution.

29:50

Speaker 8: But then you have the problem of how to serve these files with actual authentication. Um because like you can use the static view, but um this is pretty inefficient if you do that in production. So a way to do that is to use protocols like XXO

30:08

Speaker 7: Redirect or HTTP ForwardAuth, which are basically different ways that you can use a reverse proxy to serve the files.

30:15

Speaker 8: And make the proxy first request uh ask Django if the current user with the current session, like the request that's coming in, is authenticated and

30:23

Speaker 7: also authorized to actually view the file.

30:26

Speaker 8: So the problem is that every reverse proxy has kind of its own solution. I think HTTP forward auth is also available for Nginx and for traffic, but Still, it's a bit messy, there's no real standard, and for each of these proxies you basically require your own specialized view that can actually talk to that specific proxy But

30:49

Speaker 7: um you you actually want to have this uh easy to set up for developers. So we thought let's auto-generate these views and also make it a library, and that's what we did So with Django Media Storage, you can actually pretty easily just make every access to your media files require at least an authenticated user. with a session. And for that you really only need to add Django Meter Storage to your dependencies.

31:17

Speaker 8: You have to configure it

31:18

Speaker 7: a bit For that you have to basically tell it which mode currently is, so which uh reverse proxy is your current setup running behind.

31:26

Speaker 8: And

31:27

Speaker 7: also um some settings for that reverse proxy that Django knows how to actually respond to that, for example. For XXL redirect, you need to redirect to an internal storage on Engine X, and you have to say where that path is.

31:41

Speaker 8: And um then you really just need to add auto-generated views to your URLs.

31:47

Speaker 7: py um and there's a neat function for that. And if you don't do any more setup then all the files in your slash media path um will just be

31:57

Speaker 8: um

31:58

Speaker 7: use one view that requires authentication And if you then configure a web proxy accordingly, then you have actually achieved that. But um then you have authentication, but you also need authorization.

32:09

Speaker 8: And for this, there's a few helpers. Um one

32:12

Speaker 7: is that Um okay sorry that's another slide. Um there's

32:20

Speaker 8: you you we

32:22

Speaker 7: added a new special file field subclass which is called the protected file field And you basically need one view that's called a protected file view for each of these protected file fields.

32:35

Speaker 8: And you can auto-generate them by providing some parameters to the file field, or you can manually implement your views if you need a bit more.

32:41

Speaker 7: More of a complex solution

32:43

Speaker 8: for your author authorization

32:46

Speaker 7: decisions.

32:48

Speaker 8: There's also some special cases so you can manage publicly accessible files that should skip the authentication. I don't think that's the interesting part of what we did. So um if you want to authorize, for example, a request using the Django REST framework permission class.

33:05

Speaker 2: Yeah, one minute.

33:06

Speaker 7: Yeah. Then you can simply just you have your normal project file field and you add three more um arguments to it, which is generate view, protection class, and Um yeah, and the permission classes, which are the Tango West framework permission classes, this will automatically generate a view. This will automatically add the um your L pattern for that view to your

33:32

Speaker 8: URLs and um the authorization will then be checked with a view.

33:37

Speaker 7: You can write your own views, um then you just Write a view that has a check access file and um then you can instead of say auto-generated um say which view to use for that.

33:49

Speaker 8: And

33:49

Speaker 7: um this is Basically the short thing that we published. Um

33:55

Speaker 8: we are using that in production, but currently really we have only implemented the feature that we use ourselves

34:01

Speaker 7: and we Plan on actually making this full. So feel free to try it or feel free to contribute if you like. Yeah, thank you. There's a link to the project.

34:19

Speaker 2: Next up we have a uh lightning lightning talk from um uh uh Me. Um so just very quickly I'm just gonna uh finish off uh my lightning talk from yesterday. So EuroPython is a conference uh in Europe about Python um from the 13th to the nineteenth of july. I know people say when you learn how to talk don't read the slides. It's in ICE, which is uh something conference something in Krakow in Poland. Um it's a really good conference. So I asked what I should say. They said to say it's a really good conference. I asked how many tracks there are.

35:05

Speaker 2: We couldn't really decide if it was five or six. There's lots of tracks um in the conference and uh it's got a very big announcement to make. So I want everyone to be ready for this. We have an announcement which is completely exclusive to DjangoCon Europe 2026. You are the first people to hear this information. We are announcing Our first keynote speakers. I don't know if anyone knows who they are. I mean I've been given this list to read. It's literally on my phone. Guido Van Rossum. Anyone know who that is? Guido van Rossum?

35:51

Speaker 2: And uh Guido is sharing his keynote with uh Pablo Galindo uh Salt Pablo Galindo Salgado and uh Lucas Langer. Did I say it right, Maya? Yeah. So come to this conference, please, please, please, please. That's it. Uh please plup for me. Um I'm Tickets are on sale very soon and they will be absolutely great value and produce a great return for you or your business. Guaranteed. Jan is our next and last lightning talk. This evening and then you can all go have a drink, I'm sorry. Jan?

36:37

Speaker 2: Ah here we are. Awesome. One second

36:56

Speaker 7: There it is. Yeah. Awesome. So Andrew guaranteed that nobody was allowed to leave the room until the end of this talk. Um I guess uh That uh

37:09

Speaker 1: becomes even harder now because the slides are not showing up.

37:13

Speaker 2: There we go. We got it.

37:14

Speaker 1: And there they are. So yeah, um with great power comes great responsibility. Um This is the last talk. I thought, let's talk about Django's deployment story. But we only got five minutes. So let's just deploy a Django app to a blank VPS. Um demo time. So uh I have a little uh Django project here, just a regular Django project. I created the project config and a little app. Um and I'm gonna run it locally here And uh hopefully it's gonna show up. So it's uh called emoji vote, and you can vote for your favorite emoji. I'm a dog owner, so I gotta get those up.

38:01

Speaker 1: You can vote as many times as you want Um and uh so yeah, I mean obviously we wanna deploy this and um naturally we'd like to deploy this to a virtual private server. This is just something I like to do. So um I haven't thought much about deploying this app before, so as I said, just generated it. And now I want to deploy it and actually have a command here. It's called deploy. And all I need to put in to deploy to a VPS is uh the IP address and uh custom host Uh and then I'm just gonna run and it's gonna ask me if I really wanna do it, but uh we wanna have the party, so

38:48

Speaker 1: yes. Um and uh while that's going on Uh let's talk about what's actually happening here. So um I did really just have a blank uh Django project, but I also then went and installed a plugin I wrote which is called DSD VPS CAMAL. And what I also did is then add Django Simple Deploy to the installed apps And um then you already get the deploy command that uh we just executed. And um you can run it and it's It should be quite self-explanatory. And you can see we can pass in an IP address, an optional host, and we can even say we want to use SQLite.

39:35

Speaker 1: So um of course we need to do the provisioning that's currently not part of the plugin. So I set up a VPS with Hetzner. I need to have SSH uh access so um I want to be able to SSH root add IP into the machine and I set up uh a custom host name um with just a DNS entry Um yeah, so uh that's all I needed to do, and then as you see, I was able to run this command. Now It's still running, so I have some time to explain what's actually going on. Uh we have the plugin, which really is just a very thin layer between two things. So Um

40:21

Speaker 1: we're using Django Simple Deploy, which is uh just the core mechanism that gives us the deploy command, and then there are a bunch of plugins already out there for Heroku, FlyA. O, Sklingo, Render, and You can write your own plugin for anything that's missing. Um but I wanted to deploy to a VPS. So What I do there is I rely on a CLI called CAMAL. And um so all the plugin really does, and all that's uh oh, there it is. Seems like yes, awesome. Nice. It actually did work. Great.

41:07

Speaker 1: Yeah, it's kind of the thing. How do you test something if you want to show a blank VPS? So yeah, awesome. So uh yeah, uh get your votes in uh for your favorite emoji. Um so uh really what the plugin did was create a config uh deploy YAML which um just uh tells come all then Where to deploy the application and what's needed, so the database, SQLite. And then we just passed off everything to CAMAL and CAMAL went and set up um the machine uh SSH'd into it, you know, updated the dependencies. There's a lot of things you have to do when you're working with the VPS, right? So you don't want to do it manually. Uh it builds the Docker container, uh it pushes the Docker um

41:56

Speaker 1: container up to the machine. We have uh SSH via let's encrypt. Um There's a bunch of stuff. You can execute commands on your container, you can roll back, you get even uh zero downtime deployments. Um yeah, so um That's really it. Thank you. If you want to talk to me, please do. I love talking about deployment. We can even talk about the deployment story I think it's great if we talk about it. I have a lot of opinions about it. It's also great that there are already some solutions out there. That you can use even while the API is still kind of you know being worked on. And so yeah, please talk to me at this conference, talk to me on Fostodon.

42:45

Speaker 1: This is my email. Thank you.

42:47

Speaker 2: Very good. Interesting tactic. You finished your talk and then continued, so I reset my timer. Very, very tactical. I like that. Thank you very much. Another round of applause, please. And uh now I'll hand off to uh Antonis for the closing of the day

43:04

Speaker 1: All I'm going to do is tell you that you can go downstairs for drinks and socializing. Feel free to talk to people you don't know. If you talk to at least three people you didn't know this morning, that's a that's a great win. And tomorrow we start again at 9 with registration, 9. 30 with the first keynote. So be here, enjoy, and yeah, have fun. Thanks.

Conference

DjangoCon Europe

April 15 - 17, 2026

Athens, Greece

Note: We understand that names change, people change, and bodies change. We respect each individual's journey and privacy. If you have any concerns about a video or need us to remove content, please don't hesitate to contact us. We will handle your request with care and promptly address any issues.

More videos from DjangoCon Europe