I have created a build from a server (we’ll call it Server A). I have used the Publish to Offsite Location in the build settings to push this to an offsite storage location.
When setting up a deployment, I select Offsite Location as the Default Source and the Desired Server (we’ll call it Server B) as the destination. In this configuration I am unable to select any offsite locations for the build.
If I select Server A as the destination, I am able to select the correct Offsite Location for the build; however, I wish for the deployment to be on Server B. Changing the destination to Server B and attempting to run the deployment results in two errors
Error validation deployment: OttoFMS API Error: Error fetching manifest from offsite location: Cannot read properties of undefined (reading 'msg). HTTP Status Code: 500.
No deployments found on your deployment
Hi James.
Do both servers have access to the same offsite storage location? They both should have access to the same location. They should be setup in the same way on both servers.
Thanks
Todd
Thanks Todd, I didn’t have the offsite setup on the destination server.
There may be scenarios in future where we wouldn’t want to setup the destination server with any offsite keys (we have different sets of keys that can read/write to various different buckets; however, regardless of the key used all buckets are listed in the Otto console). We’re using Linode / Akamai in this scenario in case that makes a difference.
I can understand why you might want to do that. But publishing to Offsite requires the two servers have access to the same location. That is how it works. I don’t think we will be changing that.
We do have other options coming for publishing a build that will likely serve the use case you want. And currently you can always just put the build on any web server and use the Build url method.
Hope that helps
Thanks
Thanks Todd, appreciate the response. We can work with pushing to a web server and using the build url method where required.