I've encountered a problem which I am not sure how to solve with rsconnect:
I have created a conda environment which contains multiple Bioconductor packages (installed through conda using the bioconda repository).
Within this environment I wanted to upload a shiny app to the shiny apps.io server (using rsconnect, also installed through conda in the same environment). This is the code I used:
I was wondering if it is possible to tell rsconnect to also look in the archive directory or provide a direct URL to the source package? My current work-around is to create a seperate conda environment for deployment where all of the Bioconductor packages are manually installed through BiocManager. I'm not sure how often this sort of error occurs and whether it should be fixed through rsconnect (e.g. providing a direct URL or access to the Bioc archives) or on a case-by-case basis by updating the recipes on bioconda?
I've encountered a problem which I am not sure how to solve with rsconnect:
I have created a conda environment which contains multiple Bioconductor packages (installed through conda using the bioconda repository).
Within this environment I wanted to upload a shiny app to the shiny apps.io server (using rsconnect, also installed through conda in the same environment). This is the code I used:
I was wondering if it is possible to tell rsconnect to also look in the archive directory or provide a direct URL to the source package? My current work-around is to create a seperate conda environment for deployment where all of the Bioconductor packages are manually installed through BiocManager. I'm not sure how often this sort of error occurs and whether it should be fixed through rsconnect (e.g. providing a direct URL or access to the Bioc archives) or on a case-by-case basis by updating the recipes on bioconda?