Promote Docker-based deployments; Replace SIdekiq#3999
Open
Promote Docker-based deployments; Replace SIdekiq#3999
Conversation
Contributor
timfrazee
commented
Feb 17, 2026
timfrazee
commented
- Promotes Docker as a primary production deployment mechanism
- Adds production-ready Dockerfiles for client and API
- Updates client to operate in Docker natively
- Minor changes to improve passing configuration from environment (reducing need for local config files)
- Expand S3 integration as full replacement for local attachment storage
- Promotes Docker as a primary development infrastructure (using Docker Compose)
- This was already the case for the API, but now includes the client
- Removes Sidekiq and Zhong, replaces with database-backed Good Job
- Makes API and client applications ready for deployment in Digital Ocean App Platform
- Metadown is often failing to load. Should find an alternative, or fork
- This must be re-added, but has to support internal hostname
- Fetching client public IP is still disabled. This will need to be conditionally supported.
- Improves passing bucket/prefix args - Makes all ACLs public; this may need to be adjusted later
- This should be isolated to just the necessary routes
- Moved from secrets to env
- Migration enqueued a job, but runs before good_jobs table is created
The proxy was failing with 403 errors when proxying to HTTPS targets because the Host header wasn't being rewritten. Added changeOrigin: true to fix this. Also added optional debug logging via PROXY_DEBUG env var.
- Replaces Redis with SolidCache / ActiveRecord tables as appropriate
- Creates API and client images and pushes to both GHCR and DOCR
timfrazee
force-pushed
the
docker/digital-ocean
branch
from
213a209 to
240ae2b
Compare
- Patches Ruby gems nokogiri and job-iteration - Patches NPM packages form-data and sha.js
timfrazee
force-pushed
the
docker/digital-ocean
branch
from
9e0e44d to
c762947
Compare
Allows it to be available to API instances proxied behind /api
Addresses an issue where requests routed through reverse proxies / load balancers were being aggressively throttled due to obscured client IP addresses
Addresses an issue where proxies using non-standard forwarding headers were being rate limited on the proxy's IP
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
2 participants
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.