Add health endpoints and Uptime Kuma monitoring - #689
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8b0ab3fbf5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| }, | ||
| "ConnectionStrings": { | ||
| "MerchantFileProcessor": "merchant-file-processor.db" | ||
| "MerchantFileProcessor": "" |
There was a problem hiding this comment.
When no machine-local override or environment variable has been provisioned, this empty value makes every fresh or local installation terminate in Program.cs at the explicit string.IsNullOrWhiteSpace(configuredConnectionString) check, before the health endpoint can start. The staging and production deployment jobs in .github/workflows/pushtomain.yml and .github/workflows/createrelease.yml only unpack and start the service and do not inject this setting, whereas the previous merchant-file-processor.db default allowed such installations to boot; retain a usable default or have those deployment paths supply the required value.
Useful? React with 👍 / 👎.
Summary
Testing
Not run (not requested)