* docs: Update documentation to reflect change from `config/` to `files/`
* docs(files): Match documentation between template & module.yml
* docs(files): Add example about using subfolder
* docs(files): Some small style fixes
* docs: Fix `files/system` typo
Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com>
* docs: Fix `files/system` typo pt. 2
Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com>
* chore(files): Update typespec to be compatible with legacy & new recipe
Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com>
---------
Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com>
* chore: Adjust modules to use the future `/tmp/files/` directory
* docs: Replace old `config/` with `files/` directory
* Revert "docs: Replace old `config/` with `files/` directory"
This reverts commit 68870a3d02136860b4f3bca2d34618d71dcae160.
* chore(files): Support new recipe format proposed by @xynydev
* chore(files): Support legacy recipe format along with new one
Mixed usage of it in recipe is supported too.
---------
Co-authored-by: Gerald Pinder <gmpinder@gmail.com>
Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com>
Should avoid issues of users typing ID wrongly, which would fail the whole module on booted system, so nothing would get installed or removed.
Only FlatHub repo is supported as it's the most popular flatpak repo & it's easy to implement safe-check for it.
* chore(bling): uncomment example options
* refactor(brew): remove duplicate "configuration options" setting in README, improve TSP docs
* fix(chezmoi): make example an example and not a doc of the configuration options
* chore(rpm-ostree): remove fake example
examples should be runnable
* fix(rpm-ostree): add replacing packages to typespec schema
* fix(rpm-ostree): actually install the packages the repos are added for
* feat(rpm-ostree): showcase installing from URL and using optfix in example
* fix(rpm-ostree): add optfix to typespec
* fix(systemd): real-world example instead of configuration docs duplicate
They are only needed when building the akmods, but not when shipping them.
This should considerably remove the bloat from the images without affecting the existing functionality.
* chore(gnome-extensions): Make extension URL quering more robust
If there are multiple Gnome extensions with the same name, & they are compatible with Gnome version in the base image, then build will fail.
Previously, build would always fail if there are extensions with duplicate names.
* docs(gnome-extensions): Fix typo
* docs(gnome-extensions): Mention github repo
* fix(gnome-extensions): Version checking
* chore(gnome-extensions): Make operation order better for reading
* feat(gnome-extensions): Use new PK ID installation method
* fix(gnome-extensions): Unbound variable error
* fix(gnome-extensions): Legacy config order logic
* docs(gnome-extensions): Fix spacing
* docs(gnome-extension): Delete false-claim about better config readability
* chore(gnome-extensions): Add safe check for "null" in if `jq` parsing
* chore(gnome-extensions): Update uninstall step to use PK
This will break config for uninstalling extensions in literal names, but I bet that no one uses this feature yet since this extension is still new & fresh, so I'll just break it.
* Revert to the current module state
* docs(gnome-extensions): Add README details about missing gschema.compiled file
* chore(gnome-extensions): Introduce hybrid literal-name/PK config
If 2 or more same-named extensions are recommended, then user is recommended to use PK ID instead.
* chore(gnome-extensions): Ignore ShellCheck 2128 error, since it's harmless & intended
* chore(gnome-extensions): Also ignore harmless SC2178 notice
* chore(gnome-extensions): Use UUID for matching compiled.gschema workaround rather than extension name
* docs(gnome-extensions): Add note in module.yml that PK can be used
