archive/c0de.dev-blog
1
0
Fork 0
mirror of https://github.com/c0de-archive/c0de.dev-blog.git synced 2024-12-22 08:52:39 +00:00
Code Issues Projects Releases Wiki Activity

Add instructions for posting

Browse Source
This commit is contained in:
David Todd 2019-05-27 17:09:45 -05:00
parent 73cc0f9ff3
commit f7d892e7ce
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
readme.md
View File

@ -18,6 +18,22 @@ There's not really a whole lot here, but it contains all the configuration files
1. `cd c0de.dev-blog` 1. `cd c0de.dev-blog`
1. `make update` 1. `make update`
## Making new posts
For seperation, I store the content in a private repo (can't read my drafts and encrypted blogs without the password). Also as a matter of choice, I'm using [Markdown](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) as markup language.
Categories are defined per folder in the [c0de.dev-content](https://github.com/alopexc0de/c0de.dev-content) repository. To create a new category, simply create a new folder in that repo with at least one post within. For posts without a category, simply throw the new posts in the root of the repo.
When a new post has been created (with the appropiate [metadata](https://docs.getpelican.com/en/3.6.3/content.html#file-metadata)), the steps to generate the output is as follows:
1. SSH into your server
1. `cd c0de.dev-blog`
1. Update all submodules (installs new plugins too) - `make update`
1. `cd pelican`
1. Clear the output cache if themes or globals changed - `make clean`
1. Generate the new static HTML site - `make html`
## TODO ## TODO
* Service/Unit to run this in a server on prod * Service/Unit to run this in a server on prod