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

refactor: local restore #1919

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

refactor: local restore #1919

wants to merge 1 commit into from

Conversation

roschaefer
Copy link
Collaborator

Motivation

I'm trying to write a regression test for #1914. For that I need to setup signal locally. I do it with restoring a backup from one of our demo instances.

It turns out that signal-cli-config was not restored. Second, I removed obsolete docker-compose.backup.yml and unnecessary tmp/db folders by just using docker compose cp, plus I DRYed the ansible playbook.

How to test

  1. ansible-playbook ansible/restore_locally.yml
  2. Runs faster, no temporary folders created.

Motivation
----------
I'm trying to write a regression test for #1914. For that I need to
setup signal locally. I do it with restoring a backup from one of our
demo instances.

It turns out that `signal-cli-config` was not restored. Second,
I removed obsolete `docker-compose.backup.yml` and unnecessary `tmp/db`
folders by just using `docker compose cp`, plus I DRYed the ansible
playbook.

How to test
-----------
1. `ansible-playbook ansible/restore_locally.yml`
2. Runs faster, no temporary folders created.
@roschaefer roschaefer requested a review from mattwr18 June 29, 2024 11:38
Copy link
Contributor

@mattwr18 mattwr18 left a comment

Choose a reason for hiding this comment

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

I'm not sure I actually like these changes @roschaefer ... I suggested making similar changes when we introduced the backup of the signal-cli-config and Till pointed out the potential danger in doing so. Have a look.

#1380

I have a signal-cli-config for development. Maybe a better solution is to save a zip of this to 1password that you could use whenever you want to test out signal stuff? I also like the idea of not having actual contributors from a production instance in your db while you are testing out Signal since you could easily send out a message to everyone without intending on it.

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.

2 participants