Skip to content

Commit 35427aa

Browse files
mattmakaimattmakai
committed
fixing up the source and app dependencies pages
1 parent 15bf93a commit 35427aa

8 files changed

Lines changed: 111 additions & 99 deletions

File tree

‎all.html‎

Lines changed: 42 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -4647,24 +4647,29 @@ <h2>Git resources</h2>
46474647
</li>
46484648
</ul>
46494649
<h2>Source control learning checklist</h2>
4650-
<p><i class="fa fa-check-square-o"></i>
4651-
Pick a version control system. Git is recommended because on the web there
4652-
are a significant number of tutorials to help both new and advanced users.</p>
4653-
<p><i class="fa fa-check-square-o"></i>
4654-
Learn basic use cases for version control such as committing changes, rolling
4655-
back to earlier file versions and searching for when lines of code were
4656-
modified during development history.</p>
4657-
<p><i class="fa fa-check-square-o"></i>
4658-
Ensure your source code is backed up in a central repository. A central
4659-
repository is critical not only if your local development version is corrupted
4660-
but also for the deployment process.</p>
4661-
<p><i class="fa fa-check-square-o"></i>
4662-
Integrate source control into your deployment process in three ways. First,
4663-
pull the project source code from version control during deployments. Second,
4664-
kick off deployments when code is modified by using webhooks or polling on
4665-
the repository. Third, ensure you can roll back to a previous version if a
4666-
code deployment goes wrong.</p>
4667-
<h3>Now that your source code is versioned, what's next?</h3>
4650+
<ol>
4651+
<li>
4652+
<p>Pick a version control system. Git is recommended because on the web there
4653+
are a significant number of tutorials to help both new and advanced users.</p>
4654+
</li>
4655+
<li>
4656+
<p>Learn basic use cases for version control such as committing changes,
4657+
rolling back to earlier file versions and searching for when lines of code
4658+
were modified during development history.</p>
4659+
</li>
4660+
<li>
4661+
<p>Ensure your source code is backed up in a central repository. A central
4662+
repository is critical not only if your local development version is
4663+
corrupted but also for the deployment process.</p>
4664+
</li>
4665+
<li>
4666+
<p>Integrate source control into your deployment process in three ways. First,
4667+
pull the project source code from version control during deployments.
4668+
Second, kick off deployments when code is modified by using webhooks or
4669+
polling on the repository. Third, ensure you can roll back to a previous
4670+
version if a code deployment goes wrong.</p>
4671+
</li>
4672+
</ol>
46684673
<h1>Application Dependencies</h1>
46694674
<p>Application dependencies are the libraries other than your project code
46704675
that are required to create and run your application. </p>
@@ -4824,20 +4829,25 @@ <h2>Open source app dependency projects</h2>
48244829
</li>
48254830
</ul>
48264831
<h2>Application dependencies learning checklist</h2>
4827-
<p><i class="fa fa-check-square-o"></i>
4828-
Ensure the libraries your web application depends on are all captured in a
4829-
requirement.txt file with pegged versions. </p>
4830-
<p><i class="fa fa-check-square-o"></i>
4831-
An easy way to capture currently installed dependencies is with the
4832-
<code>pip freeze</code> command.</p>
4833-
<p><i class="fa fa-check-square-o"></i>
4834-
Create a fresh virtualenv and install the dependencies from your
4835-
requirements.txt file by using the <code>pip install -r requirements.txt</code>
4836-
command.</p>
4837-
<p><i class="fa fa-check-square-o"></i>
4838-
Check that your application runs properly with the fresh virtualenv and only
4839-
the installed dependencies from the requirements.txt file.</p>
4840-
<h3>What do you need to learn after installing your app dependencies?</h3>
4832+
<ol>
4833+
<li>
4834+
<p>Ensure the libraries your web application depends on are all captured in
4835+
a requirement.txt file with pegged versions. </p>
4836+
</li>
4837+
<li>
4838+
<p>An easy way to capture currently installed dependencies is with the
4839+
<code>pip freeze</code> command.</p>
4840+
</li>
4841+
<li>
4842+
<p>Create a fresh virtualenv and install the dependencies from your
4843+
requirements.txt file by using the <code>pip install -r requirements.txt</code>
4844+
command.</p>
4845+
</li>
4846+
<li>
4847+
<p>Check that your application runs properly with the fresh virtualenv and
4848+
only the installed dependencies from the requirements.txt file.</p>
4849+
</li>
4850+
</ol>
48414851
<h1>Static content</h1>
48424852
<p>Some content on a website does not change and therefore should be served
48434853
up either directly through the web server or a content delivery network (CDN).

