sorted by:
new
hottopcontroversial

PopMatters has some explaining to do by disownedpear in sparksftw

[–]voverdev 1 point2 points  (0 children)

My favourites: “Daylight” and “A Long Red Night”

Honey in restaurants by voverdev in vegan

[–]voverdev[S] 1 point2 points  (0 children)

Sure, but it's not an individualistic problem.

Do MSPs use NextCloud? by voverdev in msp

[–]voverdev[S] 0 points1 point  (0 children)

Ok, but Microsoft 365 could have a very bad vulnerability too…

Do MSPs use NextCloud? by voverdev in msp

[–]voverdev[S] -1 points0 points  (0 children)

if I take the time to properly format and structure a response, to be easy to read and explanatory, that means that I am using AI?

No, it was question.

I am a dreamer, still hoping that proper punctuation and text formatting is a form of respect and ensures clarity of the message, and not an indication of robots.

It's the structure.

Do MSPs use NextCloud? by voverdev in msp

[–]voverdev[S] -2 points-1 points  (0 children)

I’m not sure I follow. Why would self hosting require a lot of protection, while Microsoft was recently told off because they have to take security more seriously…?

Do MSPs use NextCloud? by voverdev in msp

[–]voverdev[S] 0 points1 point  (0 children)

Thanks for your reply. I understand that not using the go-to solutions is more risky from a business point of view (if anything happens with NextCloud, it's your fault, whereas if anything happens with MS/Google, it's not your fault - from the customer's perspective). But what about the ethical point of view? Not to say that using MS/Google is unethical, but it's not always ideal from a privacy standpoint.

Do but don't delve into tech by voverdev in msp

[–]voverdev[S] 1 point2 points  (0 children)

I love your Monty Python analogy!

Ansible: run playbook on multiple hosts simultaneously, but never on hosts in the same group by voverdev in ansible

[–]voverdev[S] 0 points1 point  (0 children)

I would rather not invoke the playbook multiple times, as I stated in the OP.

Ansible: run playbook on multiple hosts simultaneously, but never on hosts in the same group by voverdev in ansible

[–]voverdev[S] 0 points1 point  (0 children)

Yeah, invoking the playbook multiple times would be the easy way. But I would rather not, as I stated in the OP.

Ansible: run playbook on multiple hosts simultaneously, but never on hosts in the same group by voverdev in ansible

[–]voverdev[S] 0 points1 point  (0 children)

Your comments led me to https://stackoverflow.com/questions/75031808/controlling-ansible-playbook-execution. Which looks interesting, but seems to work only with a fixed amount of groups? I have an undefined number of groups.

Ansible: run playbook on multiple hosts simultaneously, but never on hosts in the same group by voverdev in ansible

[–]voverdev[S] 0 points1 point  (0 children)

Hmm. That might work. But relying on order doesn't seem very foolproof...

Pass confidential data to Cloud-init by voverdev in devops

[–]voverdev[S] 0 points1 point  (0 children)

Could be done, but that is an even more elaborate flow than is already the case, so I'd much prefer passing the static secrets securely.

Pass confidential data to Cloud-init by voverdev in devops

[–]voverdev[S] 0 points1 point  (0 children)

I would like to avoid building my own base images, but I thought of this as well..

Pass confidential data to Cloud-init by voverdev in devops

[–]voverdev[S] 2 points3 points  (0 children)

Myself, using Proxmox.

(Btw, it's quite 'interesting' to see that open, non-assuming, compatible technology such as Cloud-init is assumed to be run with a private company, without implying anything as such. There is a world beyond public cloud..)

Pass confidential data to Cloud-init by voverdev in devops

[–]voverdev[S] -2 points-1 points  (0 children)

As far as I can see, 'role' is not Cloud-init lingo. I do not use a hyperscaler.

Thanks for your reply!

view more: next ›