Closed rosseji closed 4 years ago
Do you have a lot of complex start up code outside of any endpoints in your API? You'll see that error if your API takes too long to become responsive.
We're making this property configurable per app in the next RSC release in January. See [Scheduler].InitTimeout
if you want to give your processes longer to startup. This section of the docs would be worth a read if that is what's going on here. http://docs.rstudio.com/connect/admin/appendix-configuration.html#appendix-configuration-scheduler
shinyapps.io does not currently support having API applications deployed to it.
I believe he's on Connect, @jspiewak
@trestletech I was going by the first line of the issue with the error, which looks like shinyapps.io
Oh, you're right. My bad.
Thanks for the help. What is the intended destination for the deployAPI()
function?
I have got it to work before, @trestletech helped me with some issues, and it worked fine (Screen shot of deploy that wasn't finding the plumbed functions):
Current supported destination of deployAPI is a Connect server. deployAPI will deploy to shinyapps.io, but it is unsupported and may work to a greater or lesser degree than is desirable until full support is rolled out.
@jspiewak Should we specifically wall off deploying APIs to shinyapps.io for now?
We'll track that work in https://github.com/rstudio/rsconnect/issues/204.
Same error when deploying and API via
deployAPI()
as #204. Isn't that an error suggesting its not a supported type?@trestletech Any ideas?
Had success previously.
Occurs when deploying with:
R
3.4.2,rsconnect
8.5,