From 4c0a6954fb6df177f842de4bf3e3a97eb171a11b Mon Sep 17 00:00:00 2001 From: lutangar Date: Wed, 30 Jun 2021 10:32:15 +0200 Subject: [PATCH] Document a way to update the last available version of a plugin manually May comes in very handy to quickly test a plugin in a production like environment before it reaches a greater world. > This magic trick comes from @Chocobozzz himself, who passed it on to @JohnXLivingston, who then passed it down to me. --- support/doc/plugins/guide.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/support/doc/plugins/guide.md b/support/doc/plugins/guide.md index 3715a5086..568c0662f 100644 --- a/support/doc/plugins/guide.md +++ b/support/doc/plugins/guide.md @@ -754,6 +754,8 @@ Left menu links can be filtered (add/remove a section or add/remove links) using PeerTube plugins and themes should be published on [NPM](https://www.npmjs.com/) so that PeerTube indexes take into account your plugin (after ~ 1 day). An official plugin index is available on [packages.joinpeertube.org](https://packages.joinpeertube.org/api/v1/plugins), with no interface to present packages. +> The official plugin index source code is available at https://framagit.org/framasoft/peertube/plugin-index + ## Write a plugin/theme Steps: @@ -937,6 +939,12 @@ $ npm publish Every time you want to publish another version of your plugin/theme, just update the `version` key from the `package.json` and republish it on NPM. Remember that the PeerTube index will take into account your new plugin/theme version after ~24 hours. +> If you need to force your plugin update on a specific __PeerTube__ instance, you may update the latest available version manually: +> ```sql +> UPDATE "plugin" SET "latestVersion" = 'X.X.X' WHERE "plugin"."name" = 'plugin-shortname'; +> ``` +> You'll then be able to click the __Update plugin__ button on the plugin list. + ### Unpublish If for a particular reason you don't want to maintain your plugin/theme anymore