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.

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?

Actually pretty helpful!

Interesting tidbit about the performance. It has been a bit of challenge getting “up to speed” with Incus/LXD from a guide and walkthrough perspective. Although I do find their documentation pretty well organized and useful.

Well that’s kinda why I came here to the greater community as I wasn’t really sure if there would be any performance gains or other upsides I’m not aware of. Based on general feedback, it appears that there’s no clear upside to incus.

That’s another fair point. I do have a couple of pi’s collecting dust. As someone else stated, I need to consider the time it takes me to get up to speed with incus. Can you elaborate on your experience going “from 0 to hero” with incus? Just curious.

Fair point. I’m most familiar with docker and proxmox. Sorta doing it for educational purposes but I also have critical services (critical to me) running that must be available.

Strictly from a container perspective, wouldn’t this workflow create more overhead? For example, an incus cluster for me it would be Debian hosts (layer 1), incus (layer 2), lxd container (layer 3), docker (layer 4), app/service (layer 5). A Docker Swarm cluster (for me) would be Debian hosts (layer 1), docker (layer 2), app/service (layer 3).

Granted a docker swarm cluster would negate the possibility of VMs without having to install something else on the hosts but asking since I’m trying to keep my services in containers.

Very true! Thanks.

Haven’t really looked into Podman as I read somewhere (if I remember correctly) that it takes quite a bit of rewrite (from docker compose to podman). Again, might be speaking out of turn here.

Thank you I appreciate your input!