Host a static Jekyll website

[benhylau]

Recipe that configures:

• Jekyll website
• commit webhook and nightly
• nginx
• letsencrypt
• cjdns and serving website over its IPv6

Basically, automate: https://github.com/tomeshnet/documents/blob/master/service_setup/website.md (no cjdns service yet, but current tomesh.net has the first 4 items)

[darkdrgn2k]

IPFS site upload from existing running site.

 wget \
     --recursive \
     --no-clobber \
     --page-requisites \
     --html-extension \
     --convert-links \
     --restrict-file-names=windows \
     --domains tomesh.net \
     --no-parent \
tomesh.net
cd tomesh.net
ipfs add -r .

[benhylau]

How I would do this:

1. Translate the website.md into a Dockerfile @chrisbarless
2. Add cjdns and nginx the website over cjdns ipv6 @benhylau
3. Add ipfs and republish website on ipfs on webhook @darkdrgn2k

[benhylau]

Also DAT: https://github.com/new-computers/seeder So we can host a website like that: https://decentralizedweb.net (scroll to very bottom)

[benhylau]

@chrisbarless not sure if you caught my msg on the chat. I think we can commit the Dockerfiles in this repository for now. Each Dockerfile in its own a folder like this: https://github.com/vanmesh/p2p-apps-dockers

The name of this repo may be misleading, feel free to propose renaming in a GitHub Issue. Your thoughts?

Clarification: The vanmesh/p2p-apps-dockers is where we put Dockerfiles intended to run on the armhf SBCs. This one is to run services on servers, and one Docker container would run multiple applications needed to serve a purpose such as a website over multiple content networks.

[chrisbarless]

Sounds good to me. @darkdrgn2k your instincts were correct!

So this is the repo we are supposed to use? This name is fine for now, it's descriptive enough.

[chrisbarless]

I'm going to hack on this when I have some time today and we can regroup on it when we meet up tomorrow @benhylau