Playing
05. DNS records for the WebSocket subdomain
Transcript
00:00
Once you've toggled Reverb on your server and it's technically running, we need to point our DNS for that subdomain to our primary domain. So we're going to head back over to wherever we're managing our DNS. And we're going to add a CNAME record in here now.
00:14
So let's add a CNAME record for the WS subdomain. And of course, change that if you switch that up. And for the target here, I'm just going to set that to app, which is just going to go through to the root domain.
00:26
Let's go ahead and save this out. And we'll wait for that to finish. We'll also, for the purpose of this, just get rid of the proxy through Cloudflare and just use that as DNS only.
00:35
Once you've done this, you'll want to verify that the CNAME has been hooked up properly. So we could just go ahead and ping this. Let's ping ws.alex.gs and just wait for that to finish.
00:45
And we should see this come through. Once we've done that, we know that the CNAME has been hooked up correctly to point through to our server. Just verify that the IP address is the same here in case you have
00:55
any old records lying around. And that is it. We've hooked this up now, and we now have that subdomain ready to handle our WebSocket connections.
7 episodes• 16 mins•2 months ago
Overview
So you’ve built a realtime application. Now it’s time to deploy it.
Laravel Forge makes it incredibly easy to toggle Reverb, which configures your server for you and sets up (nearly) everything you need to broadcast and listen for events.
In this course, we’ll cover every step needed to get an local example application deployed to a production server, with a separate subdomain reserved for your Reverb connections.
Alex Garrett-Smith
Hey, I'm the founder of Codecourse!
Comments
No comments, yet. Be the first to leave a comment.