Skip to content

Commit

Permalink
stagin server article
Browse files Browse the repository at this point in the history
  • Loading branch information
@matthiasn
matthiasn committed Oct 5, 2014
1 parent be62343 commit b4856e7
Show file tree
Hide file tree
Showing 5 changed files with 41 additions and 34 deletions.
22 changes: 12 additions & 10 deletions public/atom.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
<title><![CDATA[Matthias Nehlsen]]></title>
<link href="http://matthiasnehlsen.com/atom.xml" rel="self"/>
<link href="http://matthiasnehlsen.com/"/>
<updated>2014-10-04T18:53:13+02:00</updated>
<updated>2014-10-05T19:10:44+02:00</updated>
<id>http://matthiasnehlsen.com/</id>
<author>
<name><![CDATA[Matthias Nehlsen]]></name>
Expand All @@ -18,26 +18,28 @@
<link href="http://matthiasnehlsen.com/blog/2014/10/04/weekly-update/"/>
<updated>2014-10-04T19:06:00+02:00</updated>
<id>http://matthiasnehlsen.com/blog/2014/10/04/weekly-update</id>
<content type="html"><![CDATA[<p>This weekly update is mostly about organizational isssues around publishing articles and getting feedback for unfinished articles.</p>
<content type="html"><![CDATA[<p>This weekly update is mostly about organizational issues around publishing articles and getting feedback for unfinished articles.</p>
<!-- more -->
<h2>Test environment for my blog</h2>
<p>The other day, I published the unfinished second article in the <strong>Writing a System in Clojure</strong> series for getting some preliminary feedback, but without announcing the article just yet. What I did not think about though was RSS aggregators that notice and pick up new content nonetheless, so that was a little less than ideal on my part.</p>
<p>This week, I published the unfinished second article in the <strong>Writing a System in Clojure</strong> series for a getting some preliminary feedback, but without announcing the article just yet. What I did not think about though was RSS aggregators, so that was a little less than ideal on my part. Ideally, I should have a different way of publishing unfinished stuff in order to get feedback and then only have finalized articles on this blog.</p>
<p>Ideally, I should have a different way of publishing unfinished stuff in order to get feedback and then only have finalized articles on this blog.</p>
<p>So I came up with something different: a <strong>staging server</strong>. Just like I would want a test environment when developing an application, I also want a test environment for new articles. So I&#8217;ve pulled the unfinished article from master for now and put the unfinished article here:</p>
<p>So I came up with something different: a <strong>staging server</strong>. Just like I would want a test environment when developing an application, I also want a test environment for new articles. So I&#8217;ve removed the unfinished article from master for now and put the unfinished article here:</p>
<p><strong><a href="http://staging.matthiasnehlsen.com/blog/2014/10/01/Building-System-in-Clojure-2/">http://staging.matthiasnehlsen.com/blog/2014/10/01/Building-System-in-Clojure-2/</a></strong></p>
<p><strong><a href="http://staging.matthiasnehlsen.com/">http://staging.matthiasnehlsen.com/</a></strong></p>
<p>I&#8217;d love to get more feedback still. But what I got so far was also very helpful. Right now I am working on illustrating the mechanisms with some illustrations and I expect to be done with everything on Monday. I will also probably split the article in two as the current article is probably a little long.</p>
<p>The implementation of this staging server took like 5 minutes. All I had to do was clone the directory on the server, check out a different branch in the cloned directory, create a new DNS entry for <strong>staging.matthiasnehlsen.com</strong>, and modify the <strong>nginx</strong> configuration so that the staging URL point to that new directory.</p>
<h2>Closing remarks</h2>
<p>I got very helpful feedback so far, so at least publishing the unfinished article wasn&#8217;t useless at all. Right now I am working on illustrating the mechanisms with some illustrations and I expect to be done with everything on Monday. I will also probably split the article in two as the current article is a little too long.</p>
<p>Most importantly, check out the new <strong><a href="http://matthiasnehlsen.com/blog/2014/09/24/Building-Systems-in-Clojure-1/">article series</a></strong> that I just started. I hope you will find it useful and I am looking forward to your feedback. In addition, there have been plenty of new entries to my <strong><a href="https://github.com/matthiasn/Clojure-Resources">Clojure-Resources</a></strong> repository on GitHub. You may want to check that out if you&#8217;re interested in Clojure at all. Finally, I bought a useful gadget that makes my digital life a little better.</p>
<h2>Conclusion</h2>
<p>Until next week,
<p>While this little modification is probably not terribly useful for you, I feel like it will be much more convenient for my workflow. You can also check out the staging server to see new articles in the works. Just note that sharing links may or may not lead to <strong>404&#8217;s</strong> later on as there is no guarantee whatsoever that those links will last. If they end up in master, they should, but the may well not.</p>
<p>Thats all for now. Have a great week,
Matthias</p>
]]></content>
</entry>
Expand Down
22 changes: 12 additions & 10 deletions public/blog/2014/10/04/weekly-update/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
<meta name="author" content="Matthias Nehlsen">


<meta name="description" content="This weekly update is mostly about organizational isssues around publishing articles and getting feedback for unfinished articles. Test environment &hellip;">
<meta name="description" content="This weekly update is mostly about organizational issues around publishing articles and getting feedback for unfinished articles. The other day, I &hellip;">


<!-- http://t.co/dKP3o1e -->
Expand Down Expand Up @@ -91,26 +91,28 @@ <h1 class="entry-title">Weekly Update: Staging server for this blog</h1>
</header>


<div class="entry-content"><p>This weekly update is mostly about organizational isssues around publishing articles and getting feedback for unfinished articles.</p>
<div class="entry-content"><p>This weekly update is mostly about organizational issues around publishing articles and getting feedback for unfinished articles.</p>

<!-- more -->


<h2>Test environment for my blog</h2>
<p>The other day, I published the unfinished second article in the <strong>Writing a System in Clojure</strong> series for getting some preliminary feedback, but without announcing the article just yet. What I did not think about though was RSS aggregators that notice and pick up new content nonetheless, so that was a little less than ideal on my part.</p>

<p>This week, I published the unfinished second article in the <strong>Writing a System in Clojure</strong> series for a getting some preliminary feedback, but without announcing the article just yet. What I did not think about though was RSS aggregators, so that was a little less than ideal on my part. Ideally, I should have a different way of publishing unfinished stuff in order to get feedback and then only have finalized articles on this blog.</p>
<p>Ideally, I should have a different way of publishing unfinished stuff in order to get feedback and then only have finalized articles on this blog.</p>

<p>So I came up with something different: a <strong>staging server</strong>. Just like I would want a test environment when developing an application, I also want a test environment for new articles. So I&#8217;ve pulled the unfinished article from master for now and put the unfinished article here:</p>
<p>So I came up with something different: a <strong>staging server</strong>. Just like I would want a test environment when developing an application, I also want a test environment for new articles. So I&#8217;ve removed the unfinished article from master for now and put the unfinished article here:</p>

<p><strong><a href="http://staging.matthiasnehlsen.com/blog/2014/10/01/Building-System-in-Clojure-2/">http://staging.matthiasnehlsen.com/blog/2014/10/01/Building-System-in-Clojure-2/</a></strong></p>
<p><strong><a href="http://staging.matthiasnehlsen.com/">http://staging.matthiasnehlsen.com/</a></strong></p>

<p>I&#8217;d love to get more feedback still. But what I got so far was also very helpful. Right now I am working on illustrating the mechanisms with some illustrations and I expect to be done with everything on Monday. I will also probably split the article in two as the current article is probably a little long.</p>
<p>The implementation of this staging server took like 5 minutes. All I had to do was clone the directory on the server, check out a different branch in the cloned directory, create a new DNS entry for <strong>staging.matthiasnehlsen.com</strong>, and modify the <strong>nginx</strong> configuration so that the staging URL point to that new directory.</p>

<h2>Closing remarks</h2>
<p>I got very helpful feedback so far, so at least publishing the unfinished article wasn&#8217;t useless at all. Right now I am working on illustrating the mechanisms with some illustrations and I expect to be done with everything on Monday. I will also probably split the article in two as the current article is a little too long.</p>

<p>Most importantly, check out the new <strong><a href="/blog/2014/09/24/Building-Systems-in-Clojure-1/">article series</a></strong> that I just started. I hope you will find it useful and I am looking forward to your feedback. In addition, there have been plenty of new entries to my <strong><a href="https://github.com/matthiasn/Clojure-Resources">Clojure-Resources</a></strong> repository on GitHub. You may want to check that out if you&#8217;re interested in Clojure at all. Finally, I bought a useful gadget that makes my digital life a little better.</p>
<h2>Conclusion</h2>

<p>Until next week,
<p>While this little modification is probably not terribly useful for you, I feel like it will be much more convenient for my workflow. You can also check out the staging server to see new articles in the works. Just note that sharing links may or may not lead to <strong>404&#8217;s</strong> later on as there is no guarantee whatsoever that those links will last. If they end up in master, they should, but the may well not.</p>

<p>Thats all for now. Have a great week,
Matthias</p>
</div>

Expand Down
4 changes: 2 additions & 2 deletions public/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
<meta name="author" content="Matthias Nehlsen">


<meta name="description" content="This weekly update is mostly about organizational isssues around publishing articles and getting feedback for unfinished articles. ">
<meta name="description" content="This weekly update is mostly about organizational issues around publishing articles and getting feedback for unfinished articles. ">


<!-- http://t.co/dKP3o1e -->
Expand Down Expand Up @@ -94,7 +94,7 @@ <h1 class="entry-title"><a href="/blog/2014/10/04/weekly-update/">Weekly Update:
</header>


<div class="entry-content"><p>This weekly update is mostly about organizational isssues around publishing articles and getting feedback for unfinished articles.</p>
<div class="entry-content"><p>This weekly update is mostly about organizational issues around publishing articles and getting feedback for unfinished articles.</p>

</div>

Expand Down
6 changes: 3 additions & 3 deletions public/sitemap.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -162,19 +162,19 @@
</url>
<url>
<loc>http://matthiasnehlsen.com/blog/2014/10/04/weekly-update/</loc>
<lastmod>2014-10-05T18:45:02+02:00</lastmod>
<lastmod>2014-10-05T19:10:11+02:00</lastmod>
</url>
<url>
<loc>http://matthiasnehlsen.com/about/</loc>
<lastmod>2014-09-15T16:10:56+02:00</lastmod>
</url>
<url>
<loc>http://matthiasnehlsen.com/blog/archives/</loc>
<lastmod>2014-10-05T18:45:02+02:00</lastmod>
<lastmod>2014-10-05T19:10:11+02:00</lastmod>
</url>
<url>
<loc>http://matthiasnehlsen.com/</loc>
<lastmod>2014-10-05T18:45:02+02:00</lastmod>
<lastmod>2014-10-05T19:10:11+02:00</lastmod>
</url>
<url>
<loc>http://matthiasnehlsen.com/reading-lists/</loc>
Expand Down
21 changes: 12 additions & 9 deletions source/_posts/2014-10-04-weekly-update.markdown
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,21 +5,24 @@ date: 2014-10-04 19:06
comments: true
categories:
---
This weekly update is mostly about organizational isssues around publishing articles and getting feedback for unfinished articles.
This weekly update is mostly about organizational issues around publishing articles and getting feedback for unfinished articles.

<!-- more -->

## Test environment for my blog
This week, I published the unfinished second article in the **Writing a System in Clojure** series for a getting some preliminary feedback, but without announcing the article just yet. What I did not think about though was RSS aggregators, so that was a little less than ideal on my part. Ideally, I should have a different way of publishing unfinished stuff in order to get feedback and then only have finalized articles on this blog.
The other day, I published the unfinished second article in the **Writing a System in Clojure** series for getting some preliminary feedback, but without announcing the article just yet. What I did not think about though was RSS aggregators that notice and pick up new content nonetheless, so that was a little less than ideal on my part.

So I came up with something different: a **staging server**. Just like I would want a test environment when developing an application, I also want a test environment for new articles. So I've pulled the unfinished article from master for now and put the unfinished article here:
Ideally, I should have a different way of publishing unfinished stuff in order to get feedback and then only have finalized articles on this blog.

**[http://staging.matthiasnehlsen.com/blog/2014/10/01/Building-System-in-Clojure-2/](http://staging.matthiasnehlsen.com/blog/2014/10/01/Building-System-in-Clojure-2/)**
So I came up with something different: a **staging server**. Just like I would want a test environment when developing an application, I also want a test environment for new articles. So I've removed the unfinished article from master for now and put the unfinished article here:

I'd love to get more feedback still. But what I got so far was also very helpful. Right now I am working on illustrating the mechanisms with some illustrations and I expect to be done with everything on Monday. I will also probably split the article in two as the current article is probably a little long.
**[http://staging.matthiasnehlsen.com/](http://staging.matthiasnehlsen.com/)**

## Closing remarks
Most importantly, check out the new **[article series](/blog/2014/09/24/Building-Systems-in-Clojure-1/)** that I just started. I hope you will find it useful and I am looking forward to your feedback. In addition, there have been plenty of new entries to my **[Clojure-Resources](https://github.com/matthiasn/Clojure-Resources)** repository on GitHub. You may want to check that out if you're interested in Clojure at all. Finally, I bought a useful gadget that makes my digital life a little better.
The implementation of this staging server took like 5 minutes. All I had to do was clone the directory on the server, check out a different branch in the cloned directory, create a new DNS entry for **staging.matthiasnehlsen.com**, and modify the **nginx** configuration so that the staging URL point to that new directory.

Until next week,
I got very helpful feedback so far, so at least publishing the unfinished article wasn't useless at all. Right now I am working on illustrating the mechanisms with some illustrations and I expect to be done with everything on Monday. I will also probably split the article in two as the current article is a little too long.

## Conclusion
While this little modification is probably not terribly useful for you, I feel like it will be much more convenient for my workflow. You can also check out the staging server to see new articles in the works. Just note that sharing links may or may not lead to **404's** later on as there is no guarantee whatsoever that those links will last. If they end up in master, they should, but the may well not.

Thats all for now. Have a great week,
Matthias

0 comments on commit b4856e7

Please sign in to comment.