Skip to content
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

Allow observers.sqlite to be configured in a separate working directory #274

Closed
Tracked by #353
CharlieC3 opened this issue Feb 29, 2024 · 0 comments · Fixed by #354
Closed
Tracked by #353

Allow observers.sqlite to be configured in a separate working directory #274

CharlieC3 opened this issue Feb 29, 2024 · 0 comments · Fixed by #354
Assignees

Comments

@CharlieC3
Copy link
Member

It's my understanding the observers.sqlite holds registered predicates on who to send event data to and the scope of that data. When taking backups and restoring from a backup, we often don't want to restore an old observers.sqlite file, since the registered predicates from the backup may have changed since then, and may be old.

Ideally the observers.sqlite file could be configured to be written and read from a different working directory, so that we can take separate snapshots of two different disks, and only restore the data we're interested in.

@github-project-automation github-project-automation bot moved this to 🆕 New in Ordinals Feb 29, 2024
@andresgalante andresgalante moved this from 🆕 New to 📋 Backlog in Ordinals Mar 4, 2024
@rafaelcr rafaelcr self-assigned this Aug 2, 2024
@rafaelcr rafaelcr moved this from 📋 Backlog to 🏗 In Progress in Ordinals Aug 2, 2024
@github-project-automation github-project-automation bot moved this from 🏗 In Progress to ✅ Done in Ordinals Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants