Docusaurus 2, cleanUrl false and deployment to google cloud

In the migration guide you wrote that cleanUrl option is removed and it is true now by default. That means, all urls have no .html extension ending. And that is a big problem for us)

The problem, is that our documentation is deploying as a static assets to Google Cloud Storage (https://storage.googleapis.com …). That means, clean request cannot be redirected to dirty request, and after reloading any page we have this type of error:

<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Details>
No such object: ...
</Details>
</Error>

That happens because my-document-url is not the same object as my-document-url.html, from google’s point of view.

Is it possible to override cleanUrl to false somehow in docusaurus 2?

[amimas]

I ran into a similar situation. I’m currently using V1 of Docusaurus and for deployment I use AWS services (S3 + CloudFront).

The problem is that when the static site assets are deployed to AWS S3 bucket, you’ll have to send a request for an exact path of an object (i.e. a file). It doesn’t work like a traditional web server where you’re automatically redirected to “index.html”.

In my case, I’ve setup a AWS Lambda function attached to AWS CloudFront. Before AWS CloudFront (a CDN) tries to fetch an object from AWS S3 storage, the Lambda function inspects the requested URL and changes it include “/index.html” at the end, if needed; basically tries to mimic a regular web server.

I haven’t dealt with Google Cloud yet, but I believe you can do something like this using Google Cloud Function. Pretty much all the cloud providers these days provides serverless functionality.

Hope that helps.

[amimas]

@joeplaa glad you found a pointer to get started. In case it helps, you can also deploy the following directly from aws lambda. The concept is the same.

https://serverlessrepo.aws.amazon.com/applications/arn:aws:serverlessrepo:us-east-1:621073008195:applications~standard-redirects-for-cloudfront