Rename this repo (again)? #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I wonder if this ought to be 'incus-infra' (or 'infra-incus', and rename 'core-infra' to 'infra-core' as well)? The long-term intention is not to be scaleway specific, and the 'base VM' stuff (incusos and nixos) seems to be slowly migrating away to vm-base-images ..
Hmm, that seems like it might make sense. I'd thought "scaleway-images" on the assumption that we'd end up with a fork to "fooprovider-images" containing all the variation required to port the build process to something else.
Perhaps though, and especially with nix (where it doesn't seem to be a commonly-templated option), the better approach might be to have a "base" that can be used in several contexts.
Something like this maybe?
base-images repo, creates:
Goal of the base is to be minimal, but with easy hooks to make it role-specific - "cloud-init" is what comes to mind, just 'cos of familiarity. Basically anything that would allow applying more config without needing to rebuild would work though.
incus-images (or whatever) repo, creates:
Goal of these is speeding up startup, at the expense of a longer build. Potentially, this could be done by doing a "the deploy process builds one and makes it a template" thing?