Proxy follow-ups: dedicated bot token, Klipy key, stray DNS record #12
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
robocub/vommet#12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-ups from deploying the proxy (#1):
getStickerSetandgetFile(nevergetUpdates), so sharing is safe meanwhile, but a revoke of one shouldn't break the other.KLIPY_API_KEYto the env file and restart.proxy.nether.services.nether.im(CNAME to the tunnel).cloudflared tunnel route dnscreated it because its credentials are scoped to the nether.im zone; cloudflared can't delete records, so this needs the Cloudflare dashboard. Harmless meanwhile: no ingress rule matches it, so it returns 404.https://proxy.nether.im/healthzto the existing monitoring.Filed with LLM assistance. This is a fork-only issue; never refile it on Commet's tracker.