Albatrossity, to nature
@Albatrossity@lor.sh avatar

Bird of the Day — Rock Wren, Manhattan Kansas, yesterday
A bit far east of where this bird is typically found

technotim, to proxmox
@technotim@mastodon.social avatar

CI jobs for my ansible playbook have been broken for months due to some changes with GitHub Actions.
This took me down a rabbit hole to fix...

Long story short: Self-Hosted GitHub Actions runner, running on Proxmox with nested virtualization to run molecule tests using Vagrant against VirtualBox VMs. 🙃

gyptazy, to linux
@gyptazy@gyptazy.ch avatar

Today, someone reached out to me by email just to say "thank you" for my Box Collection with different types of including all general (, , , ,..) and (, , ...) distributions.

It was just an email, rather than an issue or bug and someone took some efforts to look up my mail and to write me. It made me very happy & we should much more honour the work of others! It reminded me of how much we now take software for granted in our daily life. Things we do and handle our daily business... Even if we don't donate anything or only small amounts, we should always show respect for the time and effort of the author and maintainer. Even a small personalized email can bring great joy :)

joepferguson, to Laravel
@joepferguson@phpc.social avatar

Homestead v15.0.0 has been released https://github.com/laravel/homestead/releases

DigitalKrampus, to Ansible
@DigitalKrampus@geekdom.social avatar

Just over here converting my Raspberry Pi bringup script to an ansible playbook. I am verifying it works with Vagrant+VirtualBox VMs before I try it on any hardware.

I learned all of this from Jeff Geerling's amazing book, Ansible for DevOps, ISBN 978-0986393426 if you want to check it out.

Jeff is on Mastadon @geerlingguy



joepferguson, to random
@joepferguson@phpc.social avatar

Building boxes like it's still mainstream.

mark, to mastodon
@mark@mastodon.fixermark.com avatar

Is there anywhere that devs do live chat?

I'm working on getting the dev environment set up and am having a bear of a time understanding the documented steps. I feel like these questions would be easy to answer if I could chat with someone who succeeded.

fosslife, to opensource
@fosslife@fosstodon.org avatar

HashiCorp has dropped the open source @mozilla Public License v2.0 in favor of the source-available Business Source License (BSL) v1.1 https://www.fosslife.org/hashicorp-switches-source-available-license

fwilhe, to random
@fwilhe@social.tchncs.de avatar

It came to my mind today that maybe #lima https://github.com/lima-vm/lima can replace some of my #vagrant use-cases. Sure, it does not have the same focus, but since I anyway had been using vagrant with libvirt (no vmware or vbox), it's running qemu anyway. Getting a basic box running seems easy enough, but the lima cli seems a bit counter intuitive to me. Difference seems to be that vagrant has more rules on how the box is built while lima seems to use cloud-init for user setup. Less lock-in, I guess.

fwilhe, to fedora
@fwilhe@social.tchncs.de avatar

Any insights how and will handle the license change in ? I don't hope they would include BSL code in the distro, so… freeze the version of vagrant before the license change? Any prominent OSS fork already?

RyunoKi, to random
@RyunoKi@layer8.space avatar

It's good to know that actually works.

But does it have to be on ? 🫤

And only because I forgot to comment in the provision against the VM.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • rosin
  • thenastyranch
  • ethstaker
  • DreamBathrooms
  • osvaldo12
  • magazineikmin
  • tacticalgear
  • Youngstown
  • everett
  • mdbf
  • slotface
  • ngwrru68w68
  • kavyap
  • provamag3
  • Durango
  • InstantRegret
  • GTA5RPClips
  • tester
  • cubers
  • cisconetworking
  • normalnudes
  • khanakhh
  • modclub
  • anitta
  • Leos
  • megavids
  • lostlight
  • All magazines