Bengt Brodersen

I think you should use `continuation-token` query parameter instead of `marker`https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html#API_ListObjectsV2_RequestSyntax:~:text=Required%3A%20Yes-,continuation%2Dtoken,-ContinuationToken%20indicates%20Amazon

sadly I don't know how to help you with that issue.

Should work now.

Where should I deploy? Or just anywhere?

feel free to test http://ec2-3-72-47-194.eu-central-1.compute.amazonaws.com

You have used a wrong url pattern you need to use it like this `//gist:` e.g. http://ec2-3-72-47-194.eu-central-1.compute.amazonaws.com/qoomon/gist:5dfcdf8eec66a051ecd85625518cfd13

Or what about following convention? - `//` - `/gist//` - or back to the initial idea `/gist:/` I thinks repos(files and directories repos) and gist (file only repos) are so...

At least every thing is now working as expected, I fixed all issues.

I've deployed a version with the initial url pattern `/gist:/` see http://ec2-3-72-47-194.eu-central-1.compute.amazonaws.com/gist:qoomon/5dfcdf8eec66a051ecd85625518cfd13 I think this is the most appealing variant

Unfortunately it would be a complete refactoring. The header always shows the name of the first file (even if there a multiple files in one gist) And just an extra...