I don’t have an answer for you but I have one instead. When I attempted to do swarm my biggest challenge was shared storage. I was attempting to run a swarm with shared storage on a NAS. Literally could not run apps, ran into a ton of problems running stacks (NAS share tried SMB and NFS). How did you get around this problem?
Oh I didn’t know it saves settings to the headset itself. That would come in handy.
Are there wireless version of modmic? I only saw wired ones which would kinda defeat my purpose of cutting the chord with my current setup.
I was looking into these but it mentions software a lot in the reviews as in you must use the software to ensure good audio quality. Is this true? How long have you had them?
I was also looking into the Logitech Astro A30
I don’t think it’s necessarily true anymore. Perhaps at one point in time but generally speaking, this isn’t the case anymore.
I’ve never heard of modmic. Will look into this. Thanks!
I’ve watch a few videos that compare a few headsets and for the “lower” audio and mic quality ones, they usually say that with their tweaking software you can make it a bit better. I was wondering about it since usually those type of programs are made for Windows only plus I don’t really think I want something that I must use software to make better. Long story short, thanks for the heads up!!
Do you really only get 15 hours of battery life?
Well she stopped using it so I deleted the instance (just too busy with small children). For the time that she was using it Bookstack seemed to have me her needs once a cohesive breakdown was established (translating Bookstack hierarchy and matching it up with her topics).
Following. Sounds interesting.
Lemme fix the headline for you.
HashiCorp joins the list of companies and software killed by IBM.
Not quiet. I was running gitea before so my mount was ./gitea:/data but since switching over to forgejo, I renamed my ./gitea directory to ./forgejo. Adjusted my compose file to have a mount of ./forgejo:/data.
Now inside of that renamed forgejo directory, there are a bunch of gitea references and even one more directory called gitea. When I migrated everything worked right away but since I wanted a cleaner transition, I renamed and switched all gitea references to forgejo but went I brought the stack back online, it went belly up.
As a troubleshooting step, I recreated my compose file and created a new empty ./forgejo on a different machine just to see what a new and fresh install would look like and the forgejo stack itself created all kinds of gitea references and gitea directory once I brought it up. So to fix my original deployment, I reverted all the references back from forgejo to gitea and everything worked again.
For fun, I went out to codeberg to look at the Dockerfile and saw that they had a bunch of gitea things within their own Dockerfile so nothing I can do for now
This looks interesting too
Love that username tho!! Yeah might just do RSS. I already run FreshRSS and it’s ability to filter stuff would probably come in handy too
This sounds like the simplest and most effective solution. Thanks!
Interesting… do you like this way more or the rss route more?
Was not aware of Diun, will check out!
After you mentioned it, I looked it up too and stumbled on a similar answer to that link. Thanks!
Simple solution. I like it! Although I think it will get lost in the sea of daily emails….
I was under the impression that Google retired the “app password” workflow and moved to Gmail API within Google Cloud. I have the API set up and that’s what I’m using in the Vikunja configs but like I mentioned in the post, at this point I don’t care if its Gmail or something else. I just need the email functionality to work so I will use whatever service works well with Vikunja.