Feed: Django on Matt Layman

Blog	Matt Layman
RSS 2.0 Feed	Django on Matt Layman
web	https://www.mattlayman.com/tags/django/
Last Update	05.17.2024
Posts	223

Django Tutorial Adventure Part 2

Dec. 13, 2018 » Django on Matt Layman » [Archived Version]

What happens when you take a novice web developer and put him in front of an audience equipped with the Django tutorial only? That’s what we did at Python Frederick. The conversation and learning that resulted was awesome. Check out the video on YouTube to see what you can learn too! Our presenter was Patrick Pierson. Patrick works for IronNet Cybersecurity as a Senior Software Engineer. He uses Python daily to deploy AWS resources and test the IronNet platform.

Third party integration modeling - Building SaaS #6

Dec. 5, 2018 » Django on Matt Layman » [Archived Version]

In this stream episode, we started a new integration with a 3rd party service. We created the database model to store information related to the service and looked at how we’re going to pull all the pieces together.

Updating data models - Building SaaS #5

Nov. 29, 2018 » Django on Matt Layman » [Archived Version]

In this stream episode, we took some new data from a new Django database model, and I showed how to add that data to different templates. Along the way, we wrote automated tests and generated a database migration.

Using a background scheduler - Building SaaS #4

Nov. 22, 2018 » Django on Matt Layman » [Archived Version]

In this episode, we added Celery beat to College Conductor. Celery beat is the scheduler for the Celery worker system. I walked through how to test new infrastructure, confirmed that Celery beat worked, then showed how to add it to Ansible, the infrastructure deployment tool.

Building SaaS with Python on Twitch

Nov. 19, 2018 » Django on Matt Layman » [Archived Version]

I started streaming on Twitch. The stream covers how to build a Software as a Service (SaaS) with Python using Django. The stream runs at 9pm Eastern time on Wednesday most weeks. I show developers how to build a site that is more complex than a tutorial. We look at: Designing and creating pages for users How to create automated tests for the code Making background jobs that handle business processes Deploying code and infrastructure development During the stream, we’re working on Col…

Multiple Stripe plans - Building SaaS #3

Nov. 8, 2018 » Django on Matt Layman » [Archived Version]

In this stream episode, I built a Django model that would allow my SaaS app (College Conductor) to deal with multiple Stripe plans. After building the model, we updated the landing page to display a different plan based on the database data from the model.

Reporting scraped data - Building SaaS #2

Oct. 31, 2018 » Django on Matt Layman » [Archived Version]

In this episode, I took data that we collected from a web scraping task built in the first stream and created a report email that could be sent to the site admin.

Building SaaS with Python and Django #1

Oct. 25, 2018 » Django on Matt Layman » [Archived Version]

This was the first episode and it was an experiment in streaming. In future episodes, I’ve greatly improved audio and video settings. I’d suggest checking those out.

RFNM - Request For New Maintainer

May 15, 2018 » Django on Matt Layman » [Archived Version]

The Pull Requests piled up. Each new PR added to the weight reminding me that I was not being a responsive maintainer. I felt guilty. Guilt: A feeling held by many open source maintainers who can’t (or don’t want to) continue on a project that they manage. Feeling guilty about contributing to open source is terrible. You feel like you’re letting people down or like you owe them something more.

Feature flags and waffles

June 27, 2017 » Django on Matt Layman » [Archived Version]

You’re on a team that wants to ship a Super Cool New Feature™. The feature will cause changes all over your web app. Instead of releasing the work in pieces, the marketing team wants to have a big reveal to create a buzz. How do you manage this challenge? One option is to keep all the work in a separate code branch. When everything is done, merge the code back into your main branch, ship it, and reveal it to the world.