Skip to content
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

What's the recommended development setup? #2207

dudeman opened this Issue Feb 26, 2019 · 0 comments


None yet
1 participant
Copy link

dudeman commented Feb 26, 2019

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?

@dudeman dudeman closed this Mar 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.