Possible to re-deploy?


May 29th, 2023 02:39 PM

Hey everyone! I'm having real issues with my initial deployment and I'm wondering if it's possible to re do it without starting over?

I don't know if this was part of the problem or not but I made a bunch of changes on my local environment and was pushing to my github repository before finally deploying. I've had so many issues with failed deployments since but I'd really like to keep the changes if possible.

I tried to copy the project into a new folder in Visual Studio Code but when I went to deploy it came up with a bunch of comments from DigitalOcean instead.

Hope someone can help!


May 30th, 2023 12:22 AM

Hey Trav 👋

Yes absolutely, it should be possible to sort out the problems and deploy as normal.

To do that you would need to share more information:

  • What are the exact errors that you are seeing?
  • Are you deploying to the DigitalOcean App Platform or is it just a Linux server?
  • Did you initially deploy your project successfully or was it failing on the very first try?

The more information that you can share the better.




May 30th, 2023 01:01 AM

Hey! Thanks for that. I'm deploying to the App Platform. Right now I'm getting a HTTP ERROR 504 This Page Isn't Working error but that's because it's failing on migrating I think.

I've put the errors I've been getting below but they really didn't give me much information. I've submitted a ticket with DO but they've just kept saying they'll get back to me.

Initially it was fine but then I realised that when I was making changes in the dev environment on my local machine, every time I pushed a change it would strip out all the assets. I tried to link it with a Space but that never worked either and I'm not sure if it was because of the settings but I got the info and put it in the web and migrate env variables (individually and together to see if that would work) in DO but it never connected so I kept losing the images.

These were the settings I used for the DO Space: DO_SPACES true DO_SPACES_ENDPOINT https://URLREMOVED.syd1.digitaloceanspaces.com DO_SPACES_REGION syd1 DO_SPACES_BUCKET BUCKETNAME DO_SPACES_KEY XXXXXX - removed DO_SPACES_SECRET XXXXX - removed

I thought I had a great setup initially with the first few changes and was really happy but then when I noticed all the images gone I started googling and now I don't really know where I'm at. It's not deploying at all anymore. Let me know if you need any other info. I feel like a huge newb now and think I messed it up. I've changed the names and keys here obviously but checked to make sure they were ok.

Has anyone else had this issue? Is this super simple and I've just messed it up?

Errors I got: App Platform pushed zero-downtime, automatic rollback to previous deployment failed during deploy phase Rollback Unavailable

deployment failed during deploy phase Trigger: User configured web settings 05:09:48 AM 3m 6s build Rollback Unavailable

User canceled a deployment Trigger: User configured web settings 05:09:42 AM 0m 6s build Rollback Unavailable

App Platform's deployment failed during deploy phase Trigger: null pushed cb1b0b6 to REMOVEDFORPRIVACY/main 04:51:50 AM 2m 12s build Rollback Unavailable

App Platform pushed zero-downtime, automatic rollback to previous deployment went live 04:04:46 AM 0m 1s build Rollback

User's deployment failed during deploy phase Trigger: User configured web settings 03:58:35 AM 2m 22s build Rollback Unavailable


May 30th, 2023 01:19 AM

Hi there,

Based on the errors provided it is hard to pin point what exactly the problem is. Do you see the actual error preventing the build from completing rather than only the rollback error?

If you wish you could invite me to your DigitalOcean team and I could look into this for you:

DigitalOcean Teams

For the assets, in order to use the DigitalOcean spaces with Voyager, you would need to make some extra configuration changes as described here:

Using DigitalOcean Spaces for Laravel Object Storage

And then change the storage disk in the config/voyager.php file to:

storage' => [
  'disk' => 'digitalocean',

May 30th, 2023 01:20 AM

Yep I'll add you to it now. I really appreciate this!


May 30th, 2023 01:22 AM

I should probably ask what I need from you to add you though :S


May 30th, 2023 04:24 AM

Best Answer

Hi there,

Just in case anyone comes across this in the future, we had to increase the Heath check initial timeout as the deployment stage was taking a bit longer than usual.

After that, it was all working as expected!


May 30th, 2023 04:26 AM

And when he says 'we', he definitely means he :) Thanks Bobby! That was driving me crazy!


May 30th, 2023 11:54 PM

As a follow up, I've wrote a quick tutorial on how to implement Spaces with Voyager in case that anyone else comes across this in the future:

How to use DigitalOcean Spaces with Laravel Voyager?