chore: remove .bak files, add requirements.txt, Dockerfile, and .env.example#1
Merged
MoltyCel merged 2 commits intoApr 2, 2026
Merged
Conversation
…example Remove 11 backup files that contained outdated code including the old hardcoded API key. Add .bak* to .gitignore to prevent future commits. Add requirements.txt documenting all Python dependencies, Dockerfile for containerized deployment, .dockerignore for clean builds, and .env.example documenting all required and optional environment variables. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
…b.sql Found during local testing with docker-compose: - apscheduler is imported at startup but was missing from requirements.txt - DB host was hardcoded to localhost, now reads DB_HOST env var - init_db.sql schema was outdated — updated to match current codebase columns (agent_type, base_tx_hash, erc8004_agent_id, wallet fields, from_did/to_did in ratings, credentials table, api_keys, etc.) Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Contributor
Author
This was referenced Apr 1, 2026
Owner
|
Good cleanup — all 11 .bak files confirmed safe to remove, no active code affected. One note on init_db.sql: the updated schema doesn't yet include columns added this week (public_key_hex, key_anchor_tx, key_anchor_block, swarm_seeds, trust_score_cache, swarm_graph). This is fine since init_db.sql is for fresh dev/test environments only — production DB was migrated separately. Worth aligning in a follow-up PR so new dev setups match production schema. requirements.txt: consider pinning exact versions (== instead of >=) for better reproducibility in CI. Merging now. Thanks Harald. |
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
.bakfiles containing outdated code (including the old hardcoded API keymt_test_key_2026)*.bak*to.gitignoreto prevent future backup file commitsrequirements.txtdocumenting all Python dependenciesDockerfilefor containerized deployment (Python 3.12-slim, uvicorn).dockerignorefor clean Docker builds.env.exampledocumenting all required and optional environment variablesMotivation
The
.bakfiles contained 6,900+ lines of dead code, including security-sensitive defaults from before the API key hardcoding was fixed. The project had no dependency documentation or container support, making it difficult for new contributors to set up a dev environment.Test plan
docker build -t moltrust-api .succeedspip install -r requirements.txtinstalls all needed dependencies🤖 Generated with Claude Code