mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-10 19:06:16 +03:00
Info request : backup #4490
Closed
opened 2026-02-05 08:59:34 +03:00 by OVERLORD
·
5 comments
No Branch/Tag Specified
development
l10n_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
No Label
🔨 Feature Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#4490
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @eleo56 on GitHub (Feb 27, 2024).
Describe the feature you'd like
Hello everyone,
I've read quite a few posts on the subject of backups and exports. However, I'm a bit lost.
Our goal is to be able to retrieve pages sorted by book, which in turn are sorted by shelf.
Does the organisation of the server allow this?
According to post #2405 this is possible (?)
Is a backup possible?
According to post #2405 this is possible (?)
If Bookstack no longer exists, is no longer maintained or anything, will our data be recoverable with this organisation?
Describe the benefits this would bring to existing BookStack users
Bring more clarity...
Can the goal of this request already be achieved via other means?
I don't know. These are probably very naive questions, as I don't have access to the server.
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
3 months to 1 year
Additional context
No response
@ssddanbrown commented on GitHub (Feb 27, 2024):
Hi @eleo56,
What exactly do you mean by that? Just trying to understand how exactly your goal is related to backup/export.
@eleo56 commented on GitHub (Feb 28, 2024):
Hi Dan,
Indeed, i wasn't clear.
We have important content in Bookstack that we don't want to lose under any circumstances, whatever happens:
a- If there's a bug/crash in our Bookstack
b- If we decide to migrate our content from Bookstack to another program;
c- If we want to export the pages : having one PDF per page with a single click, and not the whole book in a single PDF file.
d- If Bookstack no longer exists or is no longer maintained
If one of these cases occurs, we want to be able to retrieve the sorted content in the same way as in Bookstack at present (Shelf > Book > Pages). Except for d, there would be no shelves.
So I asked myself several questions:
How do you make a backup? There's already information on this and I could pass it on to the technical experts: #2405 . However, I'm not sure I've understood: is the organisation of content also saved (Shelf > Book > Pages)?
How can we easily migrate our content? It all depends on the software you choose. Let's leave that aside for now.
To simply export all the books into a folder, there's already some information : https://gist.github.com/ssddanbrown/45acb913a7b873240b2d89781e74a7a4. But not but not for exporting an entire book as a PDF per page (with a single click)-->Could you tell me if this is possible?
What happens to our content if Bookstack no longer exists/maintained? Will our content still be on our server? I haven't found any answers. (I suppose this is a naive question as we are the hosts, but I want to make sure).
If there's any more recent information than I've mentioned, please don't hesitate to let me know.
Thank you and have a nice day
Eléonore
@ssddanbrown commented on GitHub (Mar 6, 2024):
As long as you're hosting the instance (and connected database), then all data is on your system.
I've had a few queries recently regarding the content storage format, and its portability. To help make this information clear, I've added some guidance to our website here: https://www.bookstackapp.com/docs/admin/content-storage/.
There is no in-built button to export all books (or multiple books) as PDFs within the UI. You'd have to view each book and click the "Export > PDF" option. Just to confirm on this though, PDFs are a copy of the content, but are not a backup for BookStack at all. They cannot be used to directly restore back into BookStack.
If you did go down the script route, I have a slightly more maintained version of that in our api-scripts repo here: https://github.com/BookStackApp/api-scripts/tree/main/php-export-all-books
That page you linked is a feature request discussion, so I can't advise following guidance there for maintaining your BookStack instance.
We have guidance on creating instance backup & restore here:
https://www.bookstackapp.com/docs/admin/backup-restore/
Following that guidance, everything in your BookStack instance will be backed-up.
There's also the newer System CLI which can help automate some of this, although that's in alpha-state. Either way, backup and restore should be tested.
Note: The exact steps may depend on how you install/run BookStack. If you're using something like docker to run BookStack, the backup steps & considerations could look quite different.
If possible, I'd usually advise also performing a system level-backup also (system snapshot, or disk-level backup).
@eleo56 commented on GitHub (Mar 6, 2024):
Thank you Dan for all this informations, I'm going to talk to the technical experts.
Have a good day
Eléonore
@ssddanbrown commented on GitHub (Feb 25, 2025):
Since there's been no further follow-up, and since the original questions have been answered here, I'm going to go ahead and close this off.