* Home now renders from content instead of all in-template * Titles are parsed from HTML :D * Updated stylesheet to have better fonts and scale better (e.g. add margin) * Any content path with '_hidden' is ignored * Added link to home page to all Blog Posts * XSRF tokens are randomized for eventual security
|3 years ago|
|content||3 years ago|
|renderedContent||3 years ago|
|templates||3 years ago|
|webResources||3 years ago|
|.gitignore||3 years ago|
|ContentConverter.py||3 years ago|
|Generate_Certificates.sh||3 years ago|
|LICENSE||3 years ago|
|ReadMe.org||3 years ago|
|SimpleBlogServer.py||3 years ago|
|WordPressXmlToOrgMode.py||3 years ago|
- Simple Org Blog
Simple Org Blog
This project is meant to be a quick-and-dirty blog based on org-mode formatted documents.
You can put your
.org files in
content/ and it will be rendered into
renderedContent within fifteen minutes, or immediately after starting the server.
This project requires Python 3.
pip3 install tornado
2. Install pandoc
sudo apt install pandoc
This will be used to convert
.org files into
3. Generate SSL keys
openssl req -x509 -nodes -days 365 -newkey rsa:1024 -keyout certificates/server_jupyter_based.crt.key -out certificates/server_jupyter_based.crt.pem
4. Run the server
5. Trust the certificate
Open your browser and visit
Your web browser should complain that the website's owner cannot be verified. This is a security measure for SSL related to the certificate. Because we made the certificate ourselves, the browser doesn't know whether to trust the certificate, because there is no signing authority.
You can safely click
Advanced and add the certificate as trustworthy, because you've signed the certificate and trust yourself :).
If you want to get rid of this, you'll need to get a signing authority like
LetsEncrypt to generate your certificate.