summaryrefslogtreecommitdiff
path: root/posts/2015-08-22-deployment-on-friday.md
diff options
context:
space:
mode:
authorFranck Cuny <franckcuny@gmail.com>2016-07-31 10:16:40 -0700
committerFranck Cuny <franckcuny@gmail.com>2016-07-31 13:42:48 -0700
commit63f413891d5adc596e4d51dfba4d0d23fdea3ca4 (patch)
treec2726b60515057a20f434bd89c596360ef17852b /posts/2015-08-22-deployment-on-friday.md
parentAdd Google Analytic tracker. (diff)
downloadlumberjaph-63f413891d5adc596e4d51dfba4d0d23fdea3ca4.tar.gz
Stop generating a static site.
Diffstat (limited to '')
-rw-r--r--posts/2015-08-22-deployment-on-friday.md (renamed from content/post/2015-08-22-deployment-on-friday.md)6
1 files changed, 0 insertions, 6 deletions
diff --git a/content/post/2015-08-22-deployment-on-friday.md b/posts/2015-08-22-deployment-on-friday.md
index eba7786..a1fb93c 100644
--- a/content/post/2015-08-22-deployment-on-friday.md
+++ b/posts/2015-08-22-deployment-on-friday.md
@@ -1,9 +1,3 @@
----
-date: 2015-08-22T00:00:00Z
-summary: In which we deploy our code on a Friday afternoon.
-title: Deploying to production on a Friday
----
-
There's a lot of reasons to not deploy code to production on a Friday. If something goes wrong, you
might end up spending your Friday night, or worst, your entire weekend, fixing some issue. But
there's no reasons Friday should be different from any other day. It's not OK to spend a night