foreman VS aptly

I was confused because there is https://github.com/ddollar/foreman and https://github.com/theforeman/foreman

In case you're unable to use intune, a free approach might be https://theforeman.org/ That works well for provisioning baremetal windows (with discovery image or pxe boot) once you've set it up. It supports script access as well as a nice hierarchy for configurations. But it's really not as well documented as it should be.

I use the foreman with puppet and pxe/kickstart scripts to automate VM/baremetal provisioning etc.

It comes from the remote execution user snippet: https://github.com/theforeman/foreman/blob/develop/app/views/unattended/provisioning_templates/snippet/remote_execution_ssh_keys.erb

KVM & Foreman

Might want to look into https://theforeman.org/ if it's not too complex for you

The iso images are typically locked at a certain verison. The update repositories sounds like what you are looking for to cache updates. Look into theforeman.org and specifically the plugin Katello. This is an upstream for Red Hat's Satellite product. Another option would be Canonical's MAAS. Both of these options Sound like what you are headed for unless you really just mean synchronize into a folder and store the images in which case yeah.....just use rsync.

Alternatively, you can use Foreman+Katello, the upstream base of Satellite, to get started in learning the platform. You can also use the component matrix to use the versions that most closely resemble Satellite.

You should ask in the upstream bug tracker (is it this one? https://github.com/lubomir-brindza/nautilus-typeahead). First step is to get it to build for Debian manually/locally - i.e. patch the official nautilus Debian package. Then it's easy to setup a personal APT repository with aptly

Exactly what aptly is for. No idea about CentOS side, for that we just had rsync from official repo + some scripts

I'm not sure if this is an option, because it might break the isolation model, but you could setup repo mirrors in whatever tool of choice you like, but for Debian/Ubuntu, I think aptly is really featureful.

I know that it is not directly what you asked about, but without knowing how the signed debs are being used, I can say that if you were to use aptly to create an apt repo to house your debs to then be installed on whatever machines offline (assuming network connectivity, which may be an incorrect assumption), it requires you to sign a published repo/mirror, and also requires you to install and trust the key on any systems that you then want to use to install package unless you specifically use [trusted=yes] in the apt repo list file.

There's also Aptly but I've never used it. Looks neat, though.

I personally just mirror the packages for what ever I'm using with aptly and use the netinstall iso and point it to that local mirror. The netinstall iso will pull any needed updated from the repo.

Take a look at Aptly.

Aptly is a purpose-built DEB content management solution. Never used but I've heard good things.

The last time I got involved in repo/package management, we used aptly Later moved to Jfrog artifactory. The latter is very expensive.There is also pulp some said it is good, which I personally never managed in production environment, so I can't recommend for or against.