giacomo

joined 1 year ago
[–] giacomo@lemmy.world 34 points 1 year ago (5 children)

"home grown" Ubuntu spin, got it

[–] giacomo@lemmy.world 1 points 1 year ago (1 children)

Very neat! Definitely a project I'd like to follow.

Makes me wonder if something similar could be implemented using frr, ospf, and ansible.

[–] giacomo@lemmy.world 4 points 1 year ago

Always backup.

Everytime I do anything with filesystems or partitions, something goes wrong and I end up having to utilize the backup.

That's not to say btrfs-convert won't work; I have no idea as I've never used it. Maybe it will work perfectly, but at least you'll have a backup for a fresh fs if it doesn't.

[–] giacomo@lemmy.world 1 points 1 year ago

Give it time

[–] giacomo@lemmy.world 7 points 1 year ago

It looks like an upsidedown Xbox controller with a screen in the middle.

[–] giacomo@lemmy.world 1 points 1 year ago

Nice! Yeah, literally minutes, haha. I knew someone had to have already done this.

[–] giacomo@lemmy.world 1 points 1 year ago

Great... For chatgpt...

[–] giacomo@lemmy.world -1 points 1 year ago

Great... For chatgpt...

[–] giacomo@lemmy.world 0 points 1 year ago

I'm sure someone has written a script to convert docker run commands to compose files.

I am usually customizing variables and tend to use compose for anything I am planning on running in "production". I'll use run if it's a temporary or on-demand use container.

It's not really that much effort to write a compose file with the variables from a run command, but you do have to keep an eye on formatting.

[–] giacomo@lemmy.world 1 points 1 year ago (5 children)

I'm sure someone has written a script to convert docker run commands to compose files.

I am usually customizing variables and tend to use compose for anything I am planning on running in "production". I'll use run if it's a temporary or on-demand use container.

It's not really that much effort to write a compose file with the variables from a run command, but you do have to keep an eye on formatting.

view more: next ›