Publishing my Emacs Configuration using Gitea Actions
About a year ago I already wrote a few blog posts about publishing my Emacs configuration, lastly using a GitLab pipeline. This worked quite fine since back then and I had zero problems or issues with the pipeline. Although I’m using the GitLab CI feature for this I don’t use GitLab for hosting the repository. My dot-emacs-repository over there is just a mirror, the main one is in my personal Gitea instance.
„Mirroring“ my open-source Git repos to my Gitea instance
Updates: Update 2021-03-25: Git hooks feature disabled by default Update 2021-08-23: Built-in mirror feature tl;dr: GitLab will still be my primary Git platform for my public projects/repositories, but these repositories can now also viewed at my Gitea instance at git.mmk2410.org. Additional links appearing to my Gitea instance You may have noticed that I added a link to a Gitea instance on some places next to a link to my GitLab account.
Quick Deploy Solution
Quick Deploy - a possibly hacky way to deploy a Git repository without much overload and fast setup. Motivation From time to time I work on some TYPO3 Site Packages (mostly design work) where seeing the changes is quite important to me. Since TYPO3 needs a web server and a Database server running (well yes, it can be set up locally, but I had some database errors last time I tried).
Moving the open-source stuff from phab.mmmk2410 to GitLab
The journey started in early 2016 when I decided to move my open-source projects and their management away from GitHub. First I launched a cgit instance for viewing the code and set up a gitolite for repository hosting. After a short time I moved the repositories to a self-hosted Phabricator instance at phab.mmk2410.org, because with that platform I had the possibilities for project management like issues or workboards. But this concept also didn’t last for long.
Rangitaki Version 1.5.0
I’m proud to announce a new release of the Rangitaki blogging engine which introduces post excerpts. Post excerpts are disabled by default and can be enabled with (re-)running php bin/init.php. Many thanks to Stefan for fixing the OpenGraph and Twitter meta tags. Full Changelog Update script
Rangitaki Version 1.4.4
Today I announce 1.4.4 of the Rangitaki blogging engine. It brings an important bug fix concerning the feed creation. Starting from 1.4.0 the feed creation server-side script failed with a 500 internal server error because it was not converted to the new YAML configuration (due to a bug - to be exact: a missing slash - in the .gitignore). While working on fixing this issue, I also upgraded to the latest version of the feed generator (PicoFeed).
Morse Converter Web App 0.3
Hi folks! No! The writtenMorse project is not dead! Yesterday I released version 0.3 of the Morse converter web app. This update brings better performance when converting large texts thanks to a new converting engine written in Dart. You can test it now live at mmk2410.org/morseconverter. Feel free to give me feedback either to me at opensource(at)mmk2410(dot)org or on the GitLab project. Thanks!
Rangitaki Version 1.4.3
Since the release of Rangitaki 1.4.0 two weeks ago there where three point releases. 1.4.1 and 1.4.2 brought changes to the authentication of the RCC and the RCC API. Caused by these changes you have to rerun php bin/init_rcc.php. To read more about this change habe a look at: https://phab.mmk2410.org/T116 Version 1.4.3 brings the following bugfixes: [FIX] Missing space in drawer between "Blogs on" and blogname [FIX] Background layer was not removed if drawer was closed Besides these fixes Rangitaki 1.
Rangitaki Version 1.4
Yesterday I released Rangitaki version 1.4 with the following new features and fixes: Three new scripts in the bin folder to simplify the maintenance and setup. Read more below. Rangitaki API for working with your Rangitaki installation from other apps. Read on how to use the API in the documentation SASS and CoffeeScript capabilities for writing extensions and themes. These files are compiled and minimized using Gulp. Open links in articles in a new tab.
How to run a web app on your desktop
Running a web app or a website on your desktop is nowadays much easier thanks to GitHub’s Electron. Why would someone want this? Well… This is a good question. For me there are only two reasons: you can start it from your launcher and it’s handled as its own application. But thats not why I’m writing this guide. My motvation is simple: It works. Installing required software For this guide you need npm and git.