A wiki is NOT a dynamic website, it has NO dynamic content strictly
speaking : the content only has to be generated upon updating and not
with every GET request.
Also, I don't really see what Javascript has to do with all this.
An ikiwiki setup has a very small memory footprint, and nginx doesn't
consume more. Same goes for CPU. And ikiwiki is based on git, which
allows for a decentralized architecture, and very efficient versionning.
What I'm saying here is that relying on 3rd parties solutions while a
very cheap (or even free) VPS would be sufficient is asking for
unnecessary trouble.
On 10/18/2012 03:18 PM, Andrew Pennebaker wrote:
GitHub <https://github.com/> offers free hosting for code and web
pages. The way it works is any code that happens to be HTML is
available as if it were a traditional, hosted website. If we want a
fairly flat website for documentation, no wiki or server running, this
would be a convenient solution.
If, on the other hand, we want a website that serves dynamic content,
like a wiki, we could setup a Node.js server on the free Joyent
<http://joyent.com/> cloud.
--
Cheers,
Andrew Pennebaker
www.yellosoft.us <http://www.yellosoft.us>
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
