We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

DjangoCon US 2016: Day 2: Lightning Talks

00:00

Formal Metadata

Title
DjangoCon US 2016: Day 2: Lightning Talks
Title of Series
Part Number
4
Number of Parts
52
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Day 2 Lightning Talks by Many People 00:14 - Lucie Daeye 05:22 - Rostyslav Bryzgunov 08:09 - Tobias McNulty 13:10 - Kenneth Love 17:58 - Joseph Bane 21:35 - Ola Sitarska 26:13 - Rachell Calhoun 30:36 - Joe Cronyn
13
Thumbnail
42:32
Multiplication signObservational studyBuildingContext awarenessMetropolitan area networkComputer programmingProof theoryExecution unitEvent horizonComputer animation
Programming languageMereologyKeyboard shortcutFamilyOperating systemTouchscreenControl flowMultiplication signGroup actionRight angleResultantConfidence intervalGenderWordOnline helpProcess (computing)AdditionGoodness of fitInternetworkingForm (programming)State of matterNeuroinformatikMappingCASE <Informatik>Integrated development environmentLattice (order)Moment (mathematics)Observational studyComputer programmingSoftwareFiber bundleTheory of relativityData managementSet (mathematics)Cartesian coordinate systemBitElectronic program guideCodeType theoryFluid staticsLaptopSoftware bugElectronic mailing listFrustrationMultiplication
GenderPresentation of a groupSoftware development kitCartesian coordinate systemGreatest elementProjective planeInstallation artData miningMapping
Information technology consultingStaff (military)NumberGroup actionMereologyLink (knot theory)Lecture/Conference
Computer fileField (computer science)Open setEndliche ModelltheorieMultiplication signContent (media)Data conversionTraffic reportingProjective planeNumberArray data structureStack (abstract data type)Point (geometry)Buffer overflowComputer animation
Projective planePoint (geometry)Multiplication signGenderCodeTraffic reportingPatch (Unix)MathematicsCore dumpSpeech synthesisComputer animation
Online helpMultiplication signGenderCodeMereologyPatch (Unix)Projective planeDot productGoodness of fitExpert systemObservational studyType theoryProcess (computing)Computing platformSuite (music)Unit testingFreewareGroup actionOpen sourceFood energySpring (hydrology)CASE <Informatik>Core dumpEntire functionQuicksortLecture/Conference
Process (computing)Right angleRow (database)VideoconferencingDecimalQuery languageTask (computing)Loop (music)NumberObject (grammar)MereologyResidual (numerical analysis)Different (Kate Ryan album)Message passingBitStack (abstract data type)Error messageType theoryGenderBit rateWordMonster groupImplementationSinc functionAxiom of choiceDemo (music)Binary codeSoftware bugLambda calculusService-oriented architecturePoint (geometry)Inclusion mapRun time (program lifecycle phase)Software developerConnectivity (graph theory)CodeExpert systemFeedbackStudent's t-testEndliche ModelltheorieTelnetFunctional (mathematics)EmailFreezingShared memoryMixed realityArithmetic meanMultiplication signFigurate numberMalwareComputer animation
Online helpSoftware testingConnected spaceQueue (abstract data type)Message passingQuicksortElectronic mailing listServer (computing)Task (computing)CodeTelnetGastropod shellLoginBus (computing)Mathematical optimizationVarianceTerm (mathematics)Computer animation
CommutatorInternet forumDecision theorySoftware maintenanceProcess (computing)SpacetimeElectronic mailing listSelf-organizationTraffic reportingSet (mathematics)CodeState of matterStandard deviationFeedbackBitThermal conductivityWave packetLattice (order)Context awarenessConnected spaceCondition numberWindowPhysical lawPole (complex analysis)Bounded variationTheory of everythingMereologySampling (statistics)Row (database)Service (economics)GenderGroup actionInformationMathematicsNumberSheaf (mathematics)Element (mathematics)Data structureTerm (mathematics)Computer programmingSource codeStatisticsMessage passingDeterminantSound effectEvent horizonUniverse (mathematics)FreewareLine (geometry)RotationOpen sourceEmailWebsiteInternet service provider
RoboticsFactory (trading post)NumberProcess (computing)Computer programmingSurface of revolutionMathematicsPlastikkarteComputer animation
Cellular automatonField (computer science)Sinc functionComputer programmingComputer animation
InternetworkingNumeral (linguistics)WebsiteWordEvent horizonProjective planeFreewareCodeAndroid (robot)Observational studyRegular graphMobile appComputer animation
WebsiteOnline helpMultiplication signEvent horizonProjective planeSelf-organizationLecture/Conference
Computer programmingPhysical systemData miningEndliche ModelltheorieSummierbarkeitWindowMultiplication signCodeMacOS XDemo (music)Computer animationLecture/Conference
Product (business)Projective planeMultiplication signTouchscreenGenderComputer fileSystem administratorConfiguration spaceDefault (computer science)Graph coloringBuildingMedical imagingDatabaseRevision controlEntire functionStandard deviationBitWebsiteCodeExecution unitDemo (music)Mobile appComputer animation
Computer file2 (number)AreaDifferent (Kate Ryan album)DatabaseWebsiteComputer animation
Computer animationXML
Transcript: English(auto-generated)
come on every time he's doing that so yeah so hi everyone I'm Lucy and for the
people who didn't saw me at the booth today or yesterday I'm working for Django girls so I'm their awesomeness ambassador so Django girls is a foundation that helps organize a workshop around the world so it's
free one day workshop for women we started two years ago and now we have six thousand people that went through our workshop so I've attended the first jungle girls in Berlin whether what I was a total beginners are programming and since then I've organized two workshop in Paris and coach at seven events in
Europe so I wanted to share with you what I've learned about teaching so teaching is happening all the time and not only during beginners workshop it could be a friend asking for help or a colleague at works so sadly there is no magic recipe to make you a great teacher that there is a thing a list of things that you should absolutely not do for example you may want to grab the
keyboard from the hand of someone that you to show them quick here what you want them to do you shouldn't do that really don't don't do it because it's true though you're taking the keyboard from the hand of someone who is currently using it and imagine if it's a laptop you're currently taking away the laptop so don't do that because also it's
humiliating you literally saying to this person that they won't be able to fix their problem and that's wrong so what should you do if you can't see the screen ask the person if they can turn the screen or move a little bit if you need more detail on to be able to have them debug the code ask them or explain them how to do it for example you can say can you show me the
log or can you type git status press enter so the main idea is also to teach them tricks to so they will be able to debug the code when you're not there and it's really important because it will also add them build confidence that yes they can fix stuff the second things you all may want to do is saying something nice about the operating system the software or
programming language the people are using so let me be clear on that someone asked for your help not your opinion so the last time I attended a programming workshop someone said to me cool someone on Linux that's one less problem the thing is that was absolutely not true because I spent more than an
hour to debug a nasty bug to make things works and secondly that's also emitting again for the people that were there not using Linux and were starting to think what is wrong with my OS so people coming to programming workshop or looking for help end up about the skills knowledge or even legitimacy to ask your question or be on a workshop programming so your job is
like I said to help them build confidence and also make sure they have a great time learning so no nasty comments or judging and by the way don't even start about trolling with other attendees or learners because you're not here to prove you the biggest geek in this part of town you're here
again to help people learn something so tourism not taking the keyboard not judging not trolling that's maybe a lot of dance so what can you do you can help them about building a friendly environment so to do that you must respect the person you're teaching to so don't do sexist racist or a blessing
at least jokes no it's easy my grandma could do it or other suitable ism tried to also create a relation where they can feel they can ask question to do that tell them that no they won't bother you with all the question because you're here to help them also try to answer the question
positively you can say something like it's a good question I'm not sure so let's check on the internet and also don't ever act surprised by the question because they need to know that you want to judge them also try to be in their shoes whoops let's start again so try to be in their shoes do not use jargon or don't say think like it's simple you just have to do this
because it's probably simple for you but this may not be the case for the person you're teaching to and finally building a friendly environment also need mean checking if the person needs a break or it's getting frustrating most of the people I've thought during opinion of workshops and you spend a whole day including lunch in front of the computer so don't hesitate to
invite them to take breaks so be patient encouraging and remember that new learners can be slow which can be really frustrating for you try to remember they're going through a lot so be ready to repeat and expel things multiple time and also tell them it's okay if they don't know everything so be friendly celebrate small and big victories and don't ever show your
frustration keep in mind that you're here to empower them so if you want to know more about how to teach programming to someone you can check our guide coach the junglers org and I strongly invite you to go to Nicole gems talks tomorrow at 220 thanks for your attention I will be talking about
using es6 scss in Django another way so I start you have five minutes begin great maybe even faster so I think some of you already know about jungle
compressor it's jungle application which provides you very nice asset management and static handling stuff so I I'm using it for a long time and and there is a way to use es6 and scss in it but you need to write some mapping
between some stuff and note commands so it's not very convenient and I have made my little addition to Django compressor which called jungle compressor toolkit and let me just show you the results first so here I created just during the last presentation one jungle project and we have two jungle
applications base and up so first inside base we have some basic stuff for es6 for scss and inside another application we want to use it we want to import from GS from es6 from something as a junk application and same
for scss we want to have cross imports between Django applications because I prefer to keep static inside jungle apps not in one separate folder so now about installation yeah you need to install the Python package and
then to configure it small screen so here I just install my compressor toolkit that's Django compressor and that's mine so you use this mapping
for scss and for es6 and inside Django template using compressor you include just your final application as CSS and JavaScript inside which you reuse some another es6 from another applications so that's the insights and
now how does it work does it work at all yay it works the link is read and es6 is transpiled compiled merged minified and executed and that's the
great success that's it I suggest you to use it great thanks so yeah my name is Tobias McNulty I am the CEO at cactus group we are a 30 person Django consultancy based in North Carolina we have been using Django since 2007 and
it's it's been a really huge part of our success a number of our staff have contributed back to Django over the years and this is my pitch to all of you to get involved and contribute and to show you why I think that's important I just want to start with a recent example so raise your hands and
keep them up how many of you have used a model a file field before okay so a lot of people and now if you keep them up if you have how many of you have used that to store a file field in a remote storage like s3 previously so
also a lot of people and how many of you had to use the or sorry did not have to use the Django documentation to do that so how many of you were able to do that without using the Django docs so okay so document like maybe two or three people still have their hands up so documentation very important a few months back I was working to move a content from a text
field into a file field for a project after reading through the Django docs like any number of times I stumbled upon this stack overflow post here you know the post kind of shows a timeline of a conversation about file field the first one says what is the purpose of this file field open method somebody
else seven months later responds that you know the docs are a little bit misleading on that about a year later somebody commented oh somebody should really raise an issue on this and then here I am two and a half years later struggling through this trying to figure out what is the purpose of this file field open method and the docs are unchanged and no issue was ever
raised throughout the timeline on this point so for those of you who may not be aware on Django has an excellent issue tracker at code Django project calm if you discover an issue in Django even if you don't have time to dig into it then you know take a few minutes to first you know search for
the issue and make sure that it doesn't already exist and then if it doesn't you know file a simple report on that so I did my due diligence and submitted that issue a few weeks later we had one of our quarterly ship it days at cactus and I spent a few hours you know working on this and within that time was able to get a PR submitted to Django master and then
you know with some back and forth and code review about you know three weeks later it's not something that you can kind of expect to get in immediately but within three weeks this really tiny change the documentation that I had was was merged into Django core and you know I think this is a really minor change if this is helpful to at least one other person in
the future I will feel like that investment of my time was worthwhile and you know I also think it's worth to note that this is really just one tiny tiny change in the history of literally thousands of patches that have helped make Django what it is today so speaking of thousands of patches you know why do all of these people volunteer their time and energy
to contribute to Django core for those new to Django it's a great opportunity to learn and dig into how Django works you also get free expert code reviews from some of the most knowledgeable people in the community many of whom are here at the conference this week you get to
feel good you know not only about creating something but also you know about being part of this community and you know lastly of course contributions to open source projects you know however small can help improve your credentials when applying to jobs if you know I've piqued your curiosity and you're wondering where to start Django has really good docs on
contributing but you know those docs like everything else could always be improved as well so you know as you get started you know trying to set up the unit test suite for the first time for example use that as kind of a case study to think through what's working and what's not working maybe you discover a platform issue that's specific to your OS on the subject of
documentation I was talking to Tim Graham yesterday the Django fellow and he mentioned that his entire first year of Django contributions with nothing was nothing but documentation fixes I think that's incredible and you know no matter sort of how good Django's docs are they can always be improved and you know there's two IRC channels I think the Django sprint one will be
the one that we're using this week there are also you know there's issue tracker I mentioned earlier there are do I get extra time this week there are two types of Django sprints Tim Graham is running and running an informal one in the MBA lounge upstairs it's a little study alcove just
to the left as you come in it took me a while to find it and then Thursday and Friday will be the sprint so thanks very much and hope to see you around the conference all right so hi I'm Kenneth love my day job is teaching Python and Django I get to do it all through video and online which is kind of cool means I don't get a lot of feedback right away but it's
still neat so for the past couple of years I've been doing this and I've had hundreds thousands of students around the world I've picked up a couple of things that I think are handy for teaching so I'm gonna share this I overlapped with Lucy we should have collaborated first of all though I'm not
an expert I very well might be wrong so if I am tell me so that I'll get better but if I'm not wrong cool I lucked into something good all right so as a teacher as a developer trying to teach one of the problems is that you know too much so you've solved problems you've encountered all these
errors bugs you've read documentation you've gotten onto IRC which is really hard for people now you've gotten over your imposter syndrome at least slightly right I mean I still get nervous about teaching I've been doing it for two years I put out 30 courses in two years and I'm still very nervous about
teaching people I'm a bit nervous right now even and I know most of you beginners don't have any of those advantages though they were full of these unknown unknowns they don't know what they don't know they don't know how to find out what they don't know they don't know any of this stuff that's why they're beginners that's why they're coming to you to teach them stuff and as part of the holes in a Python thing you remember
how in the face of uncertainty you resist the urge to guess so you have to kind of resist that you have to try to guess what they don't know but find out if you can anyway let's go back to the beginner mindset this is what you need to get you've got to bring yourself back to where they are so
where were you 10 years ago five years ago six months ago if you only have the model dot objects dot all query and a for loop how would you then filter down the records that have a certain PK or a certain username right because all times they only have those two tools they know they have those two they
know both of those but they can't figure out the other stuff or they haven't been told so when you're teaching try to answer three questions tell them what you're gonna do what that problem solves then tell them why they need to do that or when they're going to need to do that when that problem is going to come up and then of course teach them how to actually
solve the thing so you show them that they have lambdas when would they use lambdas why would they use lambdas all right so then things to avoid when you're explaining try to avoid using the word easy because things aren't easy to beginners try to avoid simple because things aren't simple none of our stuff is simple just and only as Lucy said you're not going to just to do this
thing it's not only this problem and all you have to do is a hard one to get rid of but it's there try not to have that another point to bring up mom's aren't dumb so don't use mom's grandma's dad's uncle's grandpa's
whatever as examples all these people are very capable just don't come on didn't Spotify get in trouble for that anyway things to add instead of things to avoid try to use diverse and inclusive examples as Sarone mentioned
yesterday you want to have as big of an audience as possible you want to get as many people in mix in genders air towards feminine and non-binary sides on that we have more than enough male examples already if you're using visual aids represent as many different types of people as you possibly can genders races abilities have somebody who floats it doesn't matter just bring in
stuff and remember that in the wide world not everyone fits into a first name and last name not all dates show up as a month day year not all not all numbers have commas in them they have decimals instead I want to share a thing that I got for part of the gender I got an email from a
student about six months ago they emailed me to thank me for using explicitly the word they as a pronoun choice and of course they self describe themselves as brown autistic and non-binary or genderqueer and they felt like they didn't exist in the tech world so it's pretty amazing what one
word can mean to someone so learnings hard recognize the achievements that people have encouraged self-care introduce communities like Kojo here and thank you okay thank you so this has my Twitter handle if you
want to follow me or not so a couple things that you kind of need to like basically all along here is we use message-oriented malware specifically rabbit MQ for a lot of our asynchronous tasks and scheduled jobs and
this will communicate with salary cues and exchanges that we have set up and also just general basic familiarity with PDB I would love to go into more
detail on those titles but okay so so he has this really cool feature that I stumbled upon and it's called RDB and it basically is very similar to how you would use PDB is set trace inside your code you sprinkle it in where you think you're having a problem and it will give you access to the code at
runtime so it's it's it was surprising to me how easy this was actually to put in place given all of the different components that have to work together for this to kind of solidify so I was gonna do a quick demo
basically the steps are that I'm gonna start up a rabbit broker I'm gonna start up a celery worker that has the implementation of the task that I want to debug and then I'm going to apply an async function that communicates with the celery worker to basically start the job and then I'm
going to attach to the RDB session over telnet and profit from that so first is rabbit so that's very simple just rabbit MQ server next is my celery worker I have already got this all set up to work on a test celery queue
and I'm just logging so that's running and next I'm going to use Django shell plus and import my task and run it so you can see I'm doing
just passing a message Django con u.s. 2016 and I will now show you the code it's a very simple task that just prints out the message that it's given and you can see that I have the set trace already in there so you'll see
back in my my worker it's now waiting for a connection from my telnet so it has the port which is now six nine oh five and there I am I'm in PDB and you
have I'll make that bigger you have basically all of the things that you would normally have from PDB you would have you know list help step next that sort of thing so I'm just gonna continue here and you can see that it will then print out my message in the log for hello Django con thank you so
I'm here to say my name is and for the last couple of months I've been
working with the TSF code of conduct committee and today we are announcing quite an exciting thing for us I already pull how it one of our other members are I did it at Europe item which was like an hour ago so we are synchronizing today and so we've been working for a couple of weeks now and so I'm gonna tell you about what we've been working on and what we do so let's
start with what we do so the TSF code of conduct committee's job is just a group of people whose job is to make sure that Django community provides a harassment free experience for everyone involved we deal with and keep record of code of conduct violations as well as provide support for conference organizers or moderators of Django online spaces like reddit or mailing
lists and to help them keep their members safe so we're currently seven people scattered across the world we've got members in Australia and Europe Africa and States and it's makes arranging meetings very fun we had
night one at 8 a.m. today so today I would like to tell you a little bit about the thing we've been working on for the last couple of weeks which is making our internal documentation existing at all and then make it public today so starting from so this documentation is going to contain
everything from how exactly we are dealing with the issues that are reported to us through establishing on like the on-call rotation duty where we've got now to make sure we don't forget about our own well-being and so everything is in there so you can now go and check it out and github it's open source we have a creating creative common license and I will tell
you now very briefly what you can find inside but I really encourage you to check it out and read it on your own so in the first after you can learn about the structure from the membership of the community will tell you who are the members when they joined and when their term at the committee ends you can also find out how members are added and removed from
the community so it's all transparent now then we also dive straight into the most important chapter of the whole thing which is how we handle code of conduct violations and you can learn about our uncle duty I mentioned go for the entire process since the report is made until it's considered closed as well as learning about the shepherding and how we make decisions
then the equally important section is dedicated to the way we keep records who has access and for how long and how is your information and where we start it's all in there and public and one of the most valuable services we provide to the community is a central record of all code of conduct
violations that took place in different often very disconnected parts of our community so we are now quite we've done this for a while but now we're quite officially offering a way for community organizers to reach out to us before their event takes place place to make sure that none of their attendees is blacklisted with us and we also extend this invitation to use the
service other Python communities not just Django and last but not least you can find about how we handle transparency and see statistics of reports and actions taken as well as a number of blacklisted and black people and we are still planning to expand on the section in the future but so we hope
this is just a small step towards something bigger so what's the goal we hope that making this documentation public is going to help us raise awareness about the work we are doing as well as demystify the process of what happens when report is made we realize that code of conduct can be scary for some and we like to show you exactly how we deal with issues
arising so the decision to report something is as straightforward and obvious as possible we also hope that making this transparent we're gonna help other communities outside of Django world to make their processes better because code of conduct is on is very important but but only when it's enforced and just having published on the website is not enough
and it took us quite a while to figure how this whole thing works so we hope that we're gonna help other communities make this happen and last but not least we are looking to improve our processes with your feedback and I encourage you to take a look at our issues on our pull requests and and we are very excited to see your impact on it and last I'd like
to thank everyone in the DSF code of conduct committee as well as many members of the community who had to make this happen all right hello I'm Rachel I'm here to talk about inspiring women to fall in love with programming I talk fast and being up here I'm a little bit
nervous so I'll talk to you faster but that's okay because most of you are native English speakers I come from recently Korea so I was it's kind of for me okay so first let me who am I I'm Rachel I studied Spanish and French espanol français in university and then I taught English in Korea I also
learned Korean and then I started studying Python to try to change careers and now I do Django so that's kind of my background okay so anybody know what this is have you ever seen these before it's a job that's what I it they're called knocker-uppers and what they do is they one of them blow
something like a stone or to knock the window to wake people up before we had alarm clocks and the other one would knock it with a pole I kind of got inspired by seeing another talk by Sally Williams and she was explained that jobs change and jobs are changing now too so let me talk about this so this is something we kind of can relate to jobs are changing this is
factory but also like in banking traders it's all starting to change it's called the fourth Industrial Revolution and so let's take a look here the WEF in January of this year but I report in five years not like 20 years from now it's five years seven million jobs will disappear in only two million will
be replaced and this number is because smart technology robots etc but this number will disproportionately affect women because for example if this continues for jobs that men will lose only one will be replaced but for women 20 jobs that will be lost only one will be replaced so that's why it's
really important to get more women not just in the schools and start education but now okay because it's not just programming it's CS plus X I'm sure some of you have heard of this but it's you know CS plus fashion CS plus education CS plus medicine it's not a separate field they're all going to be
combined okay so and how can we do that I'm sure you guys have heard this Django girls a lot recently and that's kind of where I come from Django girls chapter in Seoul and Django girls is one-day workshop to inspire women to fall in love with programming so what I want to talk
today is about what's next this is our workshop in Seoul last year was the first what our goal is and what I hope to achieve is not just inspiring women but supporting them on their next step so after they're inspired what do they do in Seoul we have a curriculum first workshop and then code camps and
we have two month code camp to go back to the basics and learn Python and Django HTML CSS and then we do two month base code camp it's all free and with sponsor support that will focus on making your own projects so you've learned it now do something with it and that's the best way to learn it all right and here we have if you go to our website Django girl sold out
org you can see a bunch about 15 projects came out of that websites online and we even had one Android app we also did a lot of community events workshops regular study meetups on the weekends so I want to encourage other
cities and other Django girls communities or you can start your own to continue education after the workshop all right and we learned by doing and master by teaching we're working on a nonprofit website I'd like some help if you could but because our members are all contributing myself included this was a participant she became a coach the next time around
master by teaching so how can you contribute you can be a coach or an organizer in your own city you can offer sponsorship for our events you can offer scholarships to your events or other workshops also contribute Django girls dot org slash contribute you can find other ways to contribute or get hub jail girls code camp there's a light leadership nonprofit project for
a school in Peru we're making and also we're trying to develop a curriculum for supporting women after the workshop so I hope I inspired you to help us inspire women to fall in love program thank you I wanted to start off today and I have some notes but I'm going to try to not look at or
follow them very much who in the room has used Docker before and you see a show of hands so I see some hands not up that's good some of you will not know that I don't know what I'm doing so I just want to also disclaim none of the code I'm using today is mine because then it really wouldn't work like really wouldn't work so if you haven't used
this I'm not going to teach you anything today you're just gonna see me use Docker but what I'm really hoping is that it inspires you to try using it because it's an amazing tool and I love using it daily and I try to tell everyone who hasn't used it before that they should get out there and try using it so this is me at Joe Cronin and I worked for cash star in Portland
Maine so first off does installing dependencies ever make you feel like this I know I've been in a few situations this was my first Django
shop working at cash star and I think I spent about a month installing things and figuring out like oh I'm missing another system requirement missing another system requirement and it was just really kind of a pain to get up and running so fear dependency hell no more because with Docker all things are possible you don't need to install anything so regardless of what
operating system you're on it's now supported on Mac OS X it's supported in Windows supported in Linux so really no matter what you're running it's a great tool to have and it's time for our first demo so let's see if I can fall flat on my face really quick what I'm going to do is I'm actually going to
start a brand new project so we're gonna do Django admin start project and can you see that on the big screen everybody is that okay new project alright so we're gonna go in the new project I'm going to create a requirement and save that and then I'm going to create a Docker file and I'm
going to use the official Docker image so all I have to do is say this container is from Django on build and that's the on build version of the
Django docker container from there I can just say docker build going to tag it and call it docker demo and so what this is going to do is it's going to run through their docker container that they've provided run the steps that they have and it by default just runs manage.py so basically it's gonna do
everything for me I didn't have to write any code and this project is going to hopefully run without a problem so now I'm going to run my docker demo and of course it fails because I still have something running so
one second get rid of those alright so my docker demo is up and running as you can see it kind of looks like it's just hanging but that's because I didn't attach to or watch what's going on in the container whatsoever I will print out the standard out from the Django website and so what I'm going to do now is open that up and you say it worked so one of two really gonna try
to race through how am I doing on time okay so we're doing alright the second one is actually a little bit faster so quickly but wait there's more if you've used docker how do you use docker compose okay so if you
haven't used docker compose basically it's an easy way to have an entire configuration file that says run this this way run that this way you can have your database your app your everything all configured pre-configured I can do all of this with one command whoa all right so we're gonna go ahead and try this now and go back out and yeah thank you I'll just go back in with
something different nerves are getting to me so docker composing Django and I'm
going to run docker compose up now I've already downloaded all of the files from before which is why you're not standing here for 20 minutes watching things download I figured that would probably be a good idea so it's up it's running we're going to go to the localhost 80 for this one and I have a
website so this is running a database running Django it's fully functional and it took me one command in 15 seconds per run so if you've never used it before I highly recommend going and taking a look and thank you all very much