Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Channel url#42

Answeredbyucswift
feadrick asked this question inQ&A
Sep 20, 2021· 1 comments· 2 replies
Discussion options

hi im writing this discussion ,so that i can have a clear picture on how to connect the bigboard with the resgrid core project.
there is a config that i'm not sure what value should i put .
i dont know which url i point for ChannelUrl config. i already setup the web and the api.
config

You must be logged in to vote

Hey@feadrick, the ChannelUrl is used for SignalR communications. This was the api url, but it's now being split into it's own project (https://github.com/Resgrid/Core/tree/master/Web/Resgrid.Web.Eventing) to allow for better control of multi server router, seeming it uses web sockets it needs have sticky routing whereas the API and Web projects should be load balanced differently.

At the moment that is not in the built release package, if you build the latest source you can deploy it as ASP.Net Core web app to Linux or Windows. I'm working publishing a docker image for it as well shortly. When you deploy that website it's the location you'll use for the ChannelUrl.

Replies: 1 comment 2 replies

Comment options

Hey@feadrick, the ChannelUrl is used for SignalR communications. This was the api url, but it's now being split into it's own project (https://github.com/Resgrid/Core/tree/master/Web/Resgrid.Web.Eventing) to allow for better control of multi server router, seeming it uses web sockets it needs have sticky routing whereas the API and Web projects should be load balanced differently.

At the moment that is not in the built release package, if you build the latest source you can deploy it as ASP.Net Core web app to Linux or Windows. I'm working publishing a docker image for it as well shortly. When you deploy that website it's the location you'll use for the ChannelUrl.

You must be logged in to vote
2 replies
@feadrick
Comment options

@ucswift
Comment options

Yes there will be 3 sites, now in total that need to be deployed, you've got the correct ones.

For the API and Web if your using load balancing, you can use round robin, least connections or another alog. For Eventing (webevent) you'll need to use some form of sticky session/ip hash to ensure websocket connections go to the same server.

Answer selected byfeadrick
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
2 participants
@feadrick@ucswift

[8]ページ先頭

©2009-2025 Movatter.jp