در حال بارگذاری ...

Configuring Health Check URL0:31

status code? So let me show you how that works. Within my project settings, I can actually set a health check URL right here. Now, we've been using this Forge server, so let's continue to use that. So I'm going to grab that IP address, since we don't have a domain associated with this server yet, and let's add that as our health check URL. All right, and we'll head back to this project. Now, you can see that this is all green check marks because, of course, our site, if we hit it, is working correctly. All right, so let's change our code to throw an exception on that default route and

Deploying a Broken Build0:58

if we hit it, is working correctly. All right, so let's change our code to throw an Exception on that default route and deploy something that's actually broken. Within Sublime Text, let's just throw new Exception. Everything is broken. All right, and let's deploy this code. And we'll say break application. All right, so this should deploy automatically since we do have our githook set up for this project, and there it goes. So our code is deploying. We can, of course, see the typical deployment process that we would expect. It's pulling down our code.

Rollback via Redeploy1:32

So our code is deploying. We can, of course, see the typical deployment process that we would expect. It's pulling down our code and installing our dependencies, and soon it will activate the new release, which our code is not broken yet since this is zero downtime. Okay, the release is activated. Now, if I go to my project, you'll see that I have all red Xs telling me that my application is actually down after this deployment. So let's roll back to our previous deployment, which we know was working. I can do that using this redeploy button right here, and let's confirm that redeployment. All right, so we should see the new deploy, and there it goes. It's deploying.

دوست دارید گاهی خبرهای Laracasts را ایمیل کنیم؟