Deploying to s3 compatible storage, such as Linode, Rackspace, AliCloud, etc

[wuhuw]

There are many other providers that have s3 compatible cloud storages, It will be so nice to have that.

[leonstafford]

@wuhuw - definitely on the agenda!

Q: Do you know if most S3 compatible services are supporting the latest S3 SDK methods?

I may still be adding specific addons for things like Rackspace, if there are other fields or behaviours specific to Rackspace. In the main S3 addon, we can then have an override to the connection URLs to allow using with other providers (only thing blocking it currently, which should be able to be adjusted with minor code change)

[wuhuw]

Cool. I think that should work. I am currently using Media cloud plugin to host my uploads into Alibaba cloud OSS which is s3 compatible. so far so good.

[wuhuw]

@leonstafford I am really looking forward to this update. Only one extra filed to save customized endpoint URL. Thanks

[tareco]

This would be great, looking forward to have a way to deploy directly to S3 compatible Linode object storage.

[leonstafford]

Moving this to a Discussion/Idea, but we have already S3 and GCS deployment add-ons, so I suggest forking those and creating your own for Alibaba, Rackspace, Linode, etc, then share back what you find works. I can then either point users towards your addons or convert them to official ones I maintain. You can also hire developers if you aren't able to do yourself, I'm happy to give them advice if they get stuck. Unfortunately, I'm just unable to promise quick delivery of any other custom deployment options at the moment :(

[wuhuw]

Actually, the simplest solution for this is to allow editing s3 endpoint. That is it. I guess it is 5 to 10 minutes of coding.

[john-shaffer]

The so-called "S3-compatible" storage doesn't actually have the functionality we are using, so it is not going to be that easy.

[wuhuw]

I found anther plugin called staatic, they have a custom end point field, and that is it. it makes all s3 compatible storage work.

[leonstafford]

Update to what John commented. We have now invested a lot of effort into improving the S3 + CloudFront deployment add-on and there is a separate one for Google Cloud Storage.

While there is a lot of other work needed first in the core WP2Static plugin and you can manually take what WP2Static exports and use other tools/scripts to deploy to things like Linode, Rackspace, AliCloud, etc, I suggest these options for those looking:

• use WP2Static to generate and manually deploy using a sync tool for your specific cloud provider (if an S3 compatible tool works, like AWS CLI sync tool or CyberDuck on macOS, FuseFS, etc, then by all means use those).
• fork our S3 or Google Cloud Storage add-ons from GitHub and adjust to use the APIs for your specific provider

I'd love to build out every deployment option, but realistically, it's unlikely to happen until the core plugin has no issues left, does a perfect job of detecting and crawling URLs, etc.

If you want to commission another developer to help you come up with such a solution AND it's open source on GitHub, I'll be happy to try and assist if you get stuck.

The beauty of this open source stuff, is that if it's really just 5 to 10 minutes of coding, nobody's stopping you from doing it yourself or hiring someone to do it for you. I have no restrictions on usage, as you can see by my choice of The Unlicense. I have to do this myself for other projects, where I really just want them to change 1 line of code for my intended usage, but they're in no hurry, so I fork it and make my own customised version.