[Tracking] Ops and docs cleanups

Open
  • Is something wrong?
#403 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, docker
Domain
devops, documentation, testing

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
C#
Stars
1
Forks
0
Avg merge
2h 2m
Merged PRs (30d)
98

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nevridge/TaskFlow

All issues in nevridge/TaskFlow

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.