settings.yaml won't take effect

[distributev]

Description

Thank you for this project, I started to play with it and I really like how it achieves both power of customization and simplicity of use (not easy to achieve both in the same time)

This is the current content of settings.yaml and it is not taking any effect.

title: My Startpage
background: https://images.unsplash.com/photo-1502790671504-542ad42d5189?auto=format&fit=crop&w=2560&q=80

hideVersion: true

quicklaunch:
  searchDescriptions: true
  hideInternetSearch: true
  showSearchSuggestions: false

When I change bookmarks.yaml or services.yaml the homepage refreshes/rebuilds itself and I see the changes in the browser. When I change settings.yaml nothing is happening.

I also tried

1. Opening the page in a private browser windows to make sure it is not a browser cache issue - not working
2. Manually pressing the "Refresh" button on the bottom of the page - not working
3. Stopping and starting again the application using docker-compose commands - not working

I checked the list of issues and there are many basically saying the same thing "settings.yaml won't take effect" and all were close with "Can't reproduce" - some bugs say this in a direct way like this one #2016 some other bugs have another title but when reading their details basically mean the same thing "settings.yaml won't take effect".

homepage version

latest

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

[glime-ai[bot]]

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 below 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! ❤️

---

Based on the information provided and the context from the sources, it seems that you are experiencing an issue where changes to the settings.yaml file are not being reflected on your Homepage instance. Here are a few steps you can take to troubleshoot this issue:

1. Ensure Correct YAML Syntax: Verify that the settings.yaml file is correctly formatted and follows proper YAML syntax. YAML is sensitive to indentation and formatting, so even small mistakes can cause the file to not be read correctly. You can use online YAML validators to check your file, such as https://codebeautify.org/yaml-validator or https://jsonformatter.org/yaml-validator.

2. Check for Documentation Updates: Make sure that you are following the latest documentation for the settings.yaml configuration. Refer to the official documentation at https://gethomepage.dev/latest/configs/settings and https://github.com/gethomepage/homepage/blob/main/docs/configs/settings.md for the latest configuration options and examples.

3. Restart the Container: After making changes to the settings.yaml file, you may need to restart the container for the changes to take effect. Use the following Docker commands to restart the container:

   docker-compose down
   docker-compose up -d
   

   This will ensure that the application is fully reloaded with the new settings.

4. Check Container Logs: Look at the container logs to see if there are any error messages related to loading the settings.yaml file. You can view the logs by running:

   docker logs homepage
   

   This might provide insights into any issues with the settings file.

5. Review Open Issues and Discussions: Although you mentioned that similar issues were closed with "Can't reproduce," it's still worth reviewing open and closed issues on the GitHub repository, as well as discussions in the community, to see if others have found solutions to similar problems. Check out https://github.com/gethomepage/homepage/issues and https://github.com/gethomepage/homepage/discussions.

6. Ask for Help: If you've tried all the above steps and the issue persists, consider reaching out for help. You can open a new issue on the GitHub repository or ask a question in the discussions section. Provide as much detail as possible, including the steps you've taken to troubleshoot, any relevant logs, and the exact behavior you're experiencing.

Remember to back up your settings.yaml file before making any changes, and only make one change at a time to isolate the issue.

This comment was generated by Glime.

[distributev]

Further details - I found the logs/homepage.log file and it has this content in which it references all files but not settings.yaml even if I am treating settings.yaml in the same way and services.yaml and bookmarks.yaml this file is not enumerated in the log file

[2024-03-01T22:14:44.063Z] info: docker.yaml was copied to the config folder
[2024-03-01T22:14:44.065Z] info: services.yaml was copied to the config folder
[2024-03-01T22:14:44.065Z] info: bookmarks.yaml was copied to the config folder
[2024-03-01T22:14:44.072Z] info: widgets.yaml was copied to the config folder
[2024-03-01T22:14:44.072Z] info: custom.css was copied to the config folder
[2024-03-01T22:14:44.073Z] info: custom.js was copied to the config folder
[2024-03-01T22:14:44.103Z] info: kubernetes.yaml was copied to the config folder

What I did is that I went myself in the config folder and forced pasting the content which I wanted for settings.yaml and in that moment
homepage did refresh and took my custom settings.yaml

however just by treating that file the same way (doing the same things) as both bookmarks.yaml and services.yaml did not have any effect

I had to manually check the logs and see settings.yaml is not enumerated as one of the "was copied to the config folder" and then I manually pasted my content and it worked.

[Rowrk017]

Hi distributev, I think I might be having the same issue (settings.yaml not enumerated in log). Where exactly did you manually paste your content into?

I already have the base settings.yaml in my config folder but changes still aren’t taking effect.

[lemoncat7]

I also want to know how to deal with the problem that settings.yaml does not take effect.

[dmonterde]

I'm having the same issue within the last version.

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.