# Logarion - static website generation

**URL:** <https://discuss.ocaml.org/t/logarion-static-website-generation/1297>\
**Category:** Community\
**Tags:** logarion\
**Created:** [December 17, 2017, 12:21pm UTC](https://discuss.ocaml.org/t/logarion-static-website-generation/1297 "2017-12-17T12:21:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon72795300](https://avatars.discourse-cdn.com/v4/letter/a/8e7dd6/32.png) [@anon72795300](https://discuss.ocaml.org/u/anon72795300)\
**Post date:** [December 17, 2017, 12:21pm UTC](https://discuss.ocaml.org/t/logarion-static-website-generation/1297/1 "2017-12-17T12:21:03Z")

</div>

Logarion v0.3 release candidate adds static website generation from archive.

[https://gitlab.com/orbifx/logarion/tags/v0.3rc](https://gitlab.com/orbifx/logarion/tags/v0.3rc)

Far from polished, it should be usable now. I’ll go through a phase of documentation, hoping to get some feedback meanwhile.

Generate static website from a Logarion archive:

```
logarion_cli convert "html"

```

Where `html` is the folder to save the HTML files and static directory.

Important changes:

- Templates should not contain HTML code in preparation for more conversion formats
- Started relativizing links for portability of static pages

---

<div class="post-metadata">

**Author:** ![techate](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/techate/32/671_2.png) [@techate](https://discuss.ocaml.org/u/techate)\
**Post date:** [December 17, 2017, 2:43pm UTC](https://discuss.ocaml.org/t/logarion-static-website-generation/1297/2 "2017-12-17T14:43:04Z")

</div>

Stylish. You have a potential customer that you don’t seem to be aware of though: shared-hosting and VPS customers who are sensitive to resource costs. People on shared hosting can get their sites suspended due to excessively CPU-costing designs or if an attack (on a search box for example, but more often it’s a brute force attempt or an obvious DOS) caused the site to use an extreme amount of resources. People on VPSes face the same hazards but experience them differently.

A typical WordPress site without a caching module, which is very popular to have off of ‘[wordpress.com](http://wordpress.com)’ btw, can be taken down with the resources of a single attacker making requests to the site’s front page. A static site though on the same hosting architecture would need so many more requests to affect anything that you may as well drop the layer-8 attack and try a UDP flood.

Also, a typical _unattended_ dynamic website, anything with comments, but also notably wikis, will quickly be filled with spam.

There are people who want to have a website but don’t want to have to pay web2.0’s hidden administrative costs. Logarion could be more useful to these people with self-limiting dynamic features (oops, I’ve used too much CPU time, so I’m disabled; hmm, after this last comment I notice that the owner hasn’t been around recently, so I’m going to put up a notice and stop accepting comments) and with locked-down dynamic features, like an administrative panel that requires HTTP Auth (lower-cost and also not accounted as the user’s CPU usage) before you can see the actual login page.