-
-
Notifications
You must be signed in to change notification settings - Fork 10
Docker Image #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Image #5
Conversation
…ete publish workflow
…oper installation of dependencies and setting NODE_ENV
…on commands for improved efficiency
|
NVM. There is a lot more todo for container deployment. The db is not persistent, because not mounted. Post processor should be configurable by config file. If i find more time i will update it and provide a propper deployment, because i need to understand the architecture and implementation. |
…or improved organization
Mounting is already working with the current image. Check the readme for paths. |
|
This is done :) @derekantrican feel free to refactor, merge and use it. Have fun! FYI: I would recommend to remove the cmd post processor. It allows remote code execution as root. I will remove it in my fork. |
|
This is already being worked on in #3 . I'll probably compare this PR against that one, but probably end up closing this one |
|
Feel free to close it |
…and add Docker usage details
Hi, it works for me inside my k3s cluster. I am gitlab ci dude, so optimize the workflow or the image creation.