Ah, that's a different issue. The deployment actually was successful. I see the static files in the backend (object store). But the API call from the CLI timed out because processing and deploying the files took too long.
So while the API was doing its work, and taking a minute or so, the CLI client got impatient and showed you a FetchError.
I am planning to replace the synchronous deployment API with an asynchronous design. That should prevent this confusion.
Congratulations on your work! This platform is Super cool! Keep doing well, and i got some errors while deploying prnt.sc/l4rpj3
Hi Yoginth! Thank you, that means a lot. :)
Let me take a look, should be a simple fix on my end. (Famous last words...)
Update: Should be fixed now. Disabled auto-renewal of the API server's certificate a while ago. Just did a manual renewal. Will automate this asap.
Sorry to Say! Still it's not working :( prnt.sc/l4v71q
Ah, that's a different issue. The deployment actually was successful. I see the static files in the backend (object store). But the API call from the CLI timed out because processing and deploying the files took too long.
So while the API was doing its work, and taking a minute or so, the CLI client got impatient and showed you a
FetchError.I am planning to replace the synchronous deployment API with an asynchronous design. That should prevent this confusion.
See: gitlab.com/commonshost/core/issues/12
Thanks for the feedback btw! Really helps me focus on solving these friction issues. ☺️
PS: If you deploy Markdown (
README.md) it is not automatically converted to HTML. Run a local build (or in CI) before deploying.