Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#13 Yesterday 12:00:05
- abutcher
- Plugin Author
- Registered: 2023-06-29
- Posts: 14
Re: Plugin development and publication using ais_txpplugin_packager
If anyone is interested, this is now available as a part of a simple GitHub action, so you can automate your releases using workflows on GitHub.
This is derived from an internal tool, but I’m on a mission to clean-up and publish a bunch of things lately.
A simple example (documented here) is to build a TXT package and a SHA-256 checksum file and add them to your release when you publish a release on GitHub.
Maybe it’s useful for someone else’s workflow.
Offline
Re: Plugin development and publication using ais_txpplugin_packager
Very cool! Gocom has something similar but I never really groked it, and I believe it was tied to his specific plugin organisation. Maybe I’ll fare better this time around.
Now I just need to update a plugin to try it out. Thank you!
TXP Builders – finely-crafted code, design and txp
Offline
#15 Today 10:39:00
- abutcher
- Plugin Author
- Registered: 2023-06-29
- Posts: 14
Re: Plugin development and publication using ais_txpplugin_packager
I hadn’t seen that, but then again I don’t usually develop in the web world anymore (that was a past life, 24+ years ago), so I’m really out of the loop for much of this.
I think because of this I try to keep things simple, because turn-arounds need to be quick and releasing anything publicly takes time away from other work. I think that’s why I use Textpattern when I need CMS for projects, and why I like the simplicity of the TXT plugin packages. All this saves time and money for clients.
If it helps, you can look at one of my repositories to see how I organise things. I just keep it very flat and put everything in the root, since it’s nothing complex, but you can point the action to any subdirectory you want and it’ll pack up the contents into a TXT for you. You can copy the example simple.yml into your repository as .github/workflows/release.yml and modify it using these instructions. Keep in mind that the simple example only triggers when the release is published – you’ll have to adjust the release type trigger if you want it to build on any other status.
Offline