Do you have suggestions for compatibility with other code platforms?

[schulle4u]

Since we are living in uncertain times (also from a technological point of view), it seems wise not to entrust your code to a single platform. Therefore I have been trying to find out how to upload and maintain a repository on multiple platforms simultaneously. I was only interested in the Yellow-specific documentation adjustments to the repositories. Information on mirroring GitHub repositories in general is well documented.

In principle, offering an extension on multiple code hosting platforms is not a problem. However, the installation settings in the extension.ini file only allow one download and documentation URL, so a choice of platform as the main distribution site is required before publishing. Only the relative paths currently used in the documentation for screenshots and language switching make things a little tricky.

<p align="right"><a href="README-de.md">Deutsch</a> &nbsp; <a href="README.md">English</a></p>

and

<p align="center"><img src="SCREENSHOT.png" alt="Screenshot"></p>

This leads to a navigation error e.g. on Codeberg (and other Forgeo/Gitea instances). However, if you only publish there, you can simply specify the relative repository path.

<p align="center"><img src="src/main/SCREENSHOT.png" alt="Screenshot"></p>

To avoid the need to work with absolute URLs for mirrored repositories, you can use a Markdown-based solution, as this works on both platforms. To keep the text alignment, links are enclosed in a div element.

<div align="right">

[Deutsch](./README-de.md) [English](./README.md)

</div>

and

<div align="center">

[![Screenshot](./SCREENSHOT.png)](./SCREENSHOT.png)

</div>

As you can see, the paths are specified with a preceding dot ./, which is recognised by both platforms and resolved to give the correct repository path. However, this only works in Markdown, not in HTML.

In my opinion, this is the cleanest solution that does not fundamentally damage the current documentation standard. What do you think? Further suggestions are very welcome. 🙂

[markseuffert]

Here's what I found out. On Codeberg the link normalisation works differently depending on your current location. Relative links work fine on a subpage, but they don't work on the repository start page. Relative links can be improved with a prefix like ./README.md and under certain conditions. For links, it works ONLY in Markdown format, it DOES NOT work when the Markdown is within a <p>...</p>. For images, it makes apparently no difference at all, we can use the same HTML format on Codeberg and GitHub.

Since we use absolute URLs in download links, perhaps use them in language links too?

[schulle4u]

Absolute links are fine. As a developer you would need to select a primary development platform and could then mirror to Codeberg or from Codeberg back to GitHub. However, navigating the mirrored repository could be confusing because you might end up unintentionally on the original platform. You might feel a little offended if you refuse to use GitHub.

[pftnhr]

Today, I managed to mirror a Forgejo repo to GitHub for the first time. The instructions on both sites have some significant gaps...

[pftnhr]

With regard to Yellow, it should suffice for starters to transfer all repositories with Status: available to Codeberg. This would provide everything needed to operate Yellow properly.

All you need to do is add a note to the readme files in the respective GitHub repositories stating that they are now hosted on Codeberg. I've already moved mine over: https://codeberg.org/pftnhr but I still need to update the links.

Oh yes, just update the links there and you're good to go.

[markseuffert]

Quick update regarding language links. I reported the problem with broken links in readme files on Codeberg, see #2270. A possible workaround are absolute URLs if your repositories are exclusively hosted on Codeberg, for example @simonpipe uses absolute URLs in his readme files.