How-To Fargo Self-Hosted Publishing

[Christian Dadswell]

Hello all,

I just wrote a piece on my blog about my experiences setting up a self hosted Fargo blog.

How-To Fargo Self-Hosted Publishing

Feel free to tear into it and let me know what you think good or bad. I'm all for continous improvement ;-)

Thanks to everyone on this forum for the posts I have poured over to get everything I needed to be able to do this. It's been a fun journey!

[Dave Winer]

Wow!

--
You received this message because you are subscribed to the Google Groups "smallpicture-web" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smallpicture-w...@googlegroups.com.
To post to this group, send email to smallpic...@googlegroups.com.
Visit this group at http://groups.google.com/group/smallpicture-web.
For more options, visit https://groups.google.com/d/optout.

[Dave Winer]

Christian, re the unresolved issues, I think we can resolve it now. 

I don't think this is going to change, nor should it and I should document how it works, if you don't mind testing it first.

1. There's a new environment variable fpRedirect, whose value is true or false.

2. Set it to false.

export fpRedirect =false

3. Be sure fpDomain is set to the domain you want to host, suppose it's hello.com.

4. In DNS make sure *.hello.com points to your Node.js server.

That's all you should have to do.

Let me know how it goes.

Dave

[Christian Dadswell]

Hi Dave,

Thanks for the quick response.

I suspected that was all I needed to do, but currently I have a Wordpress blog running out of my root domain. I was planning to export posts to Fargo and close it down once I got self hosting working. Seeing as I'm virtually there now, it's a good time to finish the job.

I'll have a crack at the suggestion later today and feed back.

Whilst I'm here can I ask whether it's possible to markup code segments in a post so that they appear different to the rest of the content? I can do something similar in Wordpress, but not sure how to achieve this in Fargo at the moment.

As an example, this is a post on my Wordpress blog.

http://www.chrisdadswell.co.uk/android-coding-example-authenticating-clientlogin-google-reader-api/

All the best and thanks again.

Christian.

On Friday, 20 June 2014 00:43:26 UTC+1, Dave Winer wrote:

Christian, re the unresolved issues, I think we can resolve it now. 

I don't think this is going to change, nor should it and I should document how it works, if you don't mind testing it first.

1. There's a new environment variable fpRedirect, whose value is true or false.

2. Set it to false.

export fpRedirect =false

3. Be sure fpDomain is set to the domain you want to host, suppose it's hello.com.

4. In DNS make sure *.hello.com points to your Node.js server.

That's all you should have to do.

Let me know how it goes.

Dave

On Thu, Jun 19, 2014 at 5:13 PM, Dave Winer <da...@smallpicture.com> wrote:

Wow!

On Thursday, June 19, 2014, Christian Dadswell <chrisd...@gmail.com> wrote:

Hello all,

I just wrote a piece on my blog about my experiences setting up a self hosted Fargo blog.

How-To Fargo Self-Hosted Publishing

Feel free to tear into it and let me know what you think good or bad. I'm all for continous improvement ;-)

Thanks to everyone on this forum for the posts I have poured over to get everything I needed to be able to do this. It's been a fun journey!

--
You received this message because you are subscribed to the Google Groups "smallpicture-web" group.

To unsubscribe from this group and stop receiving emails from it, send an email to smallpicture-web+unsubscribe@googlegroups.com.
To post to this group, send email to smallpicture-web@googlegroups.com.

[Johannes Kleske]

Dave,

I set up my own noteblog at http://noteblog.jkleske.me/ a couple of weeks ago and your points listed here are exactly what made the whole thing work for me back then. 

The only thing not working for me yet is the rendering of the date in the headlines. I seem to have the same problem as others living in Europe. 

Best,

Johannes

--

Website: http://jkleske.com, Company: http://thirdwaveberlin.com

Public PGP key: http://thirdwaveberlin.com/johannes.asc

InstantMessaging (OTR): jkl...@jabber.de

[Dave Winer]

I thought we fixed that in Fargo 1.58.

http://fargo.io/blog/2014/05/15/fargo158.html

There was an extensive discussion of the problem on the Fargo2 mail list.

Dave

[Christian Dadswell]

Good day Dave,

I've started having a look at this and am running into some issues.

I configure my DNS via CloudFlare.

• I've changed my *.chrisdadswell.co.uk to point at the node server IP
• chrisdadswell.co.uk. 300 IN A 162.244.24.69
  
• The pub runs on pub.chrisdadswell.co.uk
• pub.chrisdadswell.co.uk. 300 IN A 162.244.24.69
  
• The S3 bucket
• scriven.chrisdadswell.co.uk. 300 IN CNAME scriven.chrisdadswell.co.uk.s3-website-us-east-1.amazonaws.com.
  

When I browse to http://scriven.chrisdadswell.co.uk I get an S3 error telling me there is no /index.html. Which is correct. The only files in the root of the S3 bucket are directories, users and data.

I was wondering, does the fargoPublisher have to run on port 80 to be able to perform the redirect? Currently my pub is running on 8080. And of course when I hit scriven.chrisdadswell.co.uk I'm hitting it on port 80.

I probably have the wrong end of the stick, but just wanted to clarify this either way.

Interestingly, when I try and run the pub on port 80 on my server I get an error;

events.js:72

        throw er; // Unhandled 'error' event

              ^

