have enabled proxy settings to install package from CRAN.
After installation, While tried to publish the app in Rstudio connect, it stared referring .../minicran/src/contrib/Archive instead of ../minicran/src/contrib. why it is referring Archive filesystem? this issue occurred many of the users for referring Archive directory:
Please refer the deployment log
2019/04/12 08:43:45.649548383 curl: (37) Couldn't open file /proj/rstudio/minicran/src/contrib/Archive/rhandsontable/rhandsontable_0.3.6.tar.gz
I had a similar Issue & resolved it by creating proj/rstudio/minicran/src/contrib/Archive/rhandsontable and copying rhandsontable_0.3.6.tar.gz from /proj/rstudio/minicran/src/contrib.
The issue basically seems to be happening because only the current version of the package should be in the miniCRAN Repo & all the old versions should be in the archive. I am also trying to figure out if there is any command or process to do it for all packages inside miniCRAN, any idea would be helpful.
@rakesh is spot on. This is how CRANlike repositories function, and is extremely important to the way that RStudio Connect manages packages / reproducibility for your content. You can see an example here:
I'm not sure whether miniCRAN offers this functionality (I would honestly be surprised if it didn't), but I know the drat package does. In any case, in the enterprise context, removing the pain of maintaining a CRANlike repository is one of the aims of RStudio Package Manager.