Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
What's the recommended development setup? #2207
Thanks for the great work on this project, we would love to get our development environment running smoother so we can contribute and take advantage of all the latest work that's been contributed.
We're having trouble figuring out the best development setup for talk, and it feels like we're missing something.
Using the -onbulid dockerfile, plugins reconcile, but then when talk starts in the container it complains that the custom plugins are missing. Also, debugging is much harder running via docker.
In previous issues I see references to people using git submodules along with the source version of talk... is this what you recommend? How do you manage what version of talk you're using alongside your plugins? Are people forking talk and locking the versions with that (and then have their plugins in a separate submodule repo)? We'd like to keep our plugins separate from talk, but we'd also only like to have to manage our plugin repo...
Ideally, Talk would be it's own npm package that our our project could depend on, seems like this would make version management, dockerization, and local development the easiest for us. Are there any plans to release talk as on npm package?