Using Docker for Wekan development
See original GitHub issueThis is a follow-on from discussion under #874.
I’d like to work on Wekan while running the node+meteor+wekan stack in a Docker environment, rather than running it directly on my host. At the moment, the Docker configs included in this repo, in wekan-launchpad, and in the wiki as well as elsewhere all focus on using Docker for production use. This means that they are optimised to minimise the resulting image size, rather than the reload time of the system during development, which can be rather long esp. due to re-fetching the meteor package dependencies on every build.
To support this use case, the Docker environment would need to be set up such that changes to the source code don’t require a rebuild of the images, and with the source code editable on the host while still able to have changes to it trigger an update of meteor run
in the container.
Is this something other people would also be interested in? It would help in resolving the rather specific version requirements, as well as otherwise setting up the environment in a controlled fashion to make it as easy as possible to start hacking on Wekan. Also, should this environment be included in Wekan core, or hosted in a separate repo?
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (5 by maintainers)
Top GitHub Comments
@eemeli
Thanks! I added it to changelog, readme and wiki: https://github.com/wekan/wekan/wiki/Developer-Documentation
sorry for the delay in replying this issue just got away from me.