Multi-stage Dockerfile for spee.ch #74
No reviewers
Labels
No labels
Accepted
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
help wanted
icebox
In Review
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-docker#74
Loading…
Reference in a new issue
No description provided.
Delete branch "EnigmaCurry/k8s-lbry-speech"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This creates a spee.ch container.
Spee.ch imports its configuration from its own bundle. This means that we need to have the whole configuration at bundle time. Since we don't have the configuration until runtime, this force us to create the bundle at runtime.
Ideally, the final image would not even have npm in it. Simply copying the node_modules from the
prep
stage over to theapp
stage, and mounting the configuration files should be sufficient. However, this would require a change to how spee.ch imports its configuration.For now, this works with the way spee.ch currently works.
This should not run as root.
This is a good baseline and will function however I would not consider it stable or up to spec with the other containers. I do not recommend using this in production yet but I'll consider it merge-able for now to help along the process of other things like the K8's stuff in #71
This should have it's own README.md to explain the state that this container is in and it's current goals.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.