Skip to content

Commit 6bf875c

Browse files
mattmakaimattmakai
committed
adding learning checklist for source control
1 parent 8e350dc commit 6bf875c

File tree

7 files changed

+46
-5
lines changed

7 files changed

+46
-5
lines changed

‎change-log.html‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,9 +47,10 @@ <h1>Change Log</h1>
4747
<h2>2014</h2>
4848
<h3>May</h3>
4949
<ul>
50+
<li>Added learning checklist for source control.</li>
5051
<li>Moving learning checklists to the bottom of the pages since they are
5152
specific advice for steps to take after reading a section.</li>
52-
<li>Adding a stub section for APIs.</li>
53+
<li>Added a stub section for APIs.</li>
5354
<li>Cleaned up and polished the task queues and web analytics pages.</li>
5455
<li>Added learning checklist to operating systems, web servers, task queues,
5556
monitoring pages and WSGI servers.</li>

‎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>2014-05-22T07:47:24Z</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>2014-05-22T09:39:06Z</updated></feed>

‎future-directions.html‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,6 @@ <h1>Future Directions</h1>
6161
<p>Create learning checklists for every section where it makes sense. The
6262
remaining sections that need checklists are </p>
6363
<ol>
64-
<li>source control</li>
6564
<li>application dependencies</li>
6665
<li>configuration management</li>
6766
<li>NoSQL data stores</li>

‎source-control.html‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,24 @@ <h2>Source control resources</h2>
132132
and merging source code.</p>
133133
</li>
134134
</ul>
135+
<h2>Source control learning checklist</h2>
136+
<p><i class="fa fa-check-square-o"></i>
137+
Pick a version control system. Git is recommended because on the web there
138+
are a significant number of tutorials to help both new and advanced users.</p>
139+
<p><i class="fa fa-check-square-o"></i>
140+
Learn basic use cases for version control such as committing changes, rolling
141+
back to earlier file versions and searching for when lines of code were
142+
modified during development history.</p>
143+
<p><i class="fa fa-check-square-o"></i>
144+
Ensure your source code is backed up in a central repository. A central
145+
repository is critical not only if your local development version is corrupted
146+
but also for the deployment process.</p>
147+
<p><i class="fa fa-check-square-o"></i>
148+
Integrate source control into your deployment process in three ways. First,
149+
pull the project source code from version control during deployments. Second,
150+
kick off deployments when code is modified by using webhooks or polling on
151+
the repository. Third, ensure you can roll back to a previous version if a
152+
code deployment goes wrong.</p>
135153
<h3>Now that your source code is versioned, what's next?</h3>
136154
<div class="row">
137155
<div class="col-md-4">

‎source/content/pages/03-deployment/0313-source-control.markdown‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,4 +94,27 @@ reviews the basics of distributed version control systems.
9494
and merging source code.
9595

9696

97+
## Source control learning checklist
98+
<i class="fa fa-check-square-o"></i>
99+
Pick a version control system. Git is recommended because on the web there
100+
are a significant number of tutorials to help both new and advanced users.
101+
102+
<i class="fa fa-check-square-o"></i>
103+
Learn basic use cases for version control such as committing changes, rolling
104+
back to earlier file versions and searching for when lines of code were
105+
modified during development history.
106+
107+
<i class="fa fa-check-square-o"></i>
108+
Ensure your source code is backed up in a central repository. A central
109+
repository is critical not only if your local development version is corrupted
110+
but also for the deployment process.
111+
112+
<i class="fa fa-check-square-o"></i>
113+
Integrate source control into your deployment process in three ways. First,
114+
pull the project source code from version control during deployments. Second,
115+
kick off deployments when code is modified by using webhooks or polling on
116+
the repository. Third, ensure you can roll back to a previous version if a
117+
code deployment goes wrong.
118+
119+
97120
### Now that your source code is versioned, what's next?

‎source/content/pages/10-misc/1005-change-log.markdown‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,10 @@ the
2424

2525
## 2014
2626
### May
27+
* Added learning checklist for source control.
2728
* Moving learning checklists to the bottom of the pages since they are
2829
specific advice for steps to take after reading a section.
29-
* Adding a stub section for APIs.
30+
* Added a stub section for APIs.
3031
* Cleaned up and polished the task queues and web analytics pages.
3132
* Added learning checklist to operating systems, web servers, task queues,
3233
monitoring pages and WSGI servers.

‎source/content/pages/10-misc/1007-future-directions.markdown‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,6 @@ Here are some things I'm actively working on:
3939
* Create learning checklists for every section where it makes sense. The
4040
remaining sections that need checklists are
4141

42-
1. source control
4342
1. application dependencies
4443
1. configuration management
4544
1. NoSQL data stores

0 commit comments

Comments
 (0)