Error: listen EACCES

    at errnoException (net.js:904:11)

    at Server._listen2 (net.js:1023:19)

    at listen (net.js:1064:10)

    at Server.listen (net.js:1138:5)

    at Object.<anonymous> (/home/scriven/fargo/publisher.js:801:5)

    at Module._compile (module.js:456:26)

    at Object.Module._extensions..js (module.js:474:10)

    at Module.load (module.js:356:32)

    at Function.Module._load (module.js:312:12)

    at Function.Module.runMain (module.js:497:10)

The error seems to suggest something is already on port 80. So looking into that with ss,netstat and lsof I couldn't find a single thing running on that port. A bit odd, but I'll keep looking.

For now I have put an index.html in the root of my S3 bucket that does a http-equiv="refresh" to scriven.chrisdadswell.co.uk/users/scriven just so users hitting scriven.chrisdadswell.co.uk will get redirected.

I'm beginning to wonder whether I need to use Amazon Route 53 for my DNS management. Do you use Route 53?

In any case I'd really like to get this working correctly, so any help gratefully received.

All the best,

Christian.

[Johannes Kleske]

I looked through all the discussions but non of the approaches fixed it for me. 

I'm using Fargo 1.61 and FargoPublisher 0.96 on Heroku. My #siteTimeZone is set to "+2" and my computer runs at Central Euroean Time. 

– Best, JK

[Christian Dadswell]

Just added a new section, Technical Overview to the How-To: Fargo Self-Hosted Publishing post from last week. It is a diagram I created over at draw.io to show how I perceive it hangs together. 

There may be some errors or omissions.

I welcome any comments on this group.

[Christian Dadswell]

Just worked out why I couldn't run the fargoPublisher on port 80...

http://scriven.chrisdadswell.co.uk/users/scriven/2014/06/30/index.html

[Dave Winer]

You don't have to run it on port 80.

That's why the fpServerPort configuration variable is there. 

https://github.com/scripting/fargoPublisher#before-deploy

Or maybe this isn't the problem? 

Dave

To unsubscribe from this group and stop receiving emails from it, send an email to smallpicture-w...@googlegroups.com.
To post to this group, send email to smallpic...@googlegroups.com.

[Christian Dadswell]

Hi Dave,

Thanks for the response.

I understand that the fp can run on any port. I was just going a bit mad as to why I couldn't run it on port 80. 

It soon became obvious that running the fp as a normal user (as per my How-To) on ports below 1024 would cause an issue. It was a bit of a face plant moment and I should known better.

My main, and still ongoing issue, is that I cannot get my blog to work on a subdomain correctly. i.e, scriven.chrisdadswell.co.uk. If I go to that address I get;

404 Not Found

• Code: NoSuchKey
• Message: The specified key does not exist.
• Key: index.html
• RequestId: A7DD0B046D35476A
• HostId: IUU6ti1jmb01oo6eXBJb2SvMIhWoW+jK0gRrxfH2OeGoIEhetqMmqNGUiGRmkTtS

I have to go to http://scriven.chrisdadswell.co.uk/users/scriven/ to get the blog for this user.

I own this domain and I have pointed the A record for chrisdadswell.co.uk at the IP of the node and it still doesn't work.

I guess I just don't understand how the fp is doing the redirect. 

Cheers,

Chris.

[Frank McPherson]

I have also set up my own fargoPublisher server, following Chris' instructions and using the same services. I am now stuck at the same point as Chris was.

What's happening: 

1. My fargoPublisher is at frankmcpherson.net. 

2. My content is being published to blog.frankmcpherson.org/users/sports/ (outline name is sports)

3. The Home and Eye icons point to sports.frankmcpherson.net, clicking them results in a page not found.

4. All of the navigation link icons automatically created by Fargo, for example in the bread crumbs at the top of each article page is using sports.frankmcpherson.net and therefore clicking them results in page not found.

What should happen:

Either:

A. The Home, Eye icons in Fargo AND the navigation links on Fargo article pages point to blog.frankmcpherson.org/users/sports

OR

B. sports.frankmcpherson.net redirects to blog.frankmcpherson.org/users/sports

I prefer that the direct works for my site as it does with the smallpict.com sites.  

As an aside changing the URL filed in the CMS tab of the Outline Settings to blog.frankmcpherson.org results in the content not being published. For some reasons I have to keep it to sports.frankmcpherson.net in order for new content to publish.

[Frank McPherson]

I have written up some notes/thoughts about this here: http://frank-notes.smallpict.com/2014/07/15/namingOutlinesAndSites.html 

An idea... if it where possible to enter a #fpHostingPath directive an an outline that told fargoPublisher where to publish content for that specific outline, I could then create S3 buckets that are CNAMEs of fpDomain to host the content and it would support the URLs that Fargo seems to be expecting for Fargo blogs.

[Frank McPherson]

Ok, I got through the redirect issue by moving Fargo Publisher on port 80. Now for some reason Fargo is not talking with my FargoPublisher and I can't get publisher to respond with the version. One step forward two steps back.

[Frank McPherson]

And now it's all working. I'll write this up a blog post, the final piece of the puzzle was to create a CNAME on a different domain (the one I use for my S3 bucket) and point it to my Fargo Publisher domain. After I did that, /version and /status responded. 

I added the CNAME to the Fargo Settings, CMS tab for my publishing server, and after saving, waiting a few minutes, and then completely getting out of Fargo, I was able to publish content. 

Now to migrate all my content over. I need to understand outline names, they are a key part of the puzzle. I will post some questions over to the fargo2 group for that.