Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Announcements
  3. PocketBase is now available

PocketBase is now available

Scheduled Pinned Locked Moved Announcements
11 Posts 5 Posters 1.1k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    eddowding
    wrote on last edited by
    #2

    Wonderful - thank you!!

    1 Reply Last reply
    3
    • I Offline
      I Offline
      igaudette
      wrote on last edited by
      #3

      I am following this platform for a while... I am surprised to see it arriving on Cloudron as the dev is planning a big framework code update and the migration will be very complex... That's the main reason why I didn't go with this backend for a project because otherwise, it look amazing!

      How Cloudron plan to manage this big upgrade when it will comes? From what I've read from the founder, the upgrade won't be able to be done automatically and it was too complex for my skills (non-coder).

      From its creator:

      < There will be major breaking changes to the Go and JSVM (pb_hooks/pb_migrations) APIs.
      An upgrade guide listing all changes will be available but it will require users to perform manual code migration steps (only the pb_data will be automigrated). >

      Reference:
      https://github.com/pocketbase/pocketbase/discussions/5543
      https://github.com/pocketbase/pocketbase/discussions/4355

      robiR 1 Reply Last reply
      0
      • I igaudette

        I am following this platform for a while... I am surprised to see it arriving on Cloudron as the dev is planning a big framework code update and the migration will be very complex... That's the main reason why I didn't go with this backend for a project because otherwise, it look amazing!

        How Cloudron plan to manage this big upgrade when it will comes? From what I've read from the founder, the upgrade won't be able to be done automatically and it was too complex for my skills (non-coder).

        From its creator:

        < There will be major breaking changes to the Go and JSVM (pb_hooks/pb_migrations) APIs.
        An upgrade guide listing all changes will be available but it will require users to perform manual code migration steps (only the pb_data will be automigrated). >

        Reference:
        https://github.com/pocketbase/pocketbase/discussions/5543
        https://github.com/pocketbase/pocketbase/discussions/4355

        robiR Offline
        robiR Offline
        robi
        wrote on last edited by
        #4

        @igaudette perhaps look into how the https://pockethost.io guys are planning on doing it.

        Conscious tech

        I 1 Reply Last reply
        0
        • robiR robi

          @igaudette perhaps look into how the https://pockethost.io guys are planning on doing it.

          I Offline
          I Offline
          igaudette
          wrote on last edited by
          #5

          @robi Well if I'm using Cloudron its exactly to avoid relying on other hosting services ^^ but thanks for sharing. Maybe other people could be interested.

          @girish Can you confirm that Cloudron will support the migration/upgrade to 0.23 when this will be stable and released? If yes, than I will install it right away as I have a very good use cases for it. I'm just a bit worried about the code revamp and I couldn't proceed with the upgrade myself. That would be great if Cloudron team could support the upgrade when it will be available and stable. Thanks!

          robiR 1 Reply Last reply
          0
          • I igaudette

            @robi Well if I'm using Cloudron its exactly to avoid relying on other hosting services ^^ but thanks for sharing. Maybe other people could be interested.

            @girish Can you confirm that Cloudron will support the migration/upgrade to 0.23 when this will be stable and released? If yes, than I will install it right away as I have a very good use cases for it. I'm just a bit worried about the code revamp and I couldn't proceed with the upgrade myself. That would be great if Cloudron team could support the upgrade when it will be available and stable. Thanks!

            robiR Offline
            robiR Offline
            robi
            wrote on last edited by
            #6

            @igaudette said in PocketBase is now available:

            Well if I'm using Cloudron its exactly to avoid relying on other hosting services ^^ but thanks for sharing. Maybe other people could be interested.

            Not why I responded.

            Only that they are heavily invested in pocketbase and will also have to have a migration/support plan.

            Conscious tech

            1 Reply Last reply
            1
            • nebulonN Offline
              nebulonN Offline
              nebulon
              Staff
              wrote on last edited by
              #7

              @igaudette version 0.23.* is currently in our testing pipeline, but given that it is currently unstable, we will not spend much time to fixup migration manually if needed, since it is still marked as unstable. So if you want to use it in production, just wait a bit until we have marked it stable.

              I 1 Reply Last reply
              0
              • nebulonN nebulon

                @igaudette version 0.23.* is currently in our testing pipeline, but given that it is currently unstable, we will not spend much time to fixup migration manually if needed, since it is still marked as unstable. So if you want to use it in production, just wait a bit until we have marked it stable.

                I Offline
                I Offline
                igaudette
                wrote on last edited by
                #8

                @nebulon said in PocketBase is now available:

                anually if needed, since

                Okay, but if I install the current version and use it in production.. and the 0.23 with the refactored codes becomes stable in a few months, will you support the upgrade?

                I guess if you added it on the marketplace it's because you planned to support it long-term, correct?

                I think it's a good thing to have PocketBase because Directus is overkill for many projects.

                1 Reply Last reply
                0
                • I Offline
                  I Offline
                  igaudette
                  wrote on last edited by
                  #9

                  I just realized that it's not only a matter of migration... They refactored the API too, meaning that I will have to recode my app. Hmmm. OK

                  1 Reply Last reply
                  0
                  • nebulonN Offline
                    nebulonN Offline
                    nebulon
                    Staff
                    wrote on last edited by
                    #10

                    You can think of "unstable" as published so we gather initial feedback on the packaging. Only once marked stable we will try our best to make it upgradable with new releases. Even that sometimes doesn't work when manual migration is required. For such cases we either disable automatic updates for those apps, or sometimes even have to publish a whole new app package, with manual upgrade steps.

                    I 1 Reply Last reply
                    1
                    • nebulonN nebulon

                      You can think of "unstable" as published so we gather initial feedback on the packaging. Only once marked stable we will try our best to make it upgradable with new releases. Even that sometimes doesn't work when manual migration is required. For such cases we either disable automatic updates for those apps, or sometimes even have to publish a whole new app package, with manual upgrade steps.

                      I Offline
                      I Offline
                      igaudette
                      wrote on last edited by
                      #11

                      @nebulon Okay thanks!

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search