From b4856e7d7ac3d9d271eb33c853b10eb95db6d254 Mon Sep 17 00:00:00 2001 From: Matthias Nehlsen Date: Sun, 5 Oct 2014 19:10:59 +0200 Subject: [PATCH] stagin server article --- public/atom.xml | 22 ++++++++++--------- .../blog/2014/10/04/weekly-update/index.html | 22 ++++++++++--------- public/index.html | 4 ++-- public/sitemap.xml | 6 ++--- .../_posts/2014-10-04-weekly-update.markdown | 21 ++++++++++-------- 5 files changed, 41 insertions(+), 34 deletions(-) diff --git a/public/atom.xml b/public/atom.xml index 120bf218..0131dcdf 100644 --- a/public/atom.xml +++ b/public/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Matthias Nehlsen]]> - 2014-10-04T18:53:13+02:00 + 2014-10-05T19:10:44+02:00 http://matthiasnehlsen.com/ @@ -18,26 +18,28 @@ 2014-10-04T19:06:00+02:00 http://matthiasnehlsen.com/blog/2014/10/04/weekly-update - 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.

-

Test environment for my 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.

-

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.

+

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.

-

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:

+

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:

-

http://staging.matthiasnehlsen.com/blog/2014/10/01/Building-System-in-Clojure-2/

+

http://staging.matthiasnehlsen.com/

-

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.

+

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.

-

Closing remarks

+

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.

-

Most importantly, check out the new article series 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 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.

+

Conclusion

-

Until next week, +

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

]]> diff --git a/public/blog/2014/10/04/weekly-update/index.html b/public/blog/2014/10/04/weekly-update/index.html index 6bbba665..61aaf912 100644 --- a/public/blog/2014/10/04/weekly-update/index.html +++ b/public/blog/2014/10/04/weekly-update/index.html @@ -9,7 +9,7 @@ - + @@ -91,26 +91,28 @@

Weekly Update: Staging server for this blog

-

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.

-

Test environment for my 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.

-

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.

+

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.

-

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:

+

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:

-

http://staging.matthiasnehlsen.com/blog/2014/10/01/Building-System-in-Clojure-2/

+

http://staging.matthiasnehlsen.com/

-

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.

+

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.

-

Closing remarks

+

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.

-

Most importantly, check out the new article series 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 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.

+

Conclusion

-

Until next week, +

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

diff --git a/public/index.html b/public/index.html index 82ba4923..23040d9b 100644 --- a/public/index.html +++ b/public/index.html @@ -9,7 +9,7 @@ - + @@ -94,7 +94,7 @@

Weekly Update: -

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.

diff --git a/public/sitemap.xml b/public/sitemap.xml index a0aa6809..c1964f84 100644 --- a/public/sitemap.xml +++ b/public/sitemap.xml @@ -162,7 +162,7 @@ http://matthiasnehlsen.com/blog/2014/10/04/weekly-update/ - 2014-10-05T18:45:02+02:00 + 2014-10-05T19:10:11+02:00 http://matthiasnehlsen.com/about/ @@ -170,11 +170,11 @@ http://matthiasnehlsen.com/blog/archives/ - 2014-10-05T18:45:02+02:00 + 2014-10-05T19:10:11+02:00 http://matthiasnehlsen.com/ - 2014-10-05T18:45:02+02:00 + 2014-10-05T19:10:11+02:00 http://matthiasnehlsen.com/reading-lists/ diff --git a/source/_posts/2014-10-04-weekly-update.markdown b/source/_posts/2014-10-04-weekly-update.markdown index ce5802fa..1ad5f237 100644 --- a/source/_posts/2014-10-04-weekly-update.markdown +++ b/source/_posts/2014-10-04-weekly-update.markdown @@ -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. -## 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 \ No newline at end of file