BookStack May 2023 Release Overview | v23.05

Поділитися
Вставка
  • Опубліковано 5 лис 2024

КОМЕНТАРІ • 26

  • @TritonB7
    @TritonB7 Рік тому +6

    Great work, this documentation platform is amazing.

  • @stevedecot7757
    @stevedecot7757 Рік тому +1

    Thx for all ! This's my favorite app ever !

  • @maciejlebiest4976
    @maciejlebiest4976 Рік тому +3

    Great stuff, as a Linux and terminal fanboy I really like the idea of the cli tool. The image management improvements are looking nice too.

  • @ThorstenS-linux
    @ThorstenS-linux Рік тому +1

    nice, I like the cli tool. 🤩

  • @Cesarfish91.
    @Cesarfish91. Рік тому +1

    Hola excelente herramienta!! Tengo la versión 23.05 y quiero actualizar a la versión 23.06 como hago? Lo tengo instalado en Ubuntu 22

    • @BookStackApp
      @BookStackApp  Рік тому

      Thanks! You'd generall follow our update guidance at: www.bookstackapp.com/docs/admin/updates/
      Your BookStack installation would likely be in /var/www/bookstack.

  • @manhunt153
    @manhunt153 Рік тому +1

    Hello Thx for work !,
    Would it be possible to have a web plugin like Joplin to capture and embed content directly into Bookstack?

    • @BookStackApp
      @BookStackApp  Рік тому

      Such a plugin would be possible but not something I'm currently intending to build.

  • @MrMaltavius
    @MrMaltavius Рік тому

    The error on the image uploads looks wonky. I'd expect the filename to be at the top of the window and not have a whitespace there, then maybe the error message would have been entierly visible in the notification without scrollning.

    • @BookStackApp
      @BookStackApp  Рік тому

      Maybe, but since errors are really less expected case I primarily designed around success cases.
      I'd want to keep a fixed height otherwise you can get into different funky side affects where the height is blown out by unexpected long errors, making them harder to deal with.

  • @jok5931
    @jok5931 Рік тому

    What about the upgrade subcommand for bookstack-system-cli ? should we use it ?

    • @BookStackApp
      @BookStackApp  Рік тому

      Yeah, you can try it out. Again, it's in alpha stages so you could come across issues, and it doesn't currently take care of all possibilities (File permission issue scenarios could be common during upgrades). The upgrade command essentially attempts to automate the standard update commands.

  • @christianpreiss8246
    @christianpreiss8246 Рік тому

    in the docker container, bookstack-system-cli doesn't work

    • @BookStackApp
      @BookStackApp  Рік тому

      Are you actually jumping inside the container, to the BookStack install directory?
      The CLI should work inside the container but it might take some time for the various container projects to expose the CLI and added folders, or document it's usage, to make it friendly to use in a docker-based context.

    • @BookStackApp
      @BookStackApp  Рік тому

      @@christianpreiss8246 Ah, alrighty, I might have to check in with the linux server image to see what's going on in that environment. Would expect it to have the required parts but have not yet tested on alpine.

  • @ruuji.
    @ruuji. Рік тому +1

    May 2025? How the years fly by... Great quick overview though! Thanks for your hard work!

    • @BookStackApp
      @BookStackApp  Рік тому

      Oh, did I mess up the year somewhere?

    • @deathbyharakira
      @deathbyharakira Рік тому +2

      @@BookStackApp The thumbnail.

    • @ruuji.
      @ruuji. Рік тому

      Should've mentioned it, my bad!

    • @BookStackApp
      @BookStackApp  Рік тому

      @@deathbyharakira Ah, Whoops! Totally missed that. Now updated, may take some time to roll out though.

    • @BookStackApp
      @BookStackApp  Рік тому

      @@ruuji. No worries, thanks for pointing it out originally!

  • @user-vi8yo9ep3k
    @user-vi8yo9ep3k Рік тому +1

    Finally backup and restore!
    But... Why isn't it tar.gz ? (In documentation used tar.gz)

    • @BookStackApp
      @BookStackApp  Рік тому +1

      I went with ZIP since PHP (Which the CLI is written in) has better built-in support for ZIP, and the ZIP PHP extension is quite commonly ready available/installed.
      Additionally, the CLI backup/restore expect a certain structure of content which will mostly not have existed when following our manual process, so having different extension support somewhat avoids cross-compatibility issues there.