Static hosting for viggomeesters.com and small public web artifacts.
Tech Stack / Hosting & Automation
Hosting & Automation
The public delivery and automation layer behind viggomeesters.com: Vercel hosting, cron/watchers, webhooks, email, and Telegram integrations.
Current shape
Scheduled digests, monitors, and useful no-op-silent automation.
External-service actions stay evidence-backed and avoid irreversible side effects without approval.
Why this belongs in the stack
Hosting and automation explain how public pages, scheduled work, and integrations become durable outputs.
It matters when the public delivery route, cron/watchdog model, or external integration pattern changes.
What stays out
Keep providers and patterns public; never expose tokens, credentials, private IDs, or operational secrets.
Vault-private automations should be described at the pattern level, not as private run logs.
How it earns a place
This layer covers public delivery and scheduled/integration surfaces: hosting, domains, cron jobs, webhooks, email/Telegram bridges, and deployment glue.
This page is current when public URLs, scheduled jobs, and delivery assumptions can be verified without relying on memory or hidden dashboards.
It matters when the canonical domain, Vercel project, cron/digest behavior, webhook surface, or Telegram/email routing changes how public or scheduled work is delivered.
Concrete example
Vercel and the canonical domain are listed because public pages, redirects, sitemap URLs, and live verification all depend on that delivery surface staying aligned. The boundary is intentionally public-facing: delivery surfaces are named by role, not by private tokens, accounts, or dashboard internals.