search

rstudio / rsconnect

Publish Shiny Applications, RMarkdown Documents, Jupyter Notebooks, Plumber APIs, and more
http://rstudio.github.io/rsconnect/
131 stars 80 forks source link

Ignoring any selected local packages during deployment #465

Closed Polkas closed 1 year ago

Polkas commented 3 years ago

This issue was already stated on the stack overflow. During deployment, manifest generator should allow (packrat) to ignore the existence of any selected local packages. This is an option in packrat, but rsconnect does not expose this option.

The solution provided by Soren Havelund Welling was suggesting to update the PackratSnapshot() function to allow for this functionality.

I will be very glad if you offer such functionality or provide response why you do not want support it.

Stack overflow question: https://stackoverflow.com/questions/53006625/rstudio-connect-packrat-and-custom-packages-in-local-repos

Thanks

Polkas commented 3 years ago

I will be glad if you even simply say that you do not want to support it and close the issue. Thanks for any respond.

slopp commented 3 years ago

Could you clarify where you are attempting to deploy to and what role your internal package provides?

rsconnect is assuming that if the package is identified in the project code locally than the package will be required when the code is deployed. The error attempts to help users fail fast in this scenario, as opposed to deploying code that will not run.

Polkas commented 3 years ago

The main objective is to publish the app on the corporate server where we have own CRAN. Then we attaching packages by expanding .libPaths(). So the deployment takes only 30 seconds not 10 minutes. Moreover with this step (own CRAN) we are sure about the reproducibility of our own projects. This is an option already inside packrat so the question is if you want to offer sth which is already there.

hadley commented 1 year ago

I think we're mostly likely to support this via #471