Exactly the same PR as #6, but with the merge conflicts addressed.
RTM tested the updates to this recipe when deploying our own baserow and they appear gtg.
Exactly the same PR as https://git.coopcloud.tech/coop-cloud/baserow/pulls/6, but with the merge conflicts addressed.
RTM tested the updates to this recipe when deploying our own baserow and they appear gtg.
Thank you @linnealovespie for working this out, I had meant to merge this a while ago and forgot. Glad to see someone else is paying attention :)
@ammaratef45 not sure if this is what you're asking but I tested this feature manually by making a snapshot using backup-bot-two, changing data in baserow, and then running a restore.
Thank you @linnealovespie for working this out, I had meant to merge this a while ago and forgot. Glad to see someone else is paying attention :)
@ammaratef45 not sure if this is what you're asking but I tested this feature manually by making a snapshot using backup-bot-two, changing data in baserow, and then running a restore.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Exactly the same PR as #6, but with the merge conflicts addressed.
RTM tested the updates to this recipe when deploying our own baserow and they appear gtg.
lgtm, just had that one comment + a general (for the record) question, how was that tested?
@@ -34,0 +33,4 @@- "backupbot.backup.pre-hook=/backup.sh pre-backup"- "backupbot.backup.post-hook=/backup.sh post-backup"- "backupbot.restore.post-hook=/backup.sh post-restore"- "coop-cloud.${STACK_NAME}.version=1.2.0+1.35.3"Did the version decrease on purpose or a merge conflict?
Thank you @linnealovespie for working this out, I had meant to merge this a while ago and forgot. Glad to see someone else is paying attention :)
@ammaratef45 not sure if this is what you're asking but I tested this feature manually by making a snapshot using backup-bot-two, changing data in baserow, and then running a restore.