I’m trying to use pages for my repo https://codefloe.com/klimaticka-koalice-olomouc/vybersiolomouc_cz. When this feature is enabled, this results in following URL: https://vybersiolomouc_cz.klimaticka-koalice-olomouc.codefloe.page/. However, it doesn’t work, because loading of the URL results in ERR_SSL_PROTOCOL_ERROR (in Chrome) or SSL_ERROR_INTERNAL_ERROR_ALERT (in Firefox). Is there anything I can do to resolve this?
Try to only have the published assets in the root dir of the pages branch, not the source. Keep the source in the default branch.
Alright, thanks. Does that mean that I should use CrowCI/Forgejo CI for a build and forget about commandin the statichost.yml file? If so, it looks like documentation is misleading 
Also, now I realize that I probably should create an account at Statichost, because not havond an access to logs is really a nightmare when debugging.
Building yourself and only forwarding the static output is the easiest path.
SH does have restricted support for rendering and the inclusion of statichost.yml works for some but not all - TBH we also currently not do not know when and how it applies. The SH API isn’t documented and we’re currently relying on undocumented API endpoints (which we got passed on from the SH owners when building the integration).
We hope this improves in the future and we hope to also surface the underlying logs to users at some point - but this will take a while. If you want more control (and especially if you need SSR), you might be better off with your own personal account. The benefit of a CF account is that rendering of private repos also works for free - which is restricted for other “normal” accounts.
We’ll have to check the docs, it might indeed not be up-to-date to how the integration behaves at the moment!
@milos.kroulik Besides improving our Pages integration and now displaying a build log to users, we’ve also went ahead and fixed your website build in the pages-fix branch to ensure nothing else on our side is a blocker.
Your site now renders fine - have a look at the changes we did in the branch. You can then incorporate these into your default branch.
Hope this helps to get you up and running!