Support
Running Envious in production and need a hand? Reach out — include your version
(envious version / /api/version), platform, and the relevant log lines.
Production support
Deployment help, upgrades, backup strategy, log-pipeline wiring, and bug triage for production installs.
support@marcuwynu.spaceSupport channels
| Channel | Best for | Where |
|---|---|---|
| Production issues, private deployment details | support@marcuwynu.space | |
| GitHub Issues | Bug reports and feature requests | marcuwynu23/envious issues |
| Documentation | Self-serve setup and operations | Documentation |
What to include
- Version — output of
envious versionandGET /api/version. - Platform — OS/arch, binary vs Docker image tag.
- What happened — expected vs actual, steps to reproduce.
- Logs — relevant JSON log lines (they carry
request_idfor correlation). - Never send secrets — redact API keys,
ENCRYPTION_KEY, and variable values.
Quick answers
I lost the admin API key
The server stores only a bcrypt hash, so it cannot be recovered. If you kept envious_api_key.txt (written next to the database on first run), use that — otherwise reset the stored hash directly in SQLite.
The CLI says 401
Re-run login with the right --api-base and key, then check the server audit trail for auth.login_failed entries.
How do I back up?
Copy the SQLite file at DATABASE_PATH. That single file holds apps, environments, variables, and the audit trail. On Postgres, use pg_dump instead — see the User Guide.