Repository navigation
feat: Add personal deployment option with protected volumes and separate ports - #16
Merged
Merged
Conversation
Add separate "personal" Docker environment for persistent data alongside development. Key changes: - Add docker-compose.personal.yml with different ports (18000, 18001, 14000, 16006) to run simultaneously with dev - Use external Docker volumes that survive docker compose down -v for data protection - Add Makefile targets: personal_setup, personal_up, personal_down, personal_backup, personal_restore, personal_migrate, personal_litellm_setup, client_personal - Make setup_litellm_keys.sh configurable via ENV_FILE, LITELLM_PORT, KEY_PREFIX environment variables - Add alembic.ini and alembic/ to Dockerfile for in-container migrations - Run reasoning_migrate inside container for consistency with personal environment - Add .env.personal.example template and README_USAGE.md documentation - Share docker-compose.override.yml between dev and personal for filesystem volume mounts Also: - Remove unused example config files (demo_basic, demo_complete, demo_raw_api) - Add .env.personal to .gitignore
shane-kercheval
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a "personal" deployment option that runs alongside the development environment, using separate ports and external Docker volumes that survive
docker compose down -vto protect persistent data.Changes
docker-compose.personal.ymlwith separate port mappings (18000, 18001, 14000, 16006) and external volumes.env.personal.exampletemplate with configuration for the personal environmentREADME_USAGE.mdwith comprehensive documentation for personal deployment setup and usageMakefilewith personal deployment commands (personal_up,personal_down,personal_backup,personal_restore,personal_migrate, etc.)scripts/setup_personal.shto create external Docker volumesscripts/setup_litellm_keys.shto support both dev and personal environments viaENV_FILE,LITELLM_PORT, andKEY_PREFIXvariablesprompts/.gitkeepfor default prompts directoryreasoning_migratecommand to run inside the Docker containerexamples/configs/Testing
Manual testing of personal deployment workflow including volume creation, service startup, and backup/restore commands.
Impact
No breaking changes. Development environment continues to work as before. Personal deployment is opt-in and uses completely separate configuration, ports, and volumes.