‎application-dependencies.html‎

Lines changed: 20 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -193,20 +193,26 @@ <h2>Open source app dependency projects</h2>
193193
</li>
194194
</ul>
195195
<h2>Application dependencies learning checklist</h2>
196-
<p><i class="fa fa-check-square-o"></i>
197-
Ensure the libraries your web application depends on are all captured in a
198-
requirement.txt file with pegged versions. </p>
199-
<p><i class="fa fa-check-square-o"></i>
200-
An easy way to capture currently installed dependencies is with the
201-
<code>pip freeze</code> command.</p>
202-
<p><i class="fa fa-check-square-o"></i>
203-
Create a fresh virtualenv and install the dependencies from your
204-
requirements.txt file by using the <code>pip install -r requirements.txt</code>
205-
command.</p>
206-
<p><i class="fa fa-check-square-o"></i>
207-
Check that your application runs properly with the fresh virtualenv and only
208-
the installed dependencies from the requirements.txt file.</p>
209-
<h3>What do you need to learn after installing your app dependencies?</h3>
196+
<ol>
197+
<li>
198+
<p>Ensure the libraries your web application depends on are all captured in
199+
a requirement.txt file with pegged versions. </p>
200+
</li>
201+
<li>
202+
<p>An easy way to capture currently installed dependencies is with the
203+
<code>pip freeze</code> command.</p>
204+
</li>
205+
<li>
206+
<p>Create a fresh virtualenv and install the dependencies from your
207+
requirements.txt file by using the <code>pip install -r requirements.txt</code>
208+
command.</p>
209+
</li>
210+
<li>
211+
<p>Check that your application runs properly with the fresh virtualenv and
212+
only the installed dependencies from the requirements.txt file.</p>
213+
</li>
214+
</ol>
215+
<h3>What's next after installing app dependencies?</h3>
210216
<div class="row">
211217
<div class="col-md-4">
212218
<div class="well select-next">

‎feeds/all.atom.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
<?xml version="1.0" encoding="utf-8"?>
2-
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-05-31T13:47:14Z</updated></feed>
2+
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-06-02T07:10:09Z</updated></feed>

‎source-control.html‎

Lines changed: 24 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -186,24 +186,30 @@ <h2>Git resources</h2>
186186
</li>
187187
</ul>
188188
<h2>Source control learning checklist</h2>
189-
<p><i class="fa fa-check-square-o"></i>
190-
Pick a version control system. Git is recommended because on the web there
191-
are a significant number of tutorials to help both new and advanced users.</p>
192-
<p><i class="fa fa-check-square-o"></i>
193-
Learn basic use cases for version control such as committing changes, rolling
194-
back to earlier file versions and searching for when lines of code were
195-
modified during development history.</p>
196-
<p><i class="fa fa-check-square-o"></i>
197-
Ensure your source code is backed up in a central repository. A central
198-
repository is critical not only if your local development version is corrupted
199-
but also for the deployment process.</p>
200-
<p><i class="fa fa-check-square-o"></i>
201-
Integrate source control into your deployment process in three ways. First,
202-
pull the project source code from version control during deployments. Second,
203-
kick off deployments when code is modified by using webhooks or polling on
204-
the repository. Third, ensure you can roll back to a previous version if a
205-
code deployment goes wrong.</p>
206-
<h3>Now that your source code is versioned, what's next?</h3>
189+
<ol>
190+
<li>
191+
<p>Pick a version control system. Git is recommended because on the web there
192+
are a significant number of tutorials to help both new and advanced users.</p>
193+
</li>
194+
<li>
195+
<p>Learn basic use cases for version control such as committing changes,
196+
rolling back to earlier file versions and searching for when lines of code
197+
were modified during development history.</p>
198+
</li>
199+
<li>
200+
<p>Ensure your source code is backed up in a central repository. A central
201+
repository is critical not only if your local development version is
202+
corrupted but also for the deployment process.</p>
203+
</li>
204+
<li>
205+
<p>Integrate source control into your deployment process in three ways. First,
206+
pull the project source code from version control during deployments.
207+
Second, kick off deployments when code is modified by using webhooks or
208+
polling on the repository. Third, ensure you can roll back to a previous
209+
version if a code deployment goes wrong.</p>
210+
</li>
211+
</ol>
212+
<h3>What do you want to learn about after source control?</h3>
207213
<div class="row">
208214
<div class="col-md-4">
209215
<div class="well select-next">

‎source/content/pages/07-web-app-deployment/08-source-control.markdown‎

Lines changed: 13 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -141,26 +141,20 @@ reviews the basics of distributed version control systems.
141141

142142

143143
## Source control learning checklist
144-
<i class="fa fa-check-square-o"></i>
145-
Pick a version control system. Git is recommended because on the web there
146-
are a significant number of tutorials to help both new and advanced users.
144+
1. Pick a version control system. Git is recommended because on the web there
145+
are a significant number of tutorials to help both new and advanced users.
147146

148-
<i class="fa fa-check-square-o"></i>
149-
Learn basic use cases for version control such as committing changes, rolling
150-
back to earlier file versions and searching for when lines of code were
151-
modified during development history.
147+
1. Learn basic use cases for version control such as committing changes,
148+
rolling back to earlier file versions and searching for when lines of code
149+
were modified during development history.
152150

153-
<i class="fa fa-check-square-o"></i>
154-
Ensure your source code is backed up in a central repository. A central
155-
repository is critical not only if your local development version is corrupted
156-
but also for the deployment process.
151+
1. Ensure your source code is backed up in a central repository. A central
152+
repository is critical not only if your local development version is
153+
corrupted but also for the deployment process.
157154

158-
<i class="fa fa-check-square-o"></i>
159-
Integrate source control into your deployment process in three ways. First,
160-
pull the project source code from version control during deployments. Second,
161-
kick off deployments when code is modified by using webhooks or polling on
162-
the repository. Third, ensure you can roll back to a previous version if a
163-
code deployment goes wrong.
155+
1. Integrate source control into your deployment process in three ways. First,
156+
pull the project source code from version control during deployments.
157+
Second, kick off deployments when code is modified by using webhooks or
158+
polling on the repository. Third, ensure you can roll back to a previous
159+
version if a code deployment goes wrong.
164160

165-
166-
### Now that your source code is versioned, what's next?

‎source/content/pages/07-web-app-deployment/09-app-dependencies.markdown‎

Lines changed: 9 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -164,22 +164,16 @@ further clarification.
164164

165165

166166
## Application dependencies learning checklist
167-
<i class="fa fa-check-square-o"></i>
168-
Ensure the libraries your web application depends on are all captured in a
169-
requirement.txt file with pegged versions.
167+
1. Ensure the libraries your web application depends on are all captured in
168+
a requirement.txt file with pegged versions.
170169

171-
<i class="fa fa-check-square-o"></i>
172-
An easy way to capture currently installed dependencies is with the
173-
``pip freeze`` command.
170+
1. An easy way to capture currently installed dependencies is with the
171+
``pip freeze`` command.
174172

175-
<i class="fa fa-check-square-o"></i>
176-
Create a fresh virtualenv and install the dependencies from your
177-
requirements.txt file by using the ``pip install -r requirements.txt``
178-
command.
173+
1. Create a fresh virtualenv and install the dependencies from your
174+
requirements.txt file by using the ``pip install -r requirements.txt``
175+
command.
179176

180-
<i class="fa fa-check-square-o"></i>
181-
Check that your application runs properly with the fresh virtualenv and only
182-
the installed dependencies from the requirements.txt file.
177+
1. Check that your application runs properly with the fresh virtualenv and
178+
only the installed dependencies from the requirements.txt file.
183179

184-
185-
### What do you need to learn after installing your app dependencies?

‎source/theme/templates/choices/application-dependencies.html‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
<h3>What's next after installing app dependencies?</h3>
12
<div class="row">
23
<div class="col-md-4">
34
<div class="well select-next">

‎source/theme/templates/choices/source-control.html‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
<h3>What do you want to learn about after source control?</h3>
12
<div class="row">
23
<div class="col-md-4">
34
<div class="well select-next">

0 commit comments

Comments
 (0)