archive/c0de.dev-blog
1
0
Fork 0
mirror of https://github.com/c0de-archive/c0de.dev-blog.git synced 2024-10-31 23:07:47 +00:00
Code Issues Projects Releases Wiki Activity
Holds the pelican configuration and content for the c0de.dev blog
41 Commits 4 Branches 0 Tags 56 KiB
Python 55.3%
Makefile 44.7%
785e906c0c
Go to file
dependabot[bot] 785e906c0c
Merge aa6ead2430 into da8dd8fcf8
2021-03-29 19:35:50 +00:00
pelican pull down latest blog 2019-05-28 21:15:11 -05:00
.editorconfig Initial Commit 2019-05-27 00:44:18 -05:00
.gitignore update gitignore 2019-05-27 01:36:58 -05:00
.gitmodules add upstream pelican plugins 2019-05-27 22:16:16 -05:00
license Initial Commit 2019-05-27 00:44:18 -05:00
Makefile remove some vars from makefile 2019-05-27 17:15:08 -05:00
readme.md Add instructions for posting 2019-05-27 17:09:45 -05:00
requirements.txt Bump pygments from 2.4.1 to 2.7.4 2021-03-29 19:35:48 +00:00

readme.md

c0de.dev Blog

This is a Pelican based blog that powers c0de.dev. There's not really a whole lot here, but it contains all the configuration files and plugins/themes.

Installation

  1. SSH into your server
  2. Clone the repo - git clone --recurse-submodules https://github.com/alopexc0de/c0de.dev-blog
  3. cd c0de.dev-blog
  4. Install the config and plugins - make install

Updating

  1. SSH into your server
  2. cd c0de.dev-blog
  3. 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 as markup language.

Categories are defined per folder in the 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), the steps to generate the output is as follows:

  1. SSH into your server
  2. cd c0de.dev-blog
  3. Update all submodules (installs new plugins too) - make update
  4. cd pelican
  5. Clear the output cache if themes or globals changed - make clean
  6. Generate the new static HTML site - make html

TODO

  • Service/Unit to run this in a server on prod
  • Git hooks to automatically fetch content
  • NginX config