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.

Sign up for GitHub

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

Jump to bottom

Think about merging Titan into NBusy Server or reverse #95

Open
soygul opened this issue May 3, 2016 · 2 comments
Open

Think about merging Titan into NBusy Server or reverse #95

soygul opened this issue May 3, 2016 · 2 comments

Comments

@soygul
Copy link
Member

soygul commented May 3, 2016

Similar reasoning to https://github.com/centrifugal/centrifugo

In a nutshell this is a server running near your application and keeping lots of persistent Websocket or SockJS connections from your application clients (from web browsers or other environments). When some event happens you can broadcast it to all interested clients using Centrifugo API.
@soygul
Copy link
Member Author

soygul commented May 3, 2016 •
edited
Loading

If we keep separate repos, we'll have to keep separate Deploy to Heroku buttons as well as Docker images. It might be best to merge NBusy stuff into Titan and keep NBusy Server as a Titan config repo only. But even then, it might be still better to keep two copies of everything since having a docker image for NBusy with all-in-one with SDKs and clients is useful for people who want private deployment.

@soygul
Copy link
Member Author

soygul commented May 12, 2016

Also backport 'Getting Started' from KOAN.

@soygul soygul changed the title Think about merging Titan into NBusy or reverse Think about merging Titan into NBusy Server or reverse May 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@soygul