[Feature Request] Single Docker image
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I came here to ask about single Docker image for the whole Drift project.
Why:
Current Drift's Docker setup requires two separate instances - one for frontend and one for backend. It's quite good option for development team because debugging can be much easier. But for "casual user" there is no need to expose this detail about split of the project. It will be much easier, for everyone who wants to just host it, if there is only one Docker image which contains backend and frontend.
What I need:
An option to run only one Docker image instead of two separate ones.
I know that you @MaxLeiter will be busy with porting Drift to Next 13, so I can try to make a "monolith" Docker image in my spare time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing frontend and backend Docker setup and how the two instances are launched. Define a single-image approach that preserves the current project behavior and verify that the whole Drift project can be hosted with one image instead of separate frontend and backend images.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nextjs, react, typescript
- Domain
- devops, full-stack, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100