[GH-ISSUE #757] Starting migration to YAML format #8278

New Issue

GiteaMirror · 2026-05-20T07:55:32-05:00

GiteaMirror commented

2026-05-20 07:55:32 -05:00

Originally created by @Rabenherz112 on GitHub (Apr 15, 2026).
Original GitHub issue: https://github.com/awesome-foss/awesome-sysadmin/issues/757

Originally assigned to: @nodiscc on GitHub.

Hey,

I should have a bit more free time over the next few weeks (or at least be less busy), so I was thinking about gradually starting the migration to the YAML format to make maintenance easier.

Would you prefer that I start working in my own repo for now, or could you set up a dedicated -data (and at some point -html) repo? A shared repo might make it easier to discuss questions and issues, but I'm fine either way.

Originally created by @Rabenherz112 on GitHub (Apr 15, 2026). Original GitHub issue: https://github.com/awesome-foss/awesome-sysadmin/issues/757 Originally assigned to: @nodiscc on GitHub. Hey, I should have a bit more free time over the next few weeks (or at least be less busy), so I was thinking about gradually starting the migration to the YAML format to make maintenance easier. Would you prefer that I start working in my own repo for now, or could you set up a dedicated `-data` (and at some point `-html`) repo? A shared repo might make it easier to discuss questions and issues, but I'm fine either way.

GiteaMirror added the enhancement question / discussion labels 2026-05-20 07:55:32 -05:00

GiteaMirror commented

2026-05-20 07:55:34 -05:00

@nodiscc commented on GitHub (Apr 27, 2026):

Sorry for the delay

Feel free to start your own -data repo, you can still transfer it to the org later. This is what I did with awesome-selfhosted and I found it easier to start with this setup

@nodiscc commented on GitHub (Apr 27, 2026): Sorry for the delay Feel free to start your own -data repo, you can still transfer it to the org later. This is what I did with awesome-selfhosted and I found it easier to start with this setup

GiteaMirror commented

2026-05-20 07:55:35 -05:00

@Rabenherz112 commented on GitHub (May 3, 2026):

Small update: the repos, pipelines, and everything needed are now in place and working*.
Due to #786, there's currently no metadata available yet, so the website shows question marks for all projects metadata. Everything else should be ready to go.

Feel free to test out the contribution process as well as the new guidelines around it. Most of it is obviously copied from awesome-selfhosted, since it makes sense to keep both workflows as similar to each other as possible.

awesome-sysadmin-data - main repo used for contributing to the project
awesome-sysadmin-markdown - current markdown version, generated from the -data repo
awesome-sysadmin-html - website source code, used for hosting the site

Open ToDos for the migration are tracked here: https://github.com/Rabenherz112/awesome-sysadmin-data/issues/3

Feedback and questions are more than welcome

/cc @nodiscc @Technetium1 @kokomo123

*some pipelines will throw permanent errors, prob. even after migrating (unmaintained projects, dead links); I don't plan to fix these beforehand, mainly because fixing them once the new format is in place seems much easier

@Rabenherz112 commented on GitHub (May 3, 2026): Small update: the repos, pipelines, and everything needed are now in place and working*. Due to #786, there's currently no metadata available yet, so the website shows question marks for all projects metadata. Everything else should be ready to go. Feel free to test out the contribution process as well as the new guidelines around it. Most of it is obviously copied from awesome-selfhosted, since it makes sense to keep both workflows as similar to each other as possible. [awesome-sysadmin-data](https://github.com/Rabenherz112/awesome-sysadmin-data) - main repo used for contributing to the project [awesome-sysadmin-markdown](https://github.com/Rabenherz112/awesome-sysadmin-markdown) - current markdown version, generated from the `-data` repo [awesome-sysadmin-html](https://github.com/Rabenherz112/awesome-sysadmin-html) - website source code, used for hosting the site Open ToDos for the migration are tracked here: https://github.com/Rabenherz112/awesome-sysadmin-data/issues/3 **Feedback and questions are more than welcome** /cc @nodiscc @Technetium1 @kokomo123 *some pipelines will throw permanent errors, prob. even after migrating (unmaintained projects, dead links); I don't plan to fix these beforehand, mainly because fixing them once the new format is in place seems much easier

GiteaMirror commented

2026-05-20 07:55:35 -05:00

@kokomo123 commented on GitHub (May 3, 2026):

I feel like we could find a better icon for the awesome-sysadmin website, to make it separate and unique. That's the feedback so far as the website as is works fine, i'll test out the new stuff shortly.

@kokomo123 commented on GitHub (May 3, 2026): I feel like we could find a better icon for the awesome-sysadmin website, to make it separate and unique. That's the feedback so far as the website as is works fine, i'll test out the new stuff shortly.

GiteaMirror commented

2026-05-20 07:55:36 -05:00

@kokomo123 commented on GitHub (May 3, 2026):

Would also suggest avoiding file path collisions ig, git threw out a warning while cloning💀

@kokomo123 commented on GitHub (May 3, 2026): <img width="554" height="143" alt="Image" src="https://github.com/user-attachments/assets/a53a5a9c-b1a9-496a-9a4e-b6b8263e544a" /> Would also suggest avoiding file path collisions ig, git threw out a warning while cloning💀

GiteaMirror commented

2026-05-20 07:55:37 -05:00

@Rabenherz112 commented on GitHub (May 3, 2026):

I swear sometimes windows is just... Should be fixed.

@Rabenherz112 commented on GitHub (May 3, 2026): I swear sometimes windows is just... Should be fixed.

GiteaMirror commented

2026-05-20 07:55:38 -05:00

@kokomo123 commented on GitHub (May 3, 2026):

Did the following tests:
PR - ✅
Committing to the repository - ✅
Labels - ✅
Merging - ✅
Thank you raben for helping me test! Test successful

@kokomo123 commented on GitHub (May 3, 2026): Did the following tests: PR - ✅ Committing to the repository - ✅ Labels - ✅ Merging - ✅ Thank you raben for helping me test! Test successful

GiteaMirror commented

2026-05-20 07:55:39 -05:00

@Technetium1 commented on GitHub (May 4, 2026):

Would like to see Dependabot configured, no immediate concerns otherwise.

@Technetium1 commented on GitHub (May 4, 2026): Would like to see Dependabot configured, no immediate concerns otherwise.

GiteaMirror commented

2026-05-20 07:55:41 -05:00

@Rabenherz112 commented on GitHub (May 4, 2026):

Would like to see Dependabot configured

I don't see it necessary here, for a couple of reasons:

The only Python dependency is nodiscc/hecat, which is maintained within our own ecosystem rather than being an external third-party package. Version bumps already happen deliberately whenever there's a hecat release we want
Also it is installed straight from a pinned Git tag in the Makefile, there's no requirements.txt / setup.py / ... for Dependabot to scan, so the pip ecosystem config wouldn't really have anything to track

@Rabenherz112 commented on GitHub (May 4, 2026): > Would like to see Dependabot configured I don't see it necessary here, for a couple of reasons: - The only Python dependency is `nodiscc/hecat`, which is maintained within our own ecosystem rather than being an external third-party package. Version bumps already happen deliberately whenever there's a hecat release we want - Also it is installed straight from a pinned Git tag in the `Makefile`, there's no `requirements.txt` / `setup.py` / ... for Dependabot to scan, so the pip ecosystem config wouldn't really have anything to track

GiteaMirror commented

2026-05-20 07:55:42 -05:00

@Technetium1 commented on GitHub (May 4, 2026):

I have missed major versions of actions because it wasn't there to remind me. It does have value, and takes next to no CI time when run weekly. It's not important for hecat here. It can be as simple as:

version: 2
updates:
  - package-ecosystem: "github-actions"
    directory: ".github/workflows"
    schedule:
      interval: "weekly"

@Technetium1 commented on GitHub (May 4, 2026): I have missed major versions of actions because it wasn't there to remind me. It does have value, and takes next to no CI time when run weekly. It's not important for hecat here. It can be as simple as: ```yml version: 2 updates: - package-ecosystem: "github-actions" directory: ".github/workflows" schedule: interval: "weekly" ```

GiteaMirror commented

2026-05-20 07:55:43 -05:00

@kokomo123 commented on GitHub (May 4, 2026):

That makes sense honestly, let's put dependabot to do only github workflows

@kokomo123 commented on GitHub (May 4, 2026): That makes sense honestly, let's put dependabot to do only github workflows

GiteaMirror commented

2026-05-20 07:55:43 -05:00

@Rabenherz112 commented on GitHub (May 7, 2026):

Done in d2583fefc9 Instantly found something, lel: https://github.com/Rabenherz112/awesome-sysadmin-data/pull/5

@Rabenherz112 commented on GitHub (May 7, 2026): Done in https://github.com/Rabenherz112/awesome-sysadmin-data/commit/d2583fefc9e2620244844621c5fc7171641af3bd Instantly found something, lel: https://github.com/Rabenherz112/awesome-sysadmin-data/pull/5

GiteaMirror commented

2026-05-20 07:55:44 -05:00

@kokomo123 commented on GitHub (May 7, 2026):

well done, well done

@kokomo123 commented on GitHub (May 7, 2026): well done, well done

GiteaMirror commented

2026-05-20 07:55:45 -05:00

@nodiscc commented on GitHub (May 10, 2026):

Everything looks good, thanks for taking the time to do this.

One thing I noticed after cloning the latest revision of https://github.com/Rabenherz112/awesome-sysadmin-html is that it does not have the latest stars counts/last update time from cd57845d49.

So what are the next steps? In order, I think:

Transfer these repos to the https://github.com/awesome-foss organization (not needed for awesome-sysadmin-markdown, see below)
Ensure @Rabenherz112 keeps owner permissions
Change the target repository for markdown generation to https://github.com/awesome-foss/awesome-sysadmin
Change the target repository for html generation to https://github.com/awesome-foss/awesome-sysadmin-html
Setup https://sysadmin.awesome-selfhosted.net on the current awesome-selfhosted VPS with the same mechanism as awesome-selfhosted [1]
Update CONTRIBUTING.md and other docs to reflect the new contribution process
Keep an eye on the automation to ensure everything works as expected
Anything more?

@nodiscc commented on GitHub (May 10, 2026): Everything looks good, thanks for taking the time to do this. One thing I noticed after cloning the latest revision of https://github.com/Rabenherz112/awesome-sysadmin-html is that it does not have the latest stars counts/last update time from https://github.com/Rabenherz112/awesome-sysadmin-data/commit/cd57845d494375902cf027a68194f90f8330863a. So what are the next steps? In order, I think: * [ ] Transfer these repos to the https://github.com/awesome-foss organization (not needed for awesome-sysadmin-markdown, see below) * [ ] Ensure @Rabenherz112 keeps owner permissions * [ ] Change the target repository for markdown generation to https://github.com/awesome-foss/awesome-sysadmin * [ ] Change the target repository for html generation to https://github.com/awesome-foss/awesome-sysadmin-html * [ ] Setup https://sysadmin.awesome-selfhosted.net on the current awesome-selfhosted VPS with the same mechanism as awesome-selfhosted [[1]](https://github.com/nodiscc/toolbox/tree/master/ARCHIVE/ANSIBLE-COLLECTION/roles/awesome_selfhosted_html) * [ ] Update CONTRIBUTING.md and other docs to reflect the new contribution process * [ ] Keep an eye on the automation to ensure everything works as expected * [ ] Anything more?

GiteaMirror commented

2026-05-20 07:55:45 -05:00

@Rabenherz112 commented on GitHub (May 10, 2026):

One thing I noticed after cloning the latest revision of https://github.com/Rabenherz112/awesome-sysadmin-html is that it does not have the latest stars counts/last update time from cd57845d49.

This is due to the lint fail after the metadata update due to #790.

Transfer these repos to the https://github.com/awesome-foss organization (not needed for awesome-sysadmin-markdown, see below)

I prob. need some more permissions for that? Trying to transfer it results in:
https://fs.ravshort.com/85AlW.png
https://fs.ravshort.com/8kNuF.png

Ensure @Rabenherz112 keeps owner permissions

Not really needed. I am fine with keeping the current permissions I also have here / awesome-selfhosted after the migration phase is done. (Keeping it for the migration phase would be useful)

The rest sounds good. I outlined something similar in https://github.com/Rabenherz112/awesome-sysadmin-data/issues/3

Edit:
Actually one other thing would prob. to get the git history of awesome-sysadmin over into awesome-sysadmin-data. I think we did the same over in awesome-selfhosted when we migrated. (prob. something you will need to do, since I don't know git good enough for that)

@Rabenherz112 commented on GitHub (May 10, 2026): > One thing I noticed after cloning the latest revision of https://github.com/Rabenherz112/awesome-sysadmin-html is that it does not have the latest stars counts/last update time from https://github.com/Rabenherz112/awesome-sysadmin-data/commit/cd57845d494375902cf027a68194f90f8330863a. This is due to the lint fail after the metadata update due to #790. > Transfer these repos to the https://github.com/awesome-foss organization (not needed for awesome-sysadmin-markdown, see below) I prob. need some more permissions for that? Trying to transfer it results in: https://fs.ravshort.com/85AlW.png https://fs.ravshort.com/8kNuF.png > Ensure @Rabenherz112 keeps owner permissions Not really needed. I am fine with keeping the current permissions I also have here / awesome-selfhosted after the migration phase is done. (Keeping it for the migration phase would be useful) The rest sounds good. I outlined something similar in https://github.com/Rabenherz112/awesome-sysadmin-data/issues/3 Edit: Actually one other thing would prob. to get the git history of awesome-sysadmin over into awesome-sysadmin-data. I think we did the same over in awesome-selfhosted when we migrated. (prob. something you will need to do, since I don't know git good enough for that)

GiteaMirror commented

2026-05-20 07:55:46 -05:00

@Rabenherz112 commented on GitHub (May 17, 2026):

One thing I noticed after cloning the latest revision of https://github.com/Rabenherz112/awesome-sysadmin-html is that it does not have the latest stars counts/last update time from cd57845d49.

Website now finally also has all the metadata https://rabenherz112.github.io/awesome-sysadmin-html/ ; yaay
(Would have been a lot easier, if I wouldn't permanently missed an ERROR: in update-metadata and pushed all the fixes in a single PR instead of multiple ones..)

@Rabenherz112 commented on GitHub (May 17, 2026): > One thing I noticed after cloning the latest revision of https://github.com/Rabenherz112/awesome-sysadmin-html is that it does not have the latest stars counts/last update time from https://github.com/Rabenherz112/awesome-sysadmin-data/commit/cd57845d494375902cf027a68194f90f8330863a. Website now finally also has all the metadata https://rabenherz112.github.io/awesome-sysadmin-html/ ; yaay (Would have been a lot easier, if I wouldn't permanently missed an `ERROR:` in update-metadata and pushed all the fixes in a single PR instead of multiple ones..)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#8278