-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Support: How to restore accidentally deleted docker-compose.yml
file
#1436
Comments
No special procedure is needed to recover if your data/ folder is intact, simply restart the container with the same version you were using before and it should start up as usual. (Don't use |
Great, thanks! And what about moving ArchiveBox to another server? That's why I'm trying to re-enable it first, just to ensure everything is properly archived. |
Nothing special needed, just move the |
Nice, thanks! But I'm still can't enter to the instance in order to verify if everything is OK. How can I deal with this, when there is no
I tried to modify Archivebox.conf adding the variable PS: I'm archiving public pages so I don't need websites login credentials. |
It looks like you're on an unstable dev build, can you change the |
Unfortunately, I lost my Thank you again. I'm also moving the files to a new instance, which might be enough. |
The container itself is ephemeral, there is nothing kept between runs other than whats in You can simply re-download the There is also lots more info on this subject available here, maybe it's helpful: |
docker-compose.yml
file
I accidentally removed my docker-compose files. While I can start from scratch, I have many archived pages that I want to preserve and transfer to my new instance.
What's the best way to achieve this?
My container is currently resetting itself due to missing Chrome credentials. However, I believe the archived files are still present, as I haven't deleted the Docker library folder or the persistent data bound in the docker-compose file.
The text was updated successfully, but these errors were encountered: