-
Notifications
You must be signed in to change notification settings - Fork 2
Branch dedicated to dev demo
#183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
|
1.84.0-0 is the BH version of RSPM date 2024-09-17. The link with date 2025-04-01 is named RSPM2 in the Edit: for reference, see https://github.com/openpharma/clinsight/tree/ls_deploy_shinyconnect |
manifest.json
Outdated
| "Source": "RSPM", | ||
| "Repository": "https://packagemanager.posit.co/cran/2023-11-01", | ||
| "Source": "RSPM2", | ||
| "Repository": "https://packagemanager.posit.co/cran/2025-04-01", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here you are using a different source link for the BH package. It should be 2024-09-17. Could that be the source of your error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just so we're all on the same page, it's my understanding that manifest.json is only used by Posit Connect. When deploying to shinyapps.io, Posit doesn't acknowledge this user created file, generated by rsconnect::writeManiest().
Yet Posit does automatically build it's own manifest for deployment. I confirmed this by deleting the manifest.json file and attempting to re-deploy and I still got the same error.
So, in summary, rsconnect::writeManiest() is likely capturing the same symptom that shinyapps.io is running into.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you share more of your workflow? rsconnect::writeManifest() doesn't work out of the box with renv profiles, so I'm just curious if there's something else going on as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't think rsconnect and dependencies would need to be added to renv.lock either. Did you do that just for transparency or was it needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Jeff-Thompson12, it was for transparency AND because it was aimed at our "full" renv.lock which can include anything we want for development purposes, right? Hence the name, full.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you share more of your workflow?
rsconnect::writeManifest()doesn't work out of the box withrenvprofiles, so I'm just curious if there's something else going on as well.
see app.R on this branch.
# Conflicts: # .rscignore # DESCRIPTION # R/app_ui.R # manifest.json # renv/profiles/full/renv.lock # renv/profiles/minimal/renv.lock
|
Deployments dedicated to |


Currently, not operational when using push button deployment from Rstudio IDE, with the following error:
Probably because a different version exists on pkg manager??? As seen here: