We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've followed the instructions in the deploy to s3 recipe and allowed the plugin to create the bucket from scratch.
But it seems that this plugin deploys all page files as index.html pages within a folder with the page name so
index.html
my_page.tsx => my_page/index.html
While this is fine in principle it means that navigating to https://my_host.com/my_page results in
https://my_host.com/my_page
<Error> <Code>NoSuchKey</Code> <Message>The specified key does not exist.</Message> <Key>my_page</Key> <RequestId>4CS85R71VWWWZDZ180</RequestId> <HostId> 3gTHCMxGXVjCvC3Dhubtdsfew34zTfEY5W0eBd+ceThMQZwD9fJn2FUl3Gi0+OR5d9Oavmx9W3Digab0Eo= </HostId> </Error>
It doesn't feel like this can be the intended behaviour? Is there something I'm missing?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I've followed the instructions in the deploy to s3 recipe and allowed the plugin to create the bucket from scratch.
But it seems that this plugin deploys all page files as
index.html
pages within a folder with the page name soWhile this is fine in principle it means that navigating to
https://my_host.com/my_page
results inIt doesn't feel like this can be the intended behaviour? Is there something I'm missing?
The text was updated successfully, but these errors were encountered: