Je travaille actuellement sur une application Django que je compte publier sous licence libre, et je suis confronté au problème classique de l'exposition de la configuration au développeur via les settings de son propre projet.
Classiquement, on a tendance à proposer les settings "à plat", dans le module settings.py du projet :
-# settings.py
-MY_APP_NAME_FOO = 42
-MY_APP_NAME_ENABLE_CHUCK_NORRIZ_MODE = True
-# settings.py
+MY_APP_NAME_FOO = 42
+MY_APP_NAME_ENABLE_CHUCK_NORRIZ_MODE = True
+Et donc depuis votre appli, vous pouvez récupérer les settings utilisateur de cette façon, en leur assignant une valeur par défaut s'ils ne sont pas déclarés :
-# apps/myapp/foo.py
-from django.conf import settings
+# apps/myapp/foo.py
+from django . conf import settings
+
+FOO = getattr ( settings , 'MY_APP_NAME_FOO' , 42)
+ENABLE_CHUCK_NORRIZ_MODE = getattr ( settings , 'MY_APP_NAME_ENABLE_CHUCK_NORRIZ_MODE' , False )
+Simple, pratique, suffisant me direz vous. Oui, mais bon, c'est un petit peu verbeux à mon sens, et pas toujours souple pour gérer un catalogue de settings ainsi que leur surcharge. Et puis j'ai l'impression en préfixant systématiquement ces noms de variables de faire insulte à cette merveilleuse fonctionnalité qu'on appelle la gestion des espaces de noms (voire de refaire du PHP < 5.3, ce qui provoque chez moi des bouffées d'angoisse et entame un processus de décapilation douloureux, mais je m'égare).
Qui plus est, personnellement en temps que développeur, j'aurai tendance à préférer gérer les settings correspondant à une application dans un dictionnaire dédié, un peu comme ce que propose la django-debug-toolbar.
Par exemple, en reprenant l'exemple de code initial ou seul le setting ENABLE_CHUCK_NORRIZ_MODE est finalement surchargé :
-# settings.py
-MY_APP_CONFIG = {
- 'ENABLE_CHUCK_NORRIZ_MODE': True,
-}
-# settings.py
+MY_APP_CONFIG = {
+ 'ENABLE_CHUCK_NORRIZ_MODE' : True ,
+}
+J'ai donc trouvé un moyen assez simple de proposer cette fonctionnalité. Dans le fichier __init__.py de votre module d'application, ajoutez le code suivant :
-# apps/my_app/__init__.py
-from django.conf import settings
-
-app_settings = dict({
- 'FOO': 42,
- 'ENABLE_CHUCK_NORRIZ_MODE': False,
-}, **getattr(settings, 'MY_APP_CONFIG', {}))
-# apps/my_app/__init__.py
+from django . conf import settings
+
+app_settings = dict ({
+ 'FOO' : 42,
+ 'ENABLE_CHUCK_NORRIZ_MODE' : False ,
+}, ** getattr ( settings , 'MY_APP_CONFIG' , {}))
+Vous constaterez qu'on fusionne bêtement les settings par défaut et ceux de l'utilisateur qui auront la priorité de surcharge. Ainsi, partout depuis votre application, vous pourrez accéder à ce dictionnaire de settings de cette façon :
-# apps/my_app/utils.py
-from . import app_settings
-
-if app_settings.get('ENABLE_CHUCK_NORRIZ_MODE'):
- print 'Chuck Norriz is watching you'
-else:
- print 'Dance dance, little lamb'
-# apps/my_app/utils.py
+from . import app_settings
+
+if app_settings . get ( 'ENABLE_CHUCK_NORRIZ_MODE' ):
+ print 'Chuck Norriz is watching you'
+else :
+ print 'Dance dance, little lamb'
+Et bien entendu, pour importer les settings de l'application depuis n'importe où (sous réserve que le module de l'application soit dans votre PYTHON_PATH) :
-# foo/bar.py
-from my_app import app_settings
+# foo/bar.py
+from my_app import app_settings
+
+print app_settings . get ( 'FOO' ) # 42
+Merci de votre attention, et à bientôt pour de nouvelle aventures.
diff --git a/build/code/2011/djt/index.html b/build/code/2011/djt/index.html
index 316b0be..147a2ff 100644
--- a/build/code/2011/djt/index.html
+++ b/build/code/2011/djt/index.html
@@ -2,11 +2,12 @@
Creating a Custom Panel for the Django Debug Toolbar | Code | Nicolas Perriault
So let's write our first script, we want to retrieve the weather
forecast for a given city using Google:
-// script: meteo.js
-var page = new WebPage()
-, output = { errors: [], results: null };
-if (phantom.args.length == 0) {
- console.log('You must specify a city, eg. "Paris, France"');
- phantom.exit(1);
-}
-page.open('http://www.google.fr/search?q=meteo+' + phantom.args[0], function (status) {
- if (status !== 'success') {
- output.errors.push('Unable to access network');
- } else {
- var cells = page.evaluate(function(){
- try {
- var cells = document.querySelectorAll('.tpo tr tr')[4].querySelectorAll('td');
- return Array.prototype.map.call(cells, function(cell) {
- return cell.innerText.replace(/[^0-9]/g, '');
- });
- } catch (e) {
- return [];
- }
- });
- if (!cells || !cells.length > 0) {
- output.errors.push('No valid meteo data found');
- } else {
- output.results = {
- city: phantom.args[0],
- today: {
- afternoon: cells[1],
- morning: cells[2],
- },
- tomorrow: {
- afternoon: cells[3],
- morning: cells[4],
- }
- };
- }
- console.log(JSON.stringify(output, null, ' '));
- }
- phantom.exit();
-});
-// script: meteo.js
+var page = new WebPage ()
+, output = { errors: [], results: null };
+if ( phantom . args . length == 0 ) {
+ console . log (' You must specify a city , eg . "Paris, France" ');
+ phantom . exit ( 1 );
+}
+page . open (' http: //www.google.fr/search?q=meteo+' + phantom.args[0], function (status) {
+ if ( status !== ' success ') {
+ output . errors . push (' Unable to access network ');
+ } else {
+ var cells = page . evaluate ( function (){
+ try {
+ var cells = document . querySelectorAll ('. tpo tr tr ')[ 4 ]. querySelectorAll (' td ');
+ return Array . prototype . map . call ( cells , function ( cell ) {
+ return cell . innerText . replace ( / [ ^ 0 - 9 ] / g , '');
+ });
+ } catch ( e ) {
+ return [];
+ }
+ });
+ if ( ! cells || ! cells . length > 0 ) {
+ output . errors . push (' No valid meteo data found ');
+ } else {
+ output . results = {
+ city: phantom . args [ 0 ],
+ today: {
+ afternoon: cells [ 1 ],
+ morning: cells [ 2 ],
+ },
+ tomorrow: {
+ afternoon: cells [ 3 ],
+ morning: cells [ 4 ],
+ }
+ };
+ }
+ console . log ( JSON . stringify ( output , null , ' '));
+ }
+ phantom . exit ();
+});
+Notice we use the phantom.args Array which contains the parameters
passed to the script.
The main magic happens in the page.evaluate() method, we pass it a
@@ -150,48 +161,54 @@
Basic usage
document environment. It's a kind of non-persistent XSS injection
just to help you to operate on the page contents =)
Now it's time to launch the script to see how it goes:
-$ phantomjs meteo.js "Montpellier, France"
-{
- "errors": [],
- "results": {
- "city": "Montpellier, France",
- "today": {
- "afternoon": "29",
- "morning": "17"
- },
- "tomorrow": {
- "afternoon": "28",
- "morning": "17"
- }
- }
-}
-$ phantomjs meteo . js "Montpellier , France "
+{
+ "errors ": [],
+ "results ": {
+ "city ": "Montpellier , France ",
+ "today ": {
+ "afternoon ": "29",
+ "morning ": "17"
+ },
+ "tomorrow ": {
+ "afternoon ": "28",
+ "morning ": "17"
+ }
+ }
+}
+ Now with an invalid city name:
-$ phantomjs meteo.js "Unexistent City"
-{
- "errors": [
- "No valid meteo data found"
- ],
- "results": null
-}
-$ phantomjs meteo . js "Unexistent City "
+{
+ "errors ": [
+ "No valid meteo data found "
+ ],
+ "results ": null
+}
+ Let's try with another city, an existing one this time:
-$ phantomjs meteo.js "Paris, France"
-{
- "errors": [],
- "results": {
- "city": "Paris, France",
- "today": {
- "afternoon": "21",
- "morning": "11"
- },
- "tomorrow": {
- "afternoon": "21",
- "morning": "11"
- }
- }
-}
-$ phantomjs meteo . js "Paris , France "
+{
+ "errors ": [],
+ "results ": {
+ "city ": "Paris , France ",
+ "today ": {
+ "afternoon ": "21",
+ "morning ": "11"
+ },
+ "tomorrow ": {
+ "afternoon ": "21",
+ "morning ": "11"
+ }
+ }
+}
+ As a side note and in case you were wondering, you now understand a bit
more why I moved to Montpellier ;)
I CAN HAZ SCREENSHOTS
@@ -200,24 +217,26 @@ I CAN HAZ SCREENSHOTS
favorite framework (eg. jQuery )… or can render a
PNG image of a captured area of the webpage. The example below saves a
capture of the weather forecast area:
-// script: meteoclip.js
-var page = new WebPage();
-page.open('http://www.google.fr/search?q=meteo+montpellier,+France', function (status) {
- if (status !== 'success') {
- output.error = 'Unable to access network';
- } else {
- page.clipRect = {
- top: 127,
- left: 170,
- width: 400,
- height: 114
- }
- page.render('meteo.png');
- console.log('Capture saved');
- }
- phantom.exit();
-});
-// script: meteoclip.js
+var page = new WebPage ();
+page . open (' http: //www.google.fr/search?q=meteo+montpellier,+France', function (status) {
+ if ( status !== ' success ') {
+ output . error = ' Unable to access network ';
+ } else {
+ page . clipRect = {
+ top: 127 ,
+ left: 170 ,
+ width: 400 ,
+ height: 114
+ }
+ page . render (' meteo . png ');
+ console . log (' Capture saved ');
+ }
+ phantom . exit ();
+});
+Running the meteoclip.js script will get yourself this fancy image
stored in meteo.jpg:
diff --git a/build/code/2011/setup-jenkins-github-private-repository-ubuntu/index.html b/build/code/2011/setup-jenkins-github-private-repository-ubuntu/index.html
index 3b6dd52..c3d8ef8 100644
--- a/build/code/2011/setup-jenkins-github-private-repository-ubuntu/index.html
+++ b/build/code/2011/setup-jenkins-github-private-repository-ubuntu/index.html
@@ -2,11 +2,12 @@
Setup Jenkins for working with a private Github repository | Code | Nicolas Perriault
Jenkins project connected to a private repository hosted on Github , I thought it's worth a quick blog post. I'm using Ubuntu .
So first su as the jenkins user to create some SSH keypair:
-$ ssh-keygen -p
-Notice the -p option; this will allow to avoid asking for a passphrase (which Jenkins cannot so running as a daemon).
Try to ssh on github:
-$ ssh -T git@github.com
-The authenticity of host 'github.com (207.97.227.239)' can't be established.
-RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
-Are you sure you want to continue connecting (yes/no)? yes
-Hi username/reponame! You've successfully authenticated, but GitHub does not provide shell access.
-$ ssh - T git @ github . com
+The authenticity of host 'github.com (207.97.227.239)' can ' t be established .
+RSA key fingerprint is 16: 27: ac : a5 : 76: 28: 2d : 36: 63: 1b : 56: 4d : eb : df : a6 : 48.
+Are you sure you want to continue connecting ( yes / no ) ? yes
+Hi username / reponame ! You ' ve successfully authenticated , but GitHub does not provide shell access .
+ Notice that you're asked to allow github's hostname to be added to your known_hosts file: without completing this step, you're doomed.
Now, in the Jenkins project configuration interface, set the private repository url using the git protocol, eg. git@github.com:username/reponame.git.
That's it, Jenkins will be able to clone and use your private repo.
diff --git a/build/code/2012/dead-easy-yet-powerful-static-website-generator-with-flask/index.html b/build/code/2012/dead-easy-yet-powerful-static-website-generator-with-flask/index.html
index fc278c0..4d22ecb 100644
--- a/build/code/2012/dead-easy-yet-powerful-static-website-generator-with-flask/index.html
+++ b/build/code/2012/dead-easy-yet-powerful-static-website-generator-with-flask/index.html
@@ -2,11 +2,12 @@
Dead easy yet powerful static website generator with Flask | Code | Nicolas Perriault
virtualenv in a new directory and install the necessary packages using pip :
-$ mkdir sample_project && cd !$
-$ mkvirtualenv --no-site-packages `pwd`/env
-$ source env/bin/activate
-$ pip install Flask Frozen-Flask Flask-FlatPages
-$ mkdir sample_project && cd !$
+$ mkvirtualenv -- no - site - packages `pwd `/ env
+$ source env / bin / activate
+$ pip install Flask Frozen - Flask Flask - FlatPages
+ Write a very first version of our app in a sitebuilder.py file:
-from flask import Flask
-app = Flask(__name__)
+from flask import Flask
+app = Flask ( __name__ )
+
+@ app . route ( "/ ")
+def index ():
+ return "Hello World !"
+
+if __name__ == "__main__ ":
+ app . run ( port = 8000)
+Run it; you should see someting like:
-$ python sitebuilder.py
- * Running on http://127.0.0.1:8000/
- * Restarting with reloader
-$ python sitebuilder . py
+ * Running on http : // 127. 0. 0. 1: 8000/
+ * Restarting with reloader
+ Ensure with your browser that everyting is going fine by heading at http://127.0.0.1:8000/.
New iteration: adding flat pages
Flask-FlatPages provides a collection of pages to your Flask application. Pages are built from flat text files as opposed to a relational database.
Create a pages/ directory at the root of your project folder, and put a hello-world.md file in there:
-$ mkdir pages
-$ vi pages/hello-world.md
-$ mkdir pages
+$ vi pages / hello - world . md
+ The pages/hello-world.md:
title: Hello World
date: 2012-03-04
@@ -86,81 +95,91 @@ New iteration: adding flat pages
As you can see, we can write plain Mardown for our page contents. So let's rewrite our app to serve any flatpage by its filename:
-from flask import Flask
-from flaskext.flatpages import FlatPages
+from flask import Flask
+from flaskext . flatpages import FlatPages
-DEBUG = True
-FLATPAGES_AUTO_RELOAD = DEBUG
-FLATPAGES_EXTENSION = '.md'
+DEBUG = True
+FLATPAGES_AUTO_RELOAD = DEBUG
+FLATPAGES_EXTENSION = '.md'
-app = Flask(__name__)
-app.config.from_object(__name__)
-pages = FlatPages(app)
+app = Flask ( __name__ )
+app . config . from_object ( __name__ )
+pages = FlatPages ( app )
-@app.route('/')
-def index():
- return "Hello World"
+@ app . route ( '/' )
+def index ():
+ return "Hello World "
+
+@ app . route ( '/<path:path>/' )
+def page ( path ):
+ return pages . get_or_404 ( path ). html
+
+if __name__ == '__main__' :
+ app . run ( port = 8000)
+Now requesting http://127.0.0.1:8000/hello-world/ will display our flatpage. Note that the markdown source is converted to html by getting the html property of our page object.
New iteration: adding templates
Flask uses the Jinja2 template engine, so let's create some templates to decorate our pages. First create a templates directory at the root of the project:
-$ mkdir templates
-Create a base layout in templates/base.html:
-<!doctype html>
-<html>
-<head>
- <meta charset="utf-8">
- <title>My site</title>
-</head>
-<body>
- <h1><a href="{{ url_for("index") }}">My site</a></h1>
-{% block content %}
- <p>Default content to be displayed</p>
-{% endblock content %}
-</body>
-</html>
-<!doctype html>
+<html>
+<head>
+ <meta charset= "utf-8" >
+ <title> My site</title>
+</head>
+<body>
+ <h1><a href= " {{ url_for ( "index" ) }} " > My site</a></h1>
+{% block content %}
+ <p> Default content to be displayed</p>
+{% endblock content %}
+</body>
+</html>
+Note the use of the url_for() template helper, that's the way we generate urls using Flask and Jinja2.
Now the page.html template to fill this layout with page contents:
-{% extends "base.html" %}
+{% extends "base.html" %}
+
+{% block content %}
+ <h2> {{ page.title }} </h2>
+ {{ page.html | safe }}
+{% endblock content %}
+Our app is now:
-from flask import Flask, render_template
-from flaskext.flatpages import FlatPages
+from flask import Flask , render_template
+from flaskext . flatpages import FlatPages
-DEBUG = True
-FLATPAGES_AUTO_RELOAD = DEBUG
-FLATPAGES_EXTENSION = '.md'
+DEBUG = True
+FLATPAGES_AUTO_RELOAD = DEBUG
+FLATPAGES_EXTENSION = '.md'
-app = Flask(__name__)
-app.config.from_object(__name__)
-pages = FlatPages(app)
+app = Flask ( __name__ )
+app . config . from_object ( __name__ )
+pages = FlatPages ( app )
-@app.route('/')
-def index():
- return "Hello World"
+@ app . route ( '/' )
+def index ():
+ return "Hello World "
+
+@ app . route ( '/<path:path>/' )
+def page ( path ):
+ page = pages . get_or_404 ( path )
+ return render_template ( 'page.html' , page = page )
+
+if __name__ == '__main__' :
+ app . run ( port = 8000)
+Hell, what did we just do?
we created templates for our app; a common layout (base.html) and a page template (page.html)
@@ -170,27 +189,31 @@ New iteration: adding templates
New iteration: display the list of available pages on the homepage
For now our homepage has been a bit sick, to say the least. Let's make it an index of all available pages.
Create a templates/index.html with the following contents:
- {% extends "base.html" %}
-
-{% block content %}
- <h2>List of stuff</h2>
- <ul>
- {% for page in pages %}
- <li>
- <a href="{{ url_for("page", path=page.path) }}">{{ page.title }}</a>
- </li>
- {% else %}
- <li>No stuff.</li>
- {% endfor %}
- </ul>
-{% endblock content %}
-{% extends "base.html" %}
+
+{% block content %}
+ <h2> List of stuff</h2>
+ <ul>
+ {% for page in pages %}
+ <li>
+ <a href= " {{ url_for ( "page" , path = page.path ) }} " > {{ page.title }} </a>
+ </li>
+ {% else %}
+ <li> No stuff.</li>
+ {% endfor %}
+ </ul>
+{% endblock content %}
+Feel free to create more flat pages, the same way we did with hello-world.md, storing the file into the pages/ directory using the .md extension.
So the index() route of our app is now:
-@app.route('/')
-def index():
- return render_template('index.html', pages=pages)
-@ app . route ( '/' )
+def index ():
+ return render_template ( 'index.html' , pages = pages )
+If you reload the homepage, a list of all available flatpages is displayed with a link for each. Damn, that was pretty easy.
New iteration: adding metadata to pages
Flask-FlatPages allows to enter metadata for pages the same way we did for the title and the creation date with our hello-world.md, and access them using the page.meta property, which contains a plain silly python dict. That's pretty awesome when you think about it, heh?
@@ -204,106 +227,120 @@ New iteration: adding metadata to pages
For the records, metadata are described in YAML , so you can use strings, booleans, integers, floats, lists and even dicts which will be converted to their respective native Python equivalent.
We're going to use two different templates for listing general pages and tagged ones, using a shared template partial. Our index.html is now:
-{% extends "base.html" %}
-
-{% block content %}
- <h2>List of stuff</h2>
- {% with pages=pages %}
- {% include "_list.html" %}
- {% endwith %}
-{% endblock content %}
-{% extends "base.html" %}
+
+{% block content %}
+ <h2> List of stuff</h2>
+ {% with pages = pages %}
+ {% include "_list.html" %}
+ {% endwith %}
+{% endblock content %}
+Create a new tag.html template, which will display the list of tagged pages:
-{% extends "base.html" %}
-
-{% block content %}
- <h2>List of stuff tagged <em>{{ tag }}</em></h2>
- {% with pages=pages %}
- {% include "_list.html" %}
- {% endwith %}
-{% endblock content %}
-{% extends "base.html" %}
+
+{% block content %}
+ <h2> List of stuff tagged <em> {{ tag }} </em></h2>
+ {% with pages = pages %}
+ {% include "_list.html" %}
+ {% endwith %}
+{% endblock content %}
+The new _list.html template we need for inclusion contains:
-<ul>
-{% for page in pages %}
- <li>
- <a href="{{ url_for("page", path=page.path) }}">{{ page.title }}</a>
- {% if page.meta.tags|length %}
+<ul>
+{% for page in pages %}
+ <li>
+ <a href= " {{ url_for ( "page" , path = page.path ) }} " > {{ page.title }} </a>
+ {% if page.meta.tags | length %}
| Tagged:
- {% for page_tag in page.meta.tags %}
- <a href="{{ url_for("tag", tag=page_tag) }}">{{ page_tag }}</a>
- {% endfor %}
- {% endif %}
- </li>
-{% else %}
- <li>No page.</li>
-{% endfor %}
-</ul>
-
+
{% for page_tag in page.meta.tags %}
+
<a href= " {{ url_for ( "tag" , tag = page_tag ) }} " > {{ page_tag }} </a>
+
{% endfor %}
+
{% endif %}
+
</li>
+
{% else %}
+
<li> No page.
</li>
+
{% endfor %}
+
</ul>
+
Let's add a new tag route to our app, to use our new tag.html template:
-@app.route('/tag/<string:tag>/')
-def tag(tag):
- tagged = [p for p in pages if tag in p.meta.get('tags', [])]
- return render_template('tag.html', pages=tagged, tag=tag)
-@ app . route ( '/tag/<string:tag>/' )
+def tag ( tag ):
+ tagged = [ p for p in pages if tag in p . meta . get ( 'tags' , [])]
+ return render_template ( 'tag.html' , pages = tagged , tag = tag )
+Note: if you didn't like Python's list comprehensions yet, now you do.
New iteration: generate the static stuff
Well, for now we only have a dynamic website, which uses and serves flatpages stored on the filesystem: CRAP. But the idea's of course not to host a Flask app but a set of static files and assets to skip the need of any application server.
Here enters Frozen-Flask. Its use is damn easy:
-import sys
-
-from flask import Flask, render_template
-from flaskext.flatpages import FlatPages
-from flask_frozen import Freezer
-
-DEBUG = True
-FLATPAGES_AUTO_RELOAD = DEBUG
-FLATPAGES_EXTENSION = '.md'
-
-app = Flask(__name__)
-app.config.from_object(__name__)
-pages = FlatPages(app)
-freezer = Freezer(app)
-
-@app.route('/')
-def index():
- return render_template('index.html', pages=pages)
-
-@app.route('/tag/<string:tag>/')
-def tag(tag):
- tagged = [p for p in pages if tag in p.meta.get('tags', [])]
- return render_template('tag.html', pages=tagged, tag=tag)
-
-@app.route('/<path:path>/')
-def page(path):
- page = pages.get_or_404(path)
- return render_template('page.html', page=page)
-
-if __name__ == '__main__':
- if len(sys.argv) > 1 and sys.argv[1] == "build":
- freezer.freeze()
- else:
- app.run(port=8000)
-import sys
+
+from flask import Flask , render_template
+from flaskext . flatpages import FlatPages
+from flask_frozen import Freezer
+
+DEBUG = True
+FLATPAGES_AUTO_RELOAD = DEBUG
+FLATPAGES_EXTENSION = '.md'
+
+app = Flask ( __name__ )
+app . config . from_object ( __name__ )
+pages = FlatPages ( app )
+freezer = Freezer ( app )
+
+@ app . route ( '/' )
+def index ():
+ return render_template ( 'index.html' , pages = pages )
+
+@ app . route ( '/tag/<string:tag>/' )
+def tag ( tag ):
+ tagged = [ p for p in pages if tag in p . meta . get ( 'tags' , [])]
+ return render_template ( 'tag.html' , pages = tagged , tag = tag )
+
+@ app . route ( '/<path:path>/' )
+def page ( path ):
+ page = pages . get_or_404 ( path )
+ return render_template ( 'page.html' , page = page )
+
+if __name__ == '__main__' :
+ if len ( sys . argv ) > 1 and sys . argv [ 1] == "build ":
+ freezer . freeze ()
+ else :
+ app . run ( port = 8000)
+And run:
-$ python sitebuilder.py build
-$ python sitebuilder . py build
+ Open the build folder generated by this command:
-$ tree
-.
-├── hello-world
-│ └── index.html
-├── index.html
-└── tag
- ├── awesome
- │ └── index.html
- ├── general
- │ └── index.html
- └── stuff
- └── index.html
-
-5 directories, 5 files
-$ tree
+.
+├── hello - world
+│ └── index . html
+├── index . html
+└── tag
+ ├── awesome
+ │ └── index . html
+ ├── general
+ │ └── index . html
+ └── stuff
+ └── index . html
+
+5 directories , 5 files
+ MIND: BLOWN.
You can now deploy the contents of this build directory to any webserver which's able to serve static files, and you're done. With just 34 lines of manually written Python code… not bad heh?
Of course, our website is pretty crappy right now, but you should be get started to add features on your own, now.
@@ -321,8 +358,8 @@ New iteration: generate the static stuff