Make sure you watch the previous video in this series: Deploying a Project with Laravel Vapor.
Let's walk through how you can setup a custom domain and HTTPS certificate with Laravel Vapor.
Make sure you watch the previous video in this series: Deploying a Project with Laravel Vapor.
Let's walk through how you can setup a custom domain and HTTPS certificate with Laravel Vapor.
For further actions, you may consider blocking this person and/or reporting abuse
Chipm0nk -
Hanzla Baig -
Yannis Rizos -
Mike Young -
Top comments (1)
Another easy and affordable way to do this off the shelf is with approximated.app, which will handle all of this for you for around what you'd spend on a DIY server for it. Or sometimes a lot less, I've seen people use serverless for this in ways that racked up big bills.
Note: I'm the founder, so I am pretty biased, but I also have a lot of hands on experience with this.
My usual warning with completely DIYing this is that at some point something is going to go a bit haywire and break. It might be that a certificate authority revokes a bunch of domains suddenly due to some newfound vulnerability, or accidentally hitting CA rate limits (easy to do), or any other number of things that might not show up for months. Murphy's law usually means it'll happen while you're sleeping, and when custom domains stop working it can be a big deal. If you're ready and happy to deal with that when it happens, then I say go for it.
But when I talk to engineers in charge of 100k+ custom domains on DIY systems, they usually tell me it's the most stressful part of their job because issues can mean 100k+ of their best customers go offline. It's a bit like running an email server - go for it if you want to, but for most people it'll save you a fair bit of misery to let someone else handle it for you.