Skip to content

Conversation

@aclark02-arcus
Copy link
Collaborator

@aclark02-arcus aclark02-arcus commented Apr 7, 2025

Currently, not operational when using push button deployment from Rstudio IDE, with the following error:

image

Probably because a different version exists on pkg manager??? As seen here:

image

@LDSamson
Copy link
Collaborator

LDSamson commented Apr 7, 2025

1.84.0-0 is the BH version of RSPM date 2024-09-17.
image

The link with date 2025-04-01 is named RSPM2 in the renv.lock file, not RSPM. I don't know why it does not recognize the correct source link here.

Edit: for reference, see https://github.com/openpharma/clinsight/tree/ls_deploy_shinyconnect

@LDSamson LDSamson linked an issue Apr 7, 2025 that may be closed by this pull request
manifest.json Outdated
Comment on lines 38 to 39
"Source": "RSPM",
"Repository": "https://packagemanager.posit.co/cran/2023-11-01",
"Source": "RSPM2",
"Repository": "https://packagemanager.posit.co/cran/2025-04-01",
Copy link
Collaborator

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?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, that seems to be related. Though I don't know why that would happen, because manifest.json is built directly from renv.lock.

image

Copy link
Collaborator Author

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.

Copy link
Collaborator

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.

Copy link
Collaborator

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?

Copy link
Collaborator Author

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.

Copy link
Collaborator Author

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.

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
@aclark02-arcus
Copy link
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create shinyapps.io demo app deployment

4 participants