About the cdn , again about examples

[bigtimebuddy]

Good plan. I think only sound, filters and the main repo use s3 deployments on Travis. For the main repo we need to make sure we update both the dev/master branch and v4.x branch, since that’s still getting maintained too.

[finscn]

I've used VPN , I can visit youtube twitter facebook , except you cdn .

[ivanpopelyshev]

release is now v5 and we have some problems with it, if you look at other issues that were spawned today/yesterday.

I'm both hands for extra CDN that wont be blocked by country firewalls.

[englercj]

I'm open to using this if you want to build the infrastructure necessary for us to deploy to it. Right now our AWS flow is pretty easily supported. I'm not sure what we would do to use jsdelivr is as seamless a way as we do AWS, but I am of course open to it.

[finscn]

since 2019 , I've never open the example page.
I need it for learning the PIXI v5 .
Could you use jsdelivr.com instead of cloudfront.net , please ?
I beg you.

[finscn]

I use a proxy ( on vultr.com ) , I can visit youtube, twitter, facebook , but I still can't visit cloudfront.net.

[englercj]

Cloudfront recently added support for mainland China, so we should be able to configure it to do so. I'll investigate further. https://aws.amazon.com/about-aws/whats-new/2019/04/amazon-cloudfront-is-now-available-in-mainland-china/

[englercj]

A China legal entity is required to register an AWS China Region accounts.

Well I guess that won't work.

[englercj]

Cloudflare is what I use for pixiplayground.com and it seems to work in China, maybe we switch to that for our CDN front-end to S3. I'll try setting up a staging version that uses cloudflare and try it out.

[englercj]

So looks like for us to proxy our S3 traffic through CloudFlare we would need to have the bucket name match exactly the DNS CNAME.

Currently we are exposing the buckets using different names than their CNAME. For example the bucket pixi.js is exposed as pixijs.download and pixi-filters is exposed as filters.pixijs.download. If we want to use CloudFlare as the CDN we'd have to rename our buckets to match the names. For example filters.pixijs.download as the bucket name so it matches the filters.pixijs.download request URL. Is that something we want to do?

[bigtimebuddy]

How hard is it to rename S3 buckets? I’m okay with that change of it makes this easier. As long as we don’t have to rename all our end points or something, this seems like a minor internal AWS change.

[englercj]

I think you are right it should be a mostly internal change. AFAIK this is the checklist:

• Rename all buckets to match the expected domain name they load at
• Update CloudFront configuration to ensure it continues to operate correctly while we explore CloudFlare
• Update all our travis.yml files to point to the new bucket names

After that, to move over to CloudFlare we would just need to change our nameservers to point to CloudFlare and setup the propert CNAMEs for our buckets. I imagine there will be some amount of downtime to get it working.

I don't mind doing this work if we agree it is something we want to do. Let me get a test up on my pixiplayground domain that points to a bucket in our pixi AWS account and have @finscn confirm that it works where he is before we go too deep.

[englercj]

Hey @finscn can you confirm that:

1. this CloudFlare url works properly
2. this CloudFront url does not work

Thanks!

[finscn]

@englercj ,
the first one could be opened , (but it's not cloudflare, the doamin is pixiplayground.com)
the second can't.

[englercj]

The domain is pixi.pixiplayground.com,which is served by Cloud Flare.

Glad it worked, I'll get us moved over as soon as I can.