[Feature Request] File Snip-its / Includes #2750
Replies: 1 comment
-
Based on the context provided, it seems you are suggesting a feature for the Homepage project that allows splitting the configuration files into smaller segments for better manageability, especially when different teams are using different instances but require some common sections. As of my knowledge cutoff date in April 2023, there is no direct mention in the provided documentation of the Homepage project supporting the inclusion of external YAML snippets or files using an However, the idea of using symbolic links (symlinks) or mounting a Docker volume that contains the "master" files is a common practice for sharing configuration across multiple instances. This approach would allow you to maintain a single source of truth for the common sections and ensure consistency across different instances. For the symlink approach, you would create a symlink in each instance's configuration directory that points to the master file located elsewhere on the system. This would require that all instances have access to the same filesystem where the master file is stored. For the Docker volume approach, you would create a Docker volume that contains the master configuration files and mount this volume into the appropriate directory within each container running an instance of the Homepage project. This would allow each instance to read from the same set of configuration files. It's important to note that any changes to the master files would be reflected across all instances that use those files, so you should manage updates carefully to avoid unintended disruptions. If this feature is not currently supported and you would like to see it implemented, you may consider opening a feature request on the Homepage project's GitHub repository. The maintainers and contributors of the project can then discuss the feasibility and potential implementation of such a feature. Remember to check the latest documentation or the project's repository for any updates or changes that may have occurred after my knowledge cutoff date. Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer above is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course! Thanks for using Homepage! ❤️ This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
Description
Howdy,
I would be a neat feature to have the ability to split config files (bookmarks and services specifically) up into smaller segments/snip-its and include them into a configuration file for easier readability. Implementation could be done similar to local icons, or in relation to the config files directory.
File: services.yaml
File: /snips/service-group1.yaml
File: /snips/service-group2.yaml
Other
My company is setting up different instances for different teams. My leadership wants some sections to be the same on every instance. We would like to create a single "master" file or few with the service/bookmark groups, then either 1), create sym links to the "master" file in each instance, or 2) mount a docker volume with the "master" file(s) in them to reference.
Beta Was this translation helpful? Give feedback.
All reactions