2 --- description: Blog is a command-line tool to author and manage a semi-ephemeralâ„¢ blog with a gemini archive.
5 Command line tool to author and manage a semi-ephemeralâ„¢ blog with a gemini archive.
7 => https://git.r.bdr.sh/rbdr/blog view source @ git.r.bdr.sh
8 => https://git.sr.ht/~rbdr/blog source mirror @ sourcehut
12 At the moment only installation from source is available. Clone this repository and run:
18 This will add the `blog` command to your shell.
24 Create a `.gmi` gemini file.
26 You can add this to the blog using the following command:
28 blog --add path/to/blog_post.gmi
31 This it will shift all posts and remove the oldest one if the limit of posts is reached (defualts to 3). This will also regenerate the static files.
33 ### Updating the Latest post
35 If you need to make corrections to the latest post, use:
38 blog --update path/to/blog_post.gmi
41 This will replace the latest with the contents of the `path` without shifting the existing entries. It will also regenerate files.
43 ### Regenerate Static files.
45 Adding and updating posts regenerates the blog and archive, but you can always regenerate manually (eg. if you updated your static assets or templates):
51 ## Usage II: Publishing
53 Publishing the blog and archive requires `rsync`.
55 ### Publishing the Blog
57 You can publish to any valid `rsync` target (eg. ruben@coolserver.local:blog)
60 blog --publish <remote_server>
63 This publishes the static files, including the html index, rss feed and plaintext version of the ephemeral blog.
65 ### Publishing the Archive
67 You can also publish the archive of posts as a gemlog by passing a valid rsync target
70 blog --publish-archive <remote_server>
73 This will include *all the posts* in gemtext format.
75 ## Usage III: Source Control
77 Blog supports saving snapshots of the blog in git, and you can add and remove remotes with the following commands:
80 blog --add-remote <git_url>
84 If a remote is present, it will be pulled before adding or updating, and pushed after it finishes. You can manually trigger this by calling
91 The blog will always sync down before adding to avoid going out of sync.
93 **IF YOU CHANGE ANY FILES MANUALLY, REMEMBER TO SYNC UP, OTHERWISE YOUR CHANGES WILL BE LOST**
95 ## Usage IV: Customizing
97 The default templates included in blog are very generic and likely not helpful for your use case. However, you can customize this freely:
99 ### Using Custom Templates
101 You can override the default templates by creating a `templates` directory inside your blog data root (`$XDG_DATA_HOME/blog`).
103 For the ephemeral blog you can create `feed.xml`, `index.html`, and `index.txt` inside of `templates`. These files are then parsed with [dot][dot] and passed the following variables:
106 it.posts <Array<Post>>
109 +id <String> // The numerical timestamp when the blog post was added.
110 +createdOn <String> // The UTC String of post creation date. (only feed.xml)
111 +title <String> // The title of the post. (only feed.xml)
112 +raw <String> // The raw gemini text of the template.
113 +html <String> // The parsed html generated from the gemini.
116 To customize your gemini archive you can provide an `index.gmi` file that will be used as a template for the archive. However the data structure is different, as it's just the gemini URL strings:
119 it.posts <Array<String>>
122 ### Using Static Files
124 Any files inside the `static` directory of your blog data root (`$XDG_DATA_HOME/blog`) will be copied as is. This is useful for any images, javascript files or stylesheets that you use in your posts or templates.
126 ## Usage V: Where is Data Stored?
128 Blog uses three diretories to store data, all of them using the XDG User
131 => https://wiki.archlinux.org/title/XDG_user_directories XDG User Directories.
133 - Configuration is stored in $XDG_CONFIG_HOME/blog
134 - Data such as the raw blog, templates, and static files are stored in $XDG_DATA_HOME/blog
135 - Generated "ready to upload" files are stored in $XDG_CACHE_HOME/blog
137 All of these can be overridden by environment variables.
139 ## Usage VI: Configuration
141 You can control the number of posts in the ephemeral blog, and the location of
142 all the data by using environment variables.
144 ### Overriding Number of Posts
146 Updating the `BLOG_MAX_POSTS` environment variable sets the number of posts
149 ### Overriding Configuration Directory
151 You can set the `BLOG_CONFIG_DIRECTORY` to any directory you want. This
152 defaults to `$XDG_CONFIG_HOME/blog/` and is used to store the blog remote
155 ### Overriding Data Directory
157 Setting `BLOG_DATA_DIRECTORY` will update where the posts, archive, static
158 files, and templates are saved. The default is the `$XDG_DATA_HOME/blog`.
160 ### Overriding the location of generated files.
162 Setting `BLOG_OUTPUT_DIRECTORY` will update where generated files are placed.
164 The default is `$XDG_CACHE_HOME/blog`.
168 * 6.0.0 Use custom templates, use XDG directories.
169 * 5.0.2 Internal template changes
170 * 5.0.1 Dependency update
171 * 5.0.0 Publish using rsync instead of s3
172 * 4.0.0 Add gemini archive
173 * 3.0.0 Add support for RSS and TXT
174 * 2.0.0 Add support for S3 publishing
175 * 1.0.1 Bugs and dependency fixes
176 * 1.0.0 Initial release