In the past days, I have upgraded my forums to the latest Beta release of Flarum, 0.1.0-beta.9.
I just want to say how glad I am with using Flarum. It does not need much resources, runs fine in shared hosting at Hostsharing, and is continually improved. Even though it is not a stable version yet, the upgrades work alright.
Here is a summary of contributions I am trying to give back to Flarum:
- my first extension: Post Notifications
- Migration from Discourse to Flarum: Blog Post
- Report of our OpenPetra forum in the show case section: Forum for OpenPetra community
- Report of our Nazareth forum in the show case section: Private Forum for Nazareth Charity
- German instructions how to install and maintain Flarum in the shared hosting environment at Hostsharing: Flarum installieren
Here are now some links and notes about developing my own extension, Post Notifications:
- Description of the extension: Post Notifications
- The source of the extension: https://github.com/tpokorra/flarum-ext-post-notification
- The versioning for Composer is done with the Git tags.
- Documentation about Flarum extensions: https://flarum.org/docs/extend
For the frontend for the admin settings, I need to transpile the code (see Frontend Development: Transpilation). I don’t do that directly on Hostsharing, because I don’t have npm there, and don’t want to use up the webspace. Therefore I have the development environment on my local Ubuntu.
cd flarum-ext-post-notification cd js npm install webpack npm install npm run build git add dist cd .. rsync -zvhr --exclude node_modules --exclude .git . email@example.com:doms/testflarum.mydomain.de/htdocs-ssl/vendor/tpokorra/flarum-ext-post-notification
It seems for upgrading the extension across minor versions, I need to run
composer require again, since
composer update only updates between releases? Or perhaps I was too quick, and the new tag did not arrive at Packagist yet?