Anton using PagePark?

[scripting]

I got a note that my friend Anton is using PagePark. I wanted to open a thread here in case he has any questions. I prefer using GitHub over mail lists these days. ;-)

[mistersugar]

Thanks, Dave. I will be attempting to install PagePark on my Webfaction hosted server in the next day or two. Webfaction requires a few extra steps, but I think this should be similar to how I prepared to install 1999 (i.e. node.js application with a dedicated port). I will report back soon.

[mistersugar]

I finally took some time, followed the instructions, and got PagePark installed on my webhost, WebFaction, under the domain stor.im.

I've also added another domain in the domains folder, thelongtable.org, but need to figure out the correct cname destination (to stor.im?) or A record (to the IP address?) and how WebFaction will handle that.

[eli-oat]

@mistersugar I'm really interested to see if you are able to make this work. I also host a couple websites on Webfaction, but haven't worked out how to add other domains to the folder.

[scripting]

Interesting. I'm not familiar with Webfaction, but I went to their website and see that it's basically a hosting service, and they have free trials, so I'll try to make some time to set up a server there and see what I can learn.

Generally speaking, the host doesn't know what you map to the IP address they supply you with. So anything mapped to the server's IP address will show up as a request for PagePark running on that server (assuming it's on port 80, the standard port for the web).But that's just a general statement, it's possible that WebFaction does something else?

Keep posting questions as issues here. This is a good place to gather knowledge. ;-)

On Sat, Sep 9, 2017 at 8:01 PM, Eli Mellen [email protected] wrote:

@mistersugar https://github.com/mistersugar I'm really interested to see if you are able to make this work. I also host a couple websites on Webfaction, but haven't worked out how to add other domains to the folder.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/scripting/pagePark/issues/4#issuecomment-328310750, or mute the thread https://github.com/notifications/unsubscribe-auth/ABm9OxQE9SECluBQqTUP912V5IK77yL5ks5sgybFgaJpZM4OgNG0 .

[mistersugar]

Got it to work.

Here's what I did.

