chore(deploy): trim to a Docker-only bundle for public release#11
Merged
Conversation
Remove Paramify-internal / heavy deployment direction from deploy/ ahead of the public release: - Delete the entire deploy/k8s/ tree — the Kubernetes CronJob manifests + local→EKS walkthrough, plus the multi-account hub-and-spoke bundle (Terraform, AWS_MULTI_ACCOUNT.md, aws-config.configmap.yaml). We don't want to prescribe that level of deployment. The Kubernetes *fetchers* (fetchers/k8s/) are untouched, and the Dockerfile keeps kubectl since those fetchers need it. - Fix an internal leak: entrypoint.sh defaulted uploads to stage.paramify.com; now app.paramify.com (matching the uploader's own production default). Same correction in .env.example and a "defaults to stage" note in deploy/README.md. - deploy/README.md is now a clean Docker/compose guide: dropped the k8s table row, the ConfigMap aside, and the K8s-CronJob production note; genericized the ECS/EKS secret-injection option. - Scrub the stale deploy/k8s/ link + Kubernetes/multi-account prose from docs/design.md, and "Docker or Kubernetes" -> "Docker" in the root README. No broken links remain to the deleted paths. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
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
1 participant
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.
Cleans up
deploy/ahead of the public release — removes Paramify-internal and heavy-handed deployment direction, keeping a simple Docker/compose path.Removed
deploy/k8s/tree — the KubernetesCronJobmanifests + local→EKS walkthrough, plus the multi-account hub-and-spoke bundle (Terraform IAM module,AWS_MULTI_ACCOUNT.md,aws-config.configmap.yaml). We don't want to prescribe that level of deployment in the public repo. (~900 lines.)Fixed (internal leak)
entrypoint.shdefaulted uploads tostage.paramify.com→ nowapp.paramify.com(matching the uploader's own production default). Same correction in.env.exampleand thedeploy/README.mdwalkthrough. Nostage.paramifyreference remains anywhere.Scrubbed references
deploy/README.md→ a clean Docker/compose guide: dropped thek8s/table row, the ConfigMap aside, and the "prefer K8s CronJobs" production note; genericized the ECS/EKS-specific secret-injection option.docs/design.md— removed the staledeploy/k8s/link + Kubernetes/multi-account deployment prose.README.md— "running on a schedule in Docker or Kubernetes" → "in Docker."Kept intentionally
kubectlin theDockerfile— it's a runtime dependency of the Kubernetes fetchers (fetchers/k8s/), not deployment tooling. The evidence fetchers are untouched.Verified: no broken links to any deleted path remain in the repo.
🤖 Generated with Claude Code