coder / coder/code-server

Create a public APT repository for `code-server`

Abierto
#7,780 1 comentario 2 reacciones 0 asignados Ver en GitHub
code-server Improvement
Lenguaje dominante
TypeScript
Estrellas
79.3k
Forks
6.8k
Merge medio
2 d 6 h
PR fusionados (30 d)
41

Descripción

The `.deb` packages for `code-server` are super handy, but users still have to manually update them by downloading and installing the fresh package for each release. It would be really nice to have an APT repository so this was handled automatically. (See #2600 and #2582 for some earlier discussion of the topic.)

Since the `.deb` packages are already being built, this should be quite easy to do with a host like [Buildkite Package Registry](https://buildkite.com/platform/package-registries/) (fka PackageCloud), which has a "free for open source" option. To test this out, I set up a registry with a personal fork, and it seems to work exactly as expected: https://buildkite.com/organizations/andrew-gainer/packages/registries/code-server/packages/019dee3f-dd00-7900-bf17-b6a98bedf40c

I'd be happy to help set this up for the main `coder/code-server` repo, but it's not something that can be done with just a pull request. The steps required would be:
* Set up a Buildkite organization for Coder with the "free for open source" plan and connect it to the `coder/code-server` repo
* Mint a Buildkite API token and add it as a repo secret
* Add code to the `release.yaml` GitHub action to upload the `.deb` archives to Buildkite
* Update the [coder.com docs](https://coder.com/docs/code-server/install) to reference the new repo

If y'all are interested in getting this set up, I'm happy to help!

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Revisa la GitHub Action release.yaml existente y la configuración vinculada de Buildkite Package Registry, y después inspecciona la documentación de instalación de coder.com. Determina cómo se deberían subir los archivos .deb existentes y cómo se configurarían el repositorio y el API token; se considera terminado cuando las releases se publiquen en el repositorio APT y la documentación haga referencia a él.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
github-actions, yaml
Área
devops, documentation, release
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
38/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.