miniature-potato-84713
12/14/2018, 12:15 AMAccept-Language
header or a saved cookie, I think we’ll have to do some URL rewriting (to ensure transparency and SEO). For example, foo.bla/site.html
should forward to foo.bla/en/site.html
by default, or whatever language the header/cookie contained.
Solutions
1. Client-side Javascript “cloaking” etc are off the table, I think. Doesn’t play well with SEO and is annoying for clients.
2. Use AWS S3 and web-page redirect: https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html
3. Host the site in a Kubernetes container with nginx/apache.
Of 2. and 3. I am leaning towards 2. because it’s probably easiest to set up for now. Both could be implemented using Pūlumi, and that would be the right way to go about it.
What are your thoughts, and does Pūlumi handle the redirect configurations for 2.?white-balloon-205
routingRules
at https://github.com/pulumi/pulumi-aws/blob/master/sdk/nodejs/s3/bucket.ts#L109 and the format of routing rules here: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-s3-websiteconfiguration-routingrules.htmlcreamy-potato-29402
12/14/2018, 12:48 AMminiature-potato-84713
12/14/2018, 1:44 AM<http://pulumi.io|pulumi.io>
is (very) similar to this example https://github.com/pulumi/examples/tree/master/aws-ts-static-website ?white-balloon-205
miniature-potato-84713
12/14/2018, 9:48 PMmaster
will update the S3 content objects?white-balloon-205
master
and production
).
If you have access to Actions, you could do that too in a similar way.miniature-potato-84713
12/19/2018, 12:27 AMpulumi new
is probably best, but the <https://github.com/pulumi/docs/tree/master/infrastructure>
would be a aws-typescript
template?