Add large files repo for website assets

[SebastianBezold]

Adding new repo eclipse-tractusx.github.io.largefiles, as requested in https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3499 Git LFS settings have to be configured locally and persisted in .gitattributes after repo creation

[github-actions[bot]]

Diff for feade36ee197211fe9934b5c28fd782a4e552cdd:

```diff Printing local diff for configuration at '/home/runner/work/.eclipsefdn/.eclipsefdn/otterdog-configs/otterdog.json' Actions are indicated with the following symbols: + create ! modify ! forced update - delete Organization eclipse-tractusx[id=eclipse-tractusx] there have been 37 validation infos, enable verbose output with '-v' to to display them. + add repository[name="eclipse-tractusx.github.io.largefiles"] { + allow_auto_merge = false + allow_forking = true + allow_merge_commit = true + allow_rebase_merge = true + allow_squash_merge = true + allow_update_branch = false + archived = false + default_branch = "main" + delete_branch_on_merge = false + dependabot_alerts_enabled = true + dependabot_security_updates_enabled = false + description = null + gh_pages_build_type = "disabled" + has_discussions = false + has_issues = true + has_projects = true + has_wiki = true + homepage = null + is_template = false + merge_commit_message = "PR_TITLE" + merge_commit_title = "MERGE_MESSAGE" + name = "eclipse-tractusx.github.io.largefiles" + private = false + secret_scanning = "enabled" + secret_scanning_push_protection = "enabled" + squash_merge_commit_message = "COMMIT_MESSAGES" + squash_merge_commit_title = "COMMIT_OR_PR_TITLE" + template_repository = null + topics = [] + web_commit_signoff_required = false + } Plan: 1 to add, 0 to change, 0 to delete. ``` ```diff Showing diff to a canonical version of the configuration at '/home/runner/work/.eclipsefdn/.eclipsefdn/otterdog-configs/otterdog.json' Organization eclipse-tractusx[id=eclipse-tractusx] ```

[netomi]

In general, the PR is ok, just do double check wrt the name of the repo. Is the idea to enable GH pages for it and be able to access its content via eclipse-tractusx.github.io/largefiles ?

If that is the case, the repo name will result in this link:

http://eclipse-tractusx.github.io/eclipse-tractusx.github.io.largefiles

Some info here: https://tomcam.github.io/least-github-pages/github-pages-url.html

[SebastianBezold]

My last info on that is, that GitHub recommends to make contents accessible via GitHub release. So currently we do not plan on publishing via GitHub pages. The Help Desk Ticket comments also indicate a potential shift to the EF Download servers later on.

[netomi]

Makes sense. However, the name of the repo is certainly strange, as it seems to follow a certain convention for GH Pages (see https://github.com/eclipse-tractusx/eclipse-tractusx.github.io), while it will not result in the potentially expected result. May I suggest to rename the repo to largefiles for now?

[SebastianBezold]

Yes sure, I myself did not come up with the name, so maybe @Siegfriedk or @danielmiehle can explain the reason behind. In general, we are aware of how domain names + repo paths that GitHub uses for GitHub pages. I think the current name suggestion was made to indicate the close relation of the project website an the large files, that we will most likely only host for website content

[netomi]

change has been applied, repo exists now at: https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles

[netomi]

fyi: we have now added a first version of a dashboard like display of the current configuration:

It is inspired by the dashboard that the tractus-x project already developed themselves, any feedback is welcome.

It is accessible via https://eclipse-tractusx.github.io/.eclipsefdn/configuration/ There is also a link on the main page of this repo to it.

[SebastianBezold]

Hi @netomi,

oh wow that looks nice. I think especially the List of available secrets is a good addition. We got a lot of questions regarding the names in the past. 👍

[Siegfriedk]

Makes sense. However, the name of the repo is certainly strange, as it seems to follow a certain convention for GH Pages (see https://github.com/eclipse-tractusx/eclipse-tractusx.github.io), while it will not result in the potentially expected result. May I suggest to rename the repo to largefiles for now?

Hey! The assumption is, that the large file will ber eferenzed through a release were the naming shouldn't matter in context of github pages.