mbirth 🇬🇧

Collector of social media accounts. Speaks 🇬🇧 and 🇩🇪.

  • 1 Post
  • 214 Comments
Joined 2 years ago
cake
Cake day: June 1st, 2023

help-circle



  • I just found a pattern. Monday, where it was showing up 1 hour earlier, I was connected to my M365 Cloud PC via my home Macbook. Then, the appt (only this one) showed up wrong.

    Yesterday, I was using that same Cloud PC from my work (Windows-)laptop and the appt showed up at the correct time.

    Today, I’m using the exact same Cloud PC - without rebooting - from my Macbook again and Outlook shows it wrong again.

    So, that virtual machine that’s called Cloud PC does something different depending on the system you’re connecting from. How stupid is that?



  • You’re not alone. We’re forced to use Classic Outlook at work.

    I’ve got a monthly recurring appointment for a Zoom call. That was due today again. There was the switch to winter time last week and Outlook decided to “adjust” the scheduled time for me.

    That meeting was originally for 11am and should continue to be at 11am during standard time. However, yesterday I’ve noticed that Outlook put it at 10am (and showed a proud message that it adjusted it due to timezone change). No way to undo it.

    Teams continued to show it at 11am where it belongs.

    Now, when trying to move it to 11 in Outlook, Teams moved it to 12.

    And when I opened Outlook this morning, the appt was at 11am where it belongs and Outlook and Teams agreed again.

    Mind you, this was only this external Zoom call. All other appointments are still correct. Very weird.













  • The important bit is -v /opt/podman/searxng/config:/etc/searxng:Z in the podman call. This will mount your local directory (i.e. on the host the container is running on) /opt/podman/searxng/config into the container as /etc/searxng (which is where SearXNG is searching for its config). Make sure that the local directory exists and is writeable by your user account before starting the container. This way your config will persist even when the container gets replaced by an updated version.

    IIRC, after running the container for the first time, SearXNG should put a settings.yml and uwsgi.ini there. You can edit them and restart the container for the changes to take.

    On later container updates, SearXNG will put the latest versions of the default configs as settings.yml.new and uwsgi.ini.new. This way it doesn’t overwrite your config and allows you to manually merge the new defaults into your running config. (If you only see the *.new files after starting the container for the first time, rename them and remove the .new part.)