Populate list of sites from a feed/API to import #477

New issue

Closed

opened 2026-02-28 01:47:50 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 01:47:50 -05:00

Owner

Originally created by @doofusdavid on GitHub (Oct 26, 2021).

Hey there! Love this project, and I'm wanting to implement it in our environment.

The Import Backup seems 90% close to what we're looking for. We host a lot of sites. Like 4-500. We maintain a database of all of them which I can use to generate a JSON file that matches your backup. What I'd love is the ability to either monitor a file to auto-update the monitor list, or have a hidden API key I could use to submit the file, bypassing the need to be logged in, and trigger a backup import with the new file I create. Something so that when we have a new site added or deleted, I can have jobs running that would automatically import the newest version of all of our sites.

Originally created by @doofusdavid on GitHub (Oct 26, 2021). Hey there! Love this project, and I'm wanting to implement it in our environment. The Import Backup seems 90% close to what we're looking for. We host a lot of sites. Like 4-500. We maintain a database of all of them which I can use to generate a JSON file that matches your backup. What I'd love is the ability to either monitor a file to auto-update the monitor list, or have a hidden API key I could use to submit the file, bypassing the need to be logged in, and trigger a backup import with the new file I create. Something so that when we have a new site added or deleted, I can have jobs running that would automatically import the newest version of all of our sites.

deekerman

2026-02-28 01:47:50 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@deefdragon commented on GitHub (Oct 27, 2021):

API stuff in general is #118 and I think that that is the proper solution to your problem.

Watching a specific file for changes is a bit niche, and a messier solution if you are already planning on having jobs run to update the sites.

@deefdragon commented on GitHub (Oct 27, 2021): API stuff in general is #118 and I think that that is the proper solution to your problem. Watching a specific file for changes is a bit niche, and a messier solution if you are already planning on having jobs run to update the sites.

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@doofusdavid commented on GitHub (Oct 27, 2021):

You got it, the API is the proper way!

@doofusdavid commented on GitHub (Oct 27, 2021): You got it, the API is the proper way!

deekerman referenced this issue

2026-02-28 02:06:22 -05:00

Add the status page to the backup.json file #987

deekerman referenced this issue

2026-02-28 02:09:18 -05:00