Previously, I had created a folder for thelongtable.org under my PagePark folder stor.im, and I put an index.md file (modified from one of Dave's examples) in there.

Then, in Webfaction:

1. Added thelongtable.org as a domain.
2. Created a new website reusing the PagePark app (previously set up as a Node.js application with open port, using the open port IP) and the domain thelongtable.org.
3. In my domain registrar, created an A record pointing thelongtable.org to the open port IP.

I waited a 15 seconds, and voila, I see what I expected at thelongtable.org.

I was hoping I wouldn't have to take steps 1 and 2, and that Webfaction would just let PagePark listen for domains, but I guess it makes sense for me to do this.

I'll add a new domain tonight to see if I can replicate this success.

[scripting]

I'm not sure I understand, but it sounds like you're running a new copy of pagepark for every domain? If so, that's not really using pagepark.

On Monday, September 11, 2017, Anton Zuiker [email protected] wrote:

Got it to work.

Here's what I did.

Previously, I had created a folder for thelongtable.org under my PagePark folder stor.im, and I put an index.md file (modified from one of Dave's examples) in there.

Then, in Webfaction:

1. Added thelongtable.org as a domain.
2. Created a new website reusing the PagePark app (previously set up as a Node.js application with open port, using the open port IP) and the domain thelongtable.org.
3. In my domain registrar, created an A record pointing thelongtable.org to the open port IP.

I waited a 15 seconds, and voila, I see what I expected at thelongtable.org.

I was hoping I wouldn't have to take steps 1 and 2, and that Webfaction would just let PagePark listen for domains, but I guess it makes sense for me to do this.

I'll add a new domain tonight to see if I can replicate this success.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/scripting/pagePark/issues/4#issuecomment-328690312, or mute the thread https://github.com/notifications/unsubscribe-auth/ABm9O4dGx87-j2DFbRnITDpjmsEbd9n8ks5shccggaJpZM4OgNG0 .

-- Typed on an iPad with fat fingers.

[mistersugar]

Just one copy of pagepark, but telling Webfaction how to funnel traffic into pagepark. I think it's working right. Give me a day to add a few more domains and try some things, and I'll report back.

[mistersugar]

I had forgotten that we'd documented my prior use of PagePark here, but am glad we did. I've since moved to OpalStack (company created by former Webfaction employees). I'm happy to say that setting up and using PagePark was a similar process. I have the following working examples:

• park.zuiker.com
• northernohio.live

Steps I took in OpalStack:

1. On the Applications tab, click 'Create Application' and select Proxied Port, give the application a name, select type Node.js, select the user, and click Create Application. Once the app is created, note the port assigned to the app. Follow the PagePark installation instructions.
2. Set DNS (in the domain registrar or in OpalStack if using OpalStack name records) for an A record to point to the IP address assigned to my OpalStack shared hosting server.
3. On the Domains tab, click 'Add Your Domain' and enter the domain.
4. On the Domains tab, click 'Add Site' and fill in the relevant details, then click 'Route Domain' and select the domain just added, then click 'Route Application' and select the PagePark application from step 1.
5. In Transmit (or other sftp or shell client), edit the config.json file to update the port, then add a folder for the domain in the domains folder and add an index.md or other file.
6. In a browser, go to the domain and see if you were successful.

Note to Anton: leave a comment somewhere else for Dave to note the PagePark instructions refer to a prefs.json file but I believe the correct settings file is now the config.json file.

[gwthompson]

I've come across an issue setting up PagePark to use the mirrors section of config.json in my garywthompson.net subfolder of the domains folder. When I set up the section like this:

{ "mirrors": { "/": "http://storage2.littleoutliner.com/users/gwthompson/myOutlines/blog.opml" } }

I just get plain text rendered when pointing to http://garywthompson.net. I have a blog.opml file in the folder that is empty and I have also tried without the blog.opml file. Neither setup renders the opml correctly.

If I change the mirrors section like this:

{ "mirrors": { "/blog.opml": "http://storage2.littleoutliner.com/users/gwthompson/myOutlines/blog.opml" } }

and point to http://garywthompson.net/blog.opml it renders the opml correctly.

This seems to indicate the default handler may not be recognizing the opml extension in the remote file correctly and thus doesn't load the opml parser but that's a guess. I'm just starting to look at pagepark.js to see if I can figure out what's going on.

[mistersugar]

@gwthompson is that the same issue reported by @andrewshell in #21 ?

[scripting]

What version of pagepark are you running?

[gwthompson]

I am running version 0.8.20 of pagepark and yes it does appear to be the same problem as #21.

[scripting]

It sounds like you found a workaround?

[gwthompson]

Not yet.

[mistersugar]

I also successfully updated PagePark to 0.8.20 (Dave please consider adding instructions for updating PagePark for other poets).

I have tested the mirrors feature to serve an opml file from LittleOutliner hosted on my own 1999 server. See St Croix. I love this - thanks Dave for the tools and the ability to own my own data.

[scripting]

What are the instructions for updating PP?

Isn't it just a matter of copying pagepark.js into your folder?

Is that what you did?

[scripting]

Also where did you look for upgrade instructions?

[mistersugar]

I looked for upgrade instructions at http://pagepark.io hoping for a 7. or note in the How to section after the "If this worked, congratulations ..." line.

Here's how I upgraded to the latest version:

• I downloaded the zip file from the Code button on https://github.com/scripting/pagePark
• I connected to my web host with an sftp client (Transmit) and navigated to the folder associated with PagePark.
• I connected to the terminal and stopped PagePark running.
• In the sftp client, I copied over the new PagePark files from the folder in the downloads folder on my laptop, replacing the old files on the server.
• In the terminal, I ran npm install, and then restarted pagepark.js using Forever.
• In the browser, I went to park.zuiker.com/version to check the version number.

That seemed to have worked for me. I think I did it this way because that's how I've learned to update 1999.

[scripting]

If you're interested in leading -- there's a wiki here, you can post your notes and ask for feedback.

I would be happy to post a link to it on scripting.com and push it out through my linkblog.

You really are the best person to help people get started. ;-)

[scripting]

@gwthompson, @mistersugar -- FYI

https://github.com/scripting/pagePark/issues/21#issuecomment-886229200