• 2 Posts
  • 23 Comments
Joined 11 months ago
cake
Cake day: August 8th, 2023

help-circle



  • Yeah, I’m going with a tiny dedicated infra bootstrapping box with all the tools I’d need to bootstrap the main infrastructure.

    Using a hypervisor (proxmox in this case) I have some prebuilt vms’s and container images that I can use for the bootstrap instances so i’d not need to completely hand roll it again should it be needed.

    I’m looking at cloudinit scripts to see if that’s useful for this.

    I really like packer but I’m hesitant to rely on anything hashicorp until whatever they have going on shakes out.

    Then I just load up the bootstrap box with the main infra code and use woodpecker to deploy.

    Code and config backed up, also mirrored to newly created infra forgejo instances, just in case.

    If I can get a semi presentable cloud init based bootstrap system working nicely I’ll stick it somewhere people can get to it, in case it’s useful to someone else.







  • I mean, yes? That’s a good summation.

    The part where you get to call something “open source” by OSI standards (which I’m pretty sure is the accepted standard set) but only if you adhere to those standards.

    Don’t want to adhere, no problem, but nobody who does accept that standard will agree with you if you try and assign that label to something that doesn’t adhere, because that’s how commonly accepted standards work, socially.

    Want to make an “open source 2 : electric boogaloo” licence , still no problem.

    Want to try and get the existing open source standards changed, still good, difficult, but doable.

    Relevant to this discussion, trying to convince people that someone claiming something doesn’t adhere to the current, socially accepted open source standards, when anybody can go look those standards up and check, is the longest of shots.

    To address the bible example, plenty of variations exist, with smaller or larger deviations from each other, and they each have their own set of believers, some are even compatible with each other.

    Much like the “true” 1 open source licences and the other, “closely related, but not quite legit” 2 variations.

    1 As defined by the existing, community accepted standards set forth by the OSI

    2 Any other set of standards that isn’t compatible with 1

    edit: clarified that last sentence, it was borderline unparseable


  • “It’s not libre / free as in freedom so it’s wrong”.

    I think it’s more “It’s not libre / free as in freedom so it’s not open source, don’t pretend it is”.

    The “wrong” part would be derived from claiming its something that it isn’t to gain some advantage. I’m this case community contributions.

    There’s not a handwaving distinction between open source and not, there are pretty clear guidelines.




  • What problems are you struggling with specifically?

    You basically just pick a system, for example Forgejo - that’s comparable to a self-hosted github. Which also comes with github-like actions for CI/CD/Building

    I can deploy these by hand sure, but is that the only way ?

    Let’s assume forgejo and woodpecker.

    I’d need to spin up each service + the db (postgres probably) for each.

    Given i’d not have an SCM system or build pipelines until after they were deployed, am i just doing it by hand and hoping for the best or working with something like ansible, saving the scripts to a folder somewhere and manually running them myself?

    How about future maintenance or reproducibility?

    I’m fully capable of doing it by hand and not against it, just wasn’t sure if there was a commonly used bootstrapping mechanism i wasn’t aware of.