Just wondering if it's possible to republish on a schedule, or when the linked GitHub repo is updated, or if there's some feature like that might be coming up soon? I was trying to find an option other than manually clicking to republish as I'm experimenting with deploying a Quarto dashboard which needs updating daily.
1 Like
Hi Nic - how are you? For the Alpha release, you need to click the button. However, we are exploring the GitHub integration to make pushing to your repo automatically redeploy.
Curious if you'd like to see this behavior by default or something that you could turn on/off depending on a specific piece of content.
Hope to see you at Conf again this year!
Hi Alex,
Ooh, that's awesome, that'll be a great feature to have!
I think configurable would make sense; like, for this project, sure I want to update every time I push to the main branch + on a schedule, but I could imagine people wanting to share a static snapshot of something too.
Yeah, I'll be at conf; this dashboard is the focus of a talk I'm co-presenting actually. Look forward to seeing you there!
1 Like
Hi @Alex_Chisholm1 - came across this post. Now that Connect Cloud is in beta, does it support automated deployments either as described above or using the connectapi package? I haven't found documentation anywhere about this.
Hi Kyle. Yes, all plans now support automatic publishing when you push to the associated repo/branch. When you deploy a new piece of content on Connect Cloud, Automatically publish on push is selected by default in the Source configuration panel. It can also be turned on for old content by editing settings.
Full documentation coming soon.
Currently, there isn't an automatic republish feature triggered by a GitHub repo update in Quarto. However, you can automate this process using GitHub Actions or a similar CI/CD tool to trigger the republish of your dashboard whenever the repo is updated. This would allow you to set up a daily schedule for updates without manual intervention.
Hi @alex_chisholm - I'm not seeing this working in a test repo I'm using as the apps aren't updating when I push (I have to do it manually). Can I confirm that this feature is active / working?
Hi Kyle,
The feature is active. Two questions:
- Is the repo in the same GitHub account from which you installed the GitHub app on Connect Cloud?
- When you setup the GH app, do you recall if you selected
All Repositoriesor
Only select repositories? IfOnly select repositories, is the repo in question included on the list? You can check from: Sign in to GitHub · GitHub
Alex
Thanks Alex. The answers are Yes and Yes to your questions; the repo is in my GitHub account, and I have All Repositories selected.
Here's the repo in question: GitHub - walkerke/deployment-demo: Automating app deployments to Posit Cloud Connect - and here's one of the associated apps, if helpful: https://walkerke-population-app.share.connect.posit.cloud/
I just tested again - I pushed a new commit to the repo (updating the underlying data used by the apps) and it did not trigger an app update.
For what it's worth, I'm having the same issue (and answering 'Yes' to both Alex's questions) with rendering a simple Rmd (https://01962d29-9d95-cfdd-8278-135eb4faa242.share.connect.posit.cloud , GitHub - andrewbcooper/us_clinical_trials )
@alex_chisholm Just to make sure, I created a new repository and shiny app following these directions:
https://docs.posit.co/connect-cloud/how-to/r/shiny-r.html
It worked as expected. Then I edited the app.R file to change the title and successfully pushed the changes to the public Git repository. However, the app on Posit Connect Cloud has not re-deployed. I waited 25 minutes (I remember reading somewhere that the fetch on Posit Connect runs every 15 minutes) and still no change. The Git repository and Posit Connect Cloud can be found GitHub - andrewbcooper/positcloudtest and Posit Connect Cloud
@andrewbcooper the issue here is that you haven't granted Posit Connect Cloud access to that particular GitHub repository, so the events that would trigger the auto publish were never sent.
If you Configure the Posit Connect Cloud application in your GitHub Settings to grant access to that repository , it should start working.
thanks
sam
Another update, turns out there is a bug in our system that is preventing auto publish from working. We hope to have a fix out shortly, sorry about this. Thank you very much for bringing it to our attention! (@kylewalker this is likely affecting your content as well)
thanks
sam
1 Like
We've just released a fix for this bug. Auto publishing should work again the next time you push to your repositories.
1 Like
Ah ha! I didn't realize I had only granted access to a single repository. I fixed that and it worked! Thank you so much!
1 Like
@alex_chisholm and @samp, and by following this example for running an RScript via Github actions (How to Use GitHub Actions with R to Run Code Automatically) I was able to fully automate the data refresh on a cron schedule! Thank you so much for all your help! This is totally amazing!!!!
1 Like
These tools allow for automated or workflow-based republishing, often triggered by events like content updates or scheduled we are exploring the GitHub integration to make pushing to your repo automatically redeploy To do this, open the Pages menu and select pineapple vodka wine Set as a draft in the settings for the page you'd like to not be published I seem to get an error page telling me to look at my admin email box and critical then republish it immediately in just a few
You can automate republishing using GitHub Actions or a CI/CD pipeline. Set up an action to trigger on repo updates and use the rsconnect package to redeploy automatically. This way, your Quarto dashboard will update daily without manual clicks.