Skip to content

Conversation

@EnigmaCurry
Copy link
Collaborator

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 the app 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.

@EnigmaCurry
Copy link
Collaborator Author

This should not run as root.

Copy link
Collaborator

@Leopere Leopere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@lbry-bot lbry-bot assigned Leopere and unassigned Leopere Jun 14, 2019
@Leopere Leopere self-requested a review June 14, 2019 21:20
@lbry-bot lbry-bot assigned Leopere and unassigned Leopere Jun 14, 2019
Copy link
Collaborator

@Leopere Leopere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should have it's own README.md to explain the state that this container is in and it's current goals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants