[Tracking] Ops and docs cleanups

Abierto
  • ¿Algo no está bien?
#403 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp, docker
Área
devops, documentation, testing

Línea de trabajo

Start with the three linked issues: #371 in the deploy repository, #357 for the documentation examples and exporter URI test, and #364 for backend-builder.md. Follow the listed order, beginning with the production endpoint and host settings; after redeploying, manually check whether the public Seq route is open without credentials. The tracker is done when all three issues are closed.

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

Descripción

tech-debt

Groups the small ops and docs cleanups that are not tied to the other trackers. None of them changes the API or the web app, so they do not depend on the monorepo move (#397).

Suggested order

  1. #371 — Correct the production OpenTelemetry__Endpoint and ALLOWED_HOSTS in nevridge/taskflow-deploy. The change is made in the deploy repo and picked up by a redeploy; it also records whether the public Seq route is open without credentials. Do this first, because it fixes production.
  2. #357 — Correct the OpenTelemetry endpoint examples in the docs to the base-URL form, and add an exporter URI test in this repo. Independent of #371.
  3. #364 — Fix backend-builder.md, which says to return ValidationProblem() while the controllers return BadRequest(errors). Independent. The agent files are merged in #400, so do it before then or carry the fix across.

Notes

  • #371 and #357 were split from one issue: #371 is the production fix and #357 the docs and test. Neither depends on the other.
  • #371 is made in nevridge/taskflow-deploy, so it has no PR in this repo and needs a manual check of the live site after the redeploy.

Done when

All three are closed.

Lenguaje dominante
C#
Estrellas
1
Forks
0
Merge medio
2 h 2 min
PR fusionados (30 d)
98

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nevridge/TaskFlow

Todos los issues de nevridge/TaskFlow

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.