Effective PyCharm Transcripts
Chapter: Server-side Python web apps
Lecture: Server-side features
Login or
purchase this course
to watch this video and the rest of the course contents.
0:00
Before we actually dive into them.
0:01
Let's just do a quick flyover of some of the server side features that we're gonna
0:04
be focusing on in this chapter.
0:07
We're going to create server side,
0:09
server rendered web applications in python.
0:12
This is Flask, Django Fast API pyramid and all those sorts of things where we
0:17
write python code on a server.
0:19
It generates all sorts of html responses,
0:22
API's things like that.
0:24
We'll see how you might load an existing web project.
0:27
This might sound obvious like Michael.
0:29
Haven't we already loaded some projects?
0:31
Yes, yes, we have.
0:33
What we did is we loaded up projects where we could go to the application in
0:37
right click and say run. But the way you run up your pyramid app is
0:40
not by running a file, it's by running a server pointed at a configuration file
0:45
with some other settings. The way you run,
0:47
Django might be different the way you want run Flask could be using Flask run instead
0:52
of running a particular file. So we're going to see how you might load up
0:55
some of these existing web projects and run them.
0:59
We'll see PyCharm's, support for the popular html template in particular.
1:04
We're going to talk about probably jinja and maybe evenChameleon. PyCharm also has built in
1:10
support for managing the state of your web application.
1:14
Some web frameworks like Flask don't have this idea.
1:18
You just get them and you run them and off they go,
1:20
they do their thing. But Django has this manage py which will let you create
1:25
users or add apps or do all sorts of stuff.
1:28
Pyramid has this setup.py that will allow you to register it so it can be
1:33
run as a package and those sorts of things.
1:36
So we're going to talk a little bit about the set up and manage features that
1:40
PyCharm's supports for those frameworks.
1:42
We've already talked about marking a directory as marketed as a source root marking it as
1:48
a template folder. But this is the chapter where things like template folders and resource
1:53
roots make particularly important impacts on our projects.
1:57
So we'll see specifically how we can use the resource designation to get auto complete and
2:03
other types of checks and validations around our static resources like CSS and Javascript as well
2:10
as if we set up a template directory,
2:12
correct, We'll get automatic navigation between say a view method and its underlying template in
2:18
Flask. Oftentimes in web apps there's these little tools that have to run before you
2:23
can actually launch and run your application.
2:26
This might be web pack, it might be some NPM command.
2:30
It could be some minification of some of your resources like your CSS.
2:35
It could be a Typescript compiler,
2:37
you know, who knows what?
2:38
So there's all these little tasks and tools that might need to run to prepare our
2:42
web app from the source files to what browsers actually want.
2:46
We'll see how PyCharm has great support for a whole bunch of those.
2:49
So here's a bunch of things.
2:50
We're going to focus on for the server side features of PyCharm hold tight on
2:55
the client side. That's the next chapter where we talk about how you might use
2:58
Vue.js or other sorts of front end frameworks things like that.