Hahahahaha didn’t even realize the typo. But yea I made them maaaaad!
Thank you! Easy fix
Upsetting the mirrors did it for me.
Yup! Working peachy now
Did the trick for me too
How does this happen? This is my first EOS system. Ever since I finished up the setup and customization, I’ve not changed anything outside of updating it and using the system… I guess I’m just trying to understand the why
I will give this a shot when I get back home and report back
Okay I’ll give this a try when I got back to the house.
Done. I uploaded a screenshot
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?
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).
Something else to check is your infill percentage. Make sure you don’t have it at 100% (unless you absolutely need to build something completely solid). Another thing to check is your print speed. Too low and it will take a decade to print something simple. Too fast and it cause your print to fail. At this point we will all be throwing spaghetti against the wall. Can you share a screenshot of your settings?
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?
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.