Thank You! Very informative as ever. Attention for backups is rare, performing a full restore even as a PoC is even more rare. :| This was a really good demonstration.
Thanks, the restore got me out of worryland. I had bookstack installed in a proxmox lxc via turnkey, and wanted to move to debian 12, but was having a hard time. I moved my instance from docker to the my proxmox in lxc as it was faster and thought I had a handle on restoring the database,as I've done it a few times but I got in a jam. Doing the restore as you described worked perfectly. Can I suggest, if possible, make an import/export option in the gui, to import/export, shelves, books, chapters etc.. to try and make moving much simpler??
This is all on my local system, so I've just opened up a local folder like normal in VS Code. In another video (can't remember which), I do connect to a remote server via VSCode which is done via their official remote development over SSH mode and plugin: code.visualstudio.com/docs/remote/ssh
How can we migrate from a script installed version to a docker container? Been working on that for a day now and can't seem to get it restored. Running into issues with the database and .sql file. Is there any easier way to backup and restore within the application? That would be an awesome feature, such as what sonarr/radarr do.
No way to do that in-app. You should be able to restore database data in the same way I showed in the video. A database backup is much the same, whether done in-container or out of container. Feel free to start a support request via GitHub or the project discord with details of the errors you're facing.
Any chance on a nudge to configure SSL based on this setup (not separate NGINX w/ reverse proxy). I'm close but missing something in get docker and bookstack on the same page to use SSL. I'm good with sorting out cert files, just need help with what to change to have an SSL connection listening and responding with docker and Bookstack.
I'm not I see the point of avoiding the addition of a reverse proxy, since this is the common approach and allows centralised management of SSL and routing when you have mulitple services, while allowing flexible HTTPS handling. Therefore it's not something I'd look to cover. The linuxserver image does pass through the nginx config though to the mounted `/config` folder, so it should be a case of also passing port 443, then updating the nginx config to include your cert and use port 443.
really good job! only one question, why db_data and app_data directory, specified with volumes, are created but remain always empty when i run with docker-compose, even i i do an upload? i'm on windows. thanks
I don't know, you should see content in them right away after starting up the containers. You can sometimes get strange behaviour on Windows though, I don't know if local volumes may work differently there. Make sure your content is getting stored though before adding a lot of content, you should be sure your content is safe.
@@BookStackApp thanks, finally i solved the problem, there was some problem with different dir names and path in my mounting (i use solidnerd image version). that you know is it possible to persist the database data as well? I would like to move the committed images to another host without having to do a dump, but only moving the data present in the volumes
@@gianlucabuttarelli9078 Yeah, you should have content in the volume you have mapped for the database container, so `./db_data` in my example in the video. Be sure to properly stop all containers before copying those files though, and don't delete them until you have the new host running, and make sure you use the exact same database container image. Using raw database data, as backup or migration data, is quite risky for a number of reasons, hence why I advise using dumps as per the video, as they are much more portable and less error-prone.
@@BookStackApp Ok clear, however, to do this I would have to identify all the directories where the various files used by the database are saved and this could be a problem, certainly avoidable with a dump as you suggest. If I wants to use another approach, i.e. work on the containers locally and do a whole series of operations, like insert files, images, create books, shelves and pages and then I simply wants to commit everything to the local images and then export them as TAR on the server, and from these to recreate the containers via load, managing however to have the same data inside them that I had locally, is it possible in your opinion? I'm asking because every time I try on new containers that I recreate by running or even using compose (I've tried both), there's always the initial raw data, as if it's always migrating and therefore I always lose everything. I've also tried not using the volumes but I always get the same thing, with or without every time I recreate the images on the server they are virgin again. Thanks a lot for your advice.
@@gianlucabuttarelli9078 I'm not sure I understand this, it sounds like you may be over-complicating things? Files are folders for the database are usually contained in a single directory, as per the `./db_data` (Mapped to the `/config` container path) in my video. You should be able to take your compose config, along with the volume data, then copy/migrate that without issue, as long as you have all the data mounted as volumes.
Awesome, thanks for showing how to make a proper backup and restore.
very useful ! loved the backup/restore parts ! thanks
Good decision. I plan to migrate from Confluence to your Boostack. I really liked it!
Дякую)
Thank You! Very informative as ever.
Attention for backups is rare, performing a full restore even as a PoC is even more rare. :|
This was a really good demonstration.
Yeah, this is so spot on.
Great to also see tutorials for linuxserver ! thanks a lot.
Fantastic video. Very informative for us Docker users.
Please keep them coming 🙏
Excelente video muchas gracias!
Thanks for this video Dan !
Thanks, the restore got me out of worryland. I had bookstack installed in a proxmox lxc via turnkey, and wanted to move to debian 12, but was having a hard time. I moved my instance from docker to the my proxmox in lxc as it was faster and thought I had a handle on restoring the database,as I've done it a few times but I got in a jam. Doing the restore as you described worked perfectly.
Can I suggest, if possible, make an import/export option in the gui, to import/export, shelves, books, chapters etc.. to try and make moving much simpler??
Very usefull info. Thanks a lot
how are you able to get VS Code to "see" the file structure? Are you using some kind of SSH tunnel?
This is all on my local system, so I've just opened up a local folder like normal in VS Code.
In another video (can't remember which), I do connect to a remote server via VSCode which is done via their official remote development over SSH mode and plugin:
code.visualstudio.com/docs/remote/ssh
How can we migrate from a script installed version to a docker container?
Been working on that for a day now and can't seem to get it restored.
Running into issues with the database and .sql file.
Is there any easier way to backup and restore within the application?
That would be an awesome feature, such as what sonarr/radarr do.
No way to do that in-app.
You should be able to restore database data in the same way I showed in the video. A database backup is much the same, whether done in-container or out of container.
Feel free to start a support request via GitHub or the project discord with details of the errors you're facing.
Any chance on a nudge to configure SSL based on this setup (not separate NGINX w/ reverse proxy). I'm close but missing something in get docker and bookstack on the same page to use SSL. I'm good with sorting out cert files, just need help with what to change to have an SSL connection listening and responding with docker and Bookstack.
I'm not I see the point of avoiding the addition of a reverse proxy, since this is the common approach and allows centralised management of SSL and routing when you have mulitple services, while allowing flexible HTTPS handling. Therefore it's not something I'd look to cover.
The linuxserver image does pass through the nginx config though to the mounted `/config` folder, so it should be a case of also passing port 443, then updating the nginx config to include your cert and use port 443.
really good job! only one question, why db_data and app_data directory, specified with volumes, are created but remain always empty when i run with docker-compose, even i i do an upload? i'm on windows. thanks
I don't know, you should see content in them right away after starting up the containers.
You can sometimes get strange behaviour on Windows though, I don't know if local volumes may work differently there.
Make sure your content is getting stored though before adding a lot of content, you should be sure your content is safe.
@@BookStackApp thanks, finally i solved the problem, there was some problem with different dir names and path in my mounting (i use solidnerd image version). that you know is it possible to persist the database data as well? I would like to move the committed images to another host without having to do a dump, but only moving the data present in the volumes
@@gianlucabuttarelli9078 Yeah, you should have content in the volume you have mapped for the database container, so `./db_data` in my example in the video. Be sure to properly stop all containers before copying those files though, and don't delete them until you have the new host running, and make sure you use the exact same database container image.
Using raw database data, as backup or migration data, is quite risky for a number of reasons, hence why I advise using dumps as per the video, as they are much more portable and less error-prone.
@@BookStackApp Ok clear, however, to do this I would have to identify all the directories where the various files used by the database are saved and this could be a problem, certainly avoidable with a dump as you suggest. If I wants to use another approach, i.e. work on the containers locally and do a whole series of operations, like insert files, images, create books, shelves and pages and then I simply wants to commit everything to the local images and then export them as TAR on the server, and from these to recreate the containers via load, managing however to have the same data inside them that I had locally, is it possible in your opinion? I'm asking because every time I try on new containers that I recreate by running or even using compose (I've tried both), there's always the initial raw data, as if it's always migrating and therefore I always lose everything. I've also tried not using the volumes but I always get the same thing, with or without every time I recreate the images on the server they are virgin again. Thanks a lot for your advice.
@@gianlucabuttarelli9078 I'm not sure I understand this, it sounds like you may be over-complicating things?
Files are folders for the database are usually contained in a single directory, as per the `./db_data` (Mapped to the `/config` container path) in my video.
You should be able to take your compose config, along with the volume data, then copy/migrate that without issue, as long as you have all the data mounted as volumes.