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
Gravity Sync #28
Comments
Ah, great catch! Thanks for this. I was hoping the teleporter would automatically take care of this but I guess not. I'll look into this further and see what's involved in making sure this gets run |
I will test further as I have been hit by the permission issues in docker pihole, took a while to figure that one out. This manifested in failures to write to the adlist on the dB. Setting env WEB_UID to the container's pihole user resolved it. For now at least. |
The issue stills stands for me. I added a new item to the adlist on the primary. Manually triggering an update of gravity refreshes without an issue. |
@mentalsoup I've published a beta version of the container that should resolve this. The image has been published as: If at some point you have the time to try it, I'd love to hear if it works for you 😄 |
Thanks @mattwebbio, great work. I have updated to mattwebbio/orbital-sync:1.2.2-beta.0 and the sync has completed successfully on both targets. No errors, but this has spawned a new idea, I will raise a new feature request. |
Perfect! I've gone ahead and released version |
What feature would you like added?
Based upon a fresh instance of pihole on both docker tenants.
Feature
Once the teleport completes successfully, then trigger gravity sync on the secondary pihole.
Observations
I noticed that after a successful sync between master and secondary pihole tenants, the adlists on the secondary did not appear to be downloaded.
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
Version
1.1.1 (latest)
Log output
No response
The text was updated successfully, but these errors were encountered: