Update Servers

[brianteeman]

todo

Add update server details to the xml for the component and plugins

[genr8r]

Thanks @brianteeman I am still not sure where this will live (outside this repo?) after this session of JA winds down.

Our group is solid in NOT wanting it in core. I would like to see it added here - https://extensions.joomla.org/profile/profile/details/235317/

...but I know there are implications for that.
My greatest concern is that it not be relegated to something nice that was done as just a learning exercise back in 2025.

IDK what impact any of that has on what update servers are used or if we should just post releases here and link to them in the manifest as updates are added.

JA leadership has done a really nice job coordinating everything, but these types of questions are acknowledgment that as first session participants we are building the bridge as we are crossing it. btw - thanks for reviewing the work.

@sdwjoomla @Bodge-IT @softforge @Rahulsingh1939

[genr8r]

....and just leaving this here - #35

thanks @HermanPeeren

[HermanPeeren]

I am still not sure where this will live (outside this repo?) after this session of JA winds down. (...)
My greatest concern is that it not be relegated to something nice that was done as just a learning exercise back in 2025.

After we have rounded off this project we'll have two migration components (from JA and GSoC), both migrating the same stuff from WordPress to Joomla (in a different way). We have learned a lot from both (and from the 2023 migration project). They all have possibilities and limitations. Then it will be good to get some people together, and combine the best things. I have ideas for that.

[HermanPeeren]

"Update Server" sounds sophisticated, but it is just a few XML lines to show where the latest release can be found. Then Joomla can automatically check it and install the latest release with the proverbial push on the button. To do that, it is not important where this package will live after the project is finished: just use the current repo to add those lines.

To solve this issue you have to:

• Add an updateservers-tag to your manifest file. See: https://manual.joomla.org/docs/building-extensions/install-update/update-server/#3-tell-joomla-where-your-update-server-is
• Put an xml file online to point to the latest released installation package (so: it refers to the installable zip). This xml file usually is some update.xml, put in the root of your repo. See: https://manual.joomla.org/docs/building-extensions/install-update/update-server/#extension-server-type

So, the updateservers tag in the manifest refers to the update.xml (or however you want to call it) xml file in the repo and that refers to the downloadable latest released zip. An example for a module can be found in https://manual.joomla.org/docs/building-extensions/modules/module-development-tutorial/step11_update_server/

If you bundle your component, module and plugin into one package (see issue #48) you only have to put that updateservers-tag in the manifest of the package, not in that of the individual extensions. To complete the whole automation of a release, you can update the downloadurl-tag in your update.xml automatically with GitHub Actions...