Skip to content

hosting for reform.debian.net

Please provide the specifications that you require:

  • CPU: single and slow
  • RAM: 2GB
  • Disk space: 20G
  • Desired hostname: reform.debian.net
  • Public SSH key: ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA2qPmP0371lRVCtlOHTB8tWkMmZP+hQ8fy8aJNELR1tRUPxIwSUL2u/0rWxrDZsgHC+Q+IWYWhPpBAD80otdOwcwDeeHSCfKPLwoTujGkHw6BZg+sgg0ejtJYsRmBJvTEFPKyNmEis3gYfH/ThztuPJj5c2jaUbfrSTnQnMNta48l91u5nIDKC8AToareeameuiCKeL36GSs/Hxi5Cwrni58eXXXz6hrEC6WSb8652e0m05v1/QXliyXjs1D1wnwu/Gqw0LpKGSRgRcV+ivjqrFWCBHLpiFVe0He0l1yfLMY7+tPIBSgGSucRqbhBa5hvPxQ2xas1uQaLtKZaNdHi/w== josch@josch

Please provide details as applicable:

Hi,

I just found out that there exists https://raspi.debian.net/ with downloadable bootable images for all raspberry pi platforms.

I want to provide the same thing for the MNT Reform range of open source hardware products.

I have created and been maintaining for over a year a script that builds these images already and I'd like to make this a debian.net service such that signed images and packages can be provided by Debian-run infrastructure.

No backups are needed because the script is able to re-create all artifacts from scratch using the Debian archive.

The machine would be cross-building the Debian linux kernel with reform patches on top but this can be slow and on single-core as this would only be necessary for every stable update that changes src:linux.

Given the patched packages, it would then build the bootable disk image using a wrapper around mmdebstrap and serve those via http for all available MNT Reform platforms as it is done on raspi.debian.net for all Raspberry PI boards.

Will you be adding this service to https://wiki.debian.org/Services along with a service page under that name space? -- Yes, absolutely.

Check-list for Debian.Net Team

  • Select an appropriate platform for the request.
  • Spin up a VM in the appropriate platform.
  • Hetzner Only: Add IPv4 and IPv6 reverse-DNS entries.
  • Add the Debian.Net Team's SSH keys to root's authorized_keys.
  • Set PasswordAuthentication no in sshd_config, restart sshd.
  • Add an account for the requester adduser --disabled-password USER.
  • Grant sudo access to the requester adduser USER sudo.
  • Unset the user's password, so they can set it themselves: passwd -d USER
  • Add the requester's SSH keys to their account's authorized_keys.
  • Provide IPv4 and IPv6 addresses in a comment, so the requester can create DNS records.
  • Add the instance to the infrastructure repo
Edited by Stefano Rivera