We tried to reduce references to our Forgejo fork as of recently, because we observed that people repeatedly do the following mistake: People learn that Forgejo is a Codeberg project. They visit Codeberg, and find the Forgejo source (from our fork instead of the official Forgejo source). They deploy this code to their production machines, although it is probably not suited for the task.

We must take care not to add to this kind of confusion again, but unambiguously distinguish between the code that runs on Codeberg and the code you should deploy to your own machine, because the former comes with certain caveats and potential surprises.
— @fnetX

That kind of link seems helpful in finding all projects that one might find useful in running their own version of the whole website, but it's not so good at the core problem we want to address which is to getting the source that corresponds to each of the JavaScript blobs Codeberg serves.
— @qrpnxz

That page is not accessible without JavaScript, and I would not expect to find the source there. It should just be linked directly in the footer.
— @qrpnxz

Related to: https://codeberg.org/Codeberg/Community/issues/1416 > We tried to reduce references to our Forgejo fork as of recently, because we observed that people repeatedly do the following mistake: People learn that Forgejo is a Codeberg project. They visit Codeberg, and find the Forgejo source (from our fork instead of the official Forgejo source). They deploy this code to their production machines, although it is probably not suited for the task. > > We must take care not to add to this kind of confusion again, but unambiguously distinguish between the code that runs on Codeberg and the code you should deploy to your own machine, because the former comes with certain caveats and potential surprises. > — @fnetX > That kind of link seems helpful in finding all projects that one might find useful in running their own version of the whole website, but it's not so good at the core problem we want to address which is to getting the source that corresponds to each of the JavaScript blobs Codeberg serves. > — @qrpnxz > That page is not accessible without JavaScript, and I would not expect to find the source there. It should just be linked directly in the footer. > — @qrpnxz

n0toose referenced this pull request from Codeberg/Community

2024年01月25日 18:20:16 +01:00

Request: better public clarity about the exact live deployment of Codeberg #1416

wolftune commented

2024年01月25日 18:56:30 +01:00

First-time contributor

Copy link

As discussed in #1416 I suggest language like:

"exclusively intended for codeberg.org and NOT to be used for other deployments" and with a reference to Codeberg trademarks.

I would like to see the README state something about the scope of the differences between this and regular Forgejo. What is changed aside from branding?

As discussed in #1416 I suggest language like: "exclusively intended for codeberg.org and **NOT** to be used for other deployments" and with a reference to Codeberg trademarks. I would like to see the README state something about the scope of the differences between this and regular Forgejo. What is changed aside from branding?

n0toose commented

2024年01月26日 01:04:44 +01:00

Author

Contributor

Copy link

"exclusively intended for codeberg.org and NOT to be used for other deployments" and with a reference to Codeberg trademarks.

I am honestly not aware of the Codeberg trademark situation and how that works for us, but I think that I covered the differences in a way that would make the document timeless.

> "exclusively intended for codeberg.org and NOT to be used for other deployments" and with a reference to Codeberg trademarks. I am honestly not aware of the Codeberg trademark situation and how that works for us, but I think that I covered the differences in a way that would make the document timeless.