Extiverse. Breaching the frontier in Flarum forum and community management

davetodave178

luceos Great it works now also in this case. Thank you so much for adding this endpoint this quickly! 🙌

davetodave178

@luceos If you want to use the workflow for Blomstra Premium Extensions, I think the following should work just by copy/pasting it (besides adding the Extiverse API token as a secret). Requirements for this particular workflow to work are:

Owner/Vendor is the same on GitHub as it is on Extiverse
Extensions on GitHub are prefixed with flarum-ext- but not on Extiverse (for example blomstra/flarum-ext-gdpr and https://extiverse.com/extension/blomstra/gdpr

.github/workflows/sync.yml

name: Extiverse

on:
  workflow_dispatch:
  push:
    tags:
      - '*'

jobs:
  sync:
    name: Sync Extension
    runs-on: ubuntu-latest

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Sync with Extiverse
        run: |
          REPO_NAME="${{ github.repository }}"
          OWNER=${REPO_NAME%%/*}
          REPO=${REPO_NAME##*/}
          MODIFIED_REPO=${REPO#flarum-ext-}
          SYNC_URL="https://extiverse.com/api/premium-extensions/$OWNER/$MODIFIED_REPO/sync"

          curl -X GET \
            -H "Authorization: Bearer ${{ secrets.EXTIVERSE_API_TOKEN }}" \
            -H "Content-Type: application/json" \
            $SYNC_URL

luceos

davetodave178 thanks for that, much appreciated to ping back with this solution.

I will share this in the extiverse premium discord channel, Dave let me know in DM if you want to hop into there for an occasional update as well.

davetodave178

In case you want to make the workflow reusable and thus better maintainable, you can create a new dedicated repo and use a slightly adjusted version of the workflow above. Define that the job is triggered on workflow_call (trigger when a new tag is pushed will still be defined in each extension repository itself).

Please note that you must make the workflow repository accessible from other repositories in the same organization. See this GitHub Doc for more information.

your-organization/flarum-workflow-example/.github/workflows/sync.yml

on:
  workflow_call:

jobs:
  sync:
    name: Sync Extension
    ...

Now if you want to use this reusable workflow in a extension repository, you can include it like this:

your-organization/flarum-ext-example/.github/workflows/sync.yml

name: Extiverse

on:
  push:
    tags:
      - '*'

jobs:
  trigger-sync:
    name: Invoke Workflow
    uses: your-organization/flarum-workflow-example/.github/workflows/sync.yml@master
    secrets: inherit

Again, please note that you have to set the secret either in each repository you want to use this workflow or at the organization level. AFAIK, you should be able to access either one with e.g.${{ secrets.EXTIVERSE_API_TOKEN }}.

The secret must be an API token (i.e. api:read) and not a composer token (e.g. composer:download).

luceos

davetodave178 please clearly state this has to be an API token. Not a composer one.

davetodave178

luceos Good point. I appended it to the post above.

DaleZ

Hello, I wonder what Extiverse uses to determine that an extension is incompatible. One of my extension is marked as incompatible although it can work correctly on the latest flarum. (More info: wolfshards DaleZ)

GreXXL

DaleZ can you share the extension in question? It can either be because of the information provided by the extension - or it was marked incompatible because of the last Flarum major release (1.0) and the author never applied an update that it is compatible.

DaleZ

GreXXL I mentioned, it's in DaleZ (fluent-theme).
The content I filled into the composer.json was borrowed from OXO Theme, but then after wolfshards points out the problem, I found the OXO Theme was also marked as incompatible. 😂

luceos

DaleZ OXO theme is incompatible because it uses a wildcard (*) constraint on Flarum. I decided that that marks it incompatible when Flarum 1.0 landed. Most, if not all, extensions made for beta were no longer compatible. If you really want to have a wide constraint like that, use 1.*. This will again be important when releases for Flarum 2 will surface, a wildcard constraint will make it seem like the extension is compatible, but it is almost guaranteed it will not be.

DaleZ

luceos OK, I'll change it soon. But it's still strange - Confix Theme also used a *, but Extiverse thinks it's compatible. 🤔

GreXXL However, my theme was also published after first release. Though not a big deal but it just no reason.

GreXXL

DaleZ because it was updated after 1.0 released.

luceos

GreXXL I am looking at the code, but it actually does require a valid constraint, this code has been in Extiverse for the past five years:

        try {
            $lower = $this->versionParser->normalize($lower);
        } catch (UnexpectedValueException $e) {
            // This happens when a dev sets flarum/core:* for instance. Let's not allow that.
            $version->compatibilities()->sync([]);

            return $version;
        }

DaleZ That is because @yannis cheated the system 🤣 , version 1.0.1 of his extension has compatibility with ^1.0. Extiverse thinks that version is compatible, regardless of his newer 2.x versions, which are not.

What I can do for the future is mark wildcards compatible with the major version it was written for. So checking the time of the release of that version and identifying the major version of that period...

Another solution that will probably be added somewhere in the future is the ability to report abandoned/broken extension versions. This will then add a warning, or remove the extension from the list entirely until a new version is tagged.

But setting a stricter constraint, in all regards, is the wiser solution. At some point your extension will break, not giving off the impression it still is compatible will reduce the chances of people bricking their community.

DaleZ

Hello there again. 7 hours ago, I published an update for solving this problem (DaleZ), but it seems that the theme isn't show at the Extensions page right now.
Any problem to my update?

DaleZ

luceos Aww, I know. ~~Maybe I can cheat extiverse too. 😂😂😂~~
Dividing extensions into compatible and not is surely a good idea, but its behavior is really should be smarter.

yannis

luceos @DaleZ
Just like that, cause only changes by 'css', unless the 'ID' or 'Class' is to change, are basically compatible, so I do it "*" . Otherwise, I would have to change the version number once for minor version upgrades, which would be repetitive tasks.

luceos

Extiverse has been down for a few hours. I'm not behind a pc and as such cannot restore the service for now. My apologies for any inconvenience.

I'm hoping to identify and resolve the issue within the next three to four hours.

luceos

Seems the server completely crashed around 11 AM CEST. A hardware reset recovered the system just now and everything is up again.

luceos

yannis you can use 1.* to make it compatible with any Flarum 1 installation. As we are working on 2.0 just using * would imply your extension would be compatible with it, which is not the case. This same logic applied back when we went from 0.1 beta to 1.0 stable and it still is best way to mark compatibility. Extiverse has to be on the safe side of things to protect installs from breaking.

yannis

luceos roger that ☺️

luceos

In the week of May 27th, Extiverse will migrate over into the new Flarum.org website.

More information about why this is happening can be found here on discuss: https://discuss.flarum.org/d/32812

One portal, flarum.org

The new Flarum website will merge several services of the ecosystem into one, thus increasing discoverability of extensions, services and partners within one portal. A preview can be found here: https://next.flarum.org

The migration

The new Flarum website consist mostly of features that were previously part of Extiverse, as such we are migrating over your account and your subscriptions to this new portal.

During the migration, Extiverse will be placed in a read only maintenance mode. You will not be able to log in on Extiverse.com, make changes to your account or subscriptions. You will be able to use composer to install premium extensions you've subscribed to.

Once all data has been migrated over, you will be able to log into your account on flarum.org with your Extiverse credentials. A warning will be shown on Extiverse.com to direct you to the right portal immediately after the migration and within a month or two Extiverse will cease to exist.

Opt out

If you don't want to be migrated to the new website, please log in on your Extiverse account and delete it from the account manage page before the 27th. If you still have active subscriptions deleting your account will void them. Should you run into any issues, feel free to let me know.

I welcome any feedback and questions, feel free to comment here or reach out to me directly at luceos@flarum.com.

PS. this information is going to be sent to each Extiverse user by email today.

Thank you,

Daniël Klabbers, aka @luceos

Extiverse, owner
Flarum Foundation, commercial representative
Flarum B.V., co-founder

« Previous Page Next Page »