Skip to content

feat: default config fallback + Railway one-click deploy#23

Merged
christianromeni merged 1 commit intomainfrom
feat/one-click-deploy
Mar 24, 2026
Merged

feat: default config fallback + Railway one-click deploy#23
christianromeni merged 1 commit intomainfrom
feat/one-click-deploy

Conversation

@christianromeni
Copy link
Copy Markdown
Contributor

Summary

  • VoidLLM now starts with built-in defaults when no config file is found, reading VOIDLLM_ENCRYPTION_KEY, VOIDLLM_ADMIN_KEY, and VOIDLLM_LICENSE from environment variables
  • Removes hardcoded --config CMD from Dockerfile — auto-discovery finds mounted configs, falls back to defaults
  • Adds Railway one-click deploy button to README

Test plan

  • go test ./internal/config/... -race passes (3 new test cases for loadDefaults)
  • VOIDLLM_ENCRYPTION_KEY=test go run ./cmd/voidllm starts without config file
  • go run ./cmd/voidllm without env vars fails with clear settings.encryption_key error
  • Existing docker-compose with mounted config still works

VoidLLM now starts with built-in defaults when no config file is found,
reading VOIDLLM_ENCRYPTION_KEY, VOIDLLM_ADMIN_KEY, and VOIDLLM_LICENSE
from environment variables. This enables zero-config deploys on Railway
and bare docker run with just ENV vars.

- Add loadDefaults() fallback in config.Load()
- Remove hardcoded --config CMD from Dockerfile
- Add railway.json for one-click Railway deploy
- Add Deploy on Railway button to README
@christianromeni christianromeni merged commit 3d878c5 into main Mar 24, 2026
5 checks passed
@christianromeni christianromeni deleted the feat/one-click-deploy branch March 24, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant