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

started working on migration code. #224

Merged
merged 8 commits into from
May 5, 2022
Merged

started working on migration code. #224

merged 8 commits into from
May 5, 2022

Conversation

AnalogJ
Copy link
Owner

@AnalogJ AnalogJ commented May 5, 2022

  • [feat] added ability to migrate existing scrutiny database to influxdb.

@AnalogJ AnalogJ merged commit 3dbe597 into influxdb May 5, 2022
@AnalogJ AnalogJ deleted the influx_migrations branch May 5, 2022 15:08
@tandy-1000
Copy link

Discard my comment in the last PR, I see that the code for auto migration isn't finished yet.
At the moment I get:

INFO[0000] Trying to connect to scrutiny sqlite db: /opt/scrutiny/config/scrutiny.db 
INFO[0000] Successfully connected to scrutiny sqlite db: /opt/scrutiny/config/scrutiny.db 
panic: Unexpected status code 404

If that's relevant to you...

@AnalogJ
Copy link
Owner Author

AnalogJ commented May 10, 2022

@tandy-1000 The automigration code is complete actually. The mountpoint has changed however, which is probably why you're seeing this issue:

/scrutiny/config has changed to /opt/scrutiny/config. You'll want to change your docker-compose.yml or docker run commands.

@tandy-1000
Copy link

@tandy-1000 The automigration code is complete actually. The mountpoint has changed however, which is probably why you're seeing this issue:

/scrutiny/config has changed to /opt/scrutiny/config. You'll want to change your docker-compose.yml or docker run commands.

I don't use docker, I'm using a manual install which is already at /opt/scrutiny, any ideas?

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