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. Support
  3. Replace custom build with version from appstore?

Replace custom build with version from appstore?

Scheduled Pinned Locked Moved Solved Support
cli
5 Posts 3 Posters 871 Views 3 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.
    • fbartelsF Offline
      fbartelsF Offline
      fbartels
      App Dev
      wrote on last edited by girish
      #1

      Hi,

      with the cloudron cli it is possible to "update" an app that was originally installed from the appstore with a locally built version (by doing cloudron install --app 778fa79a-7f96-418e-8810-b16c1a8a7ea2, where 778.. is the id of the current app).
      But how about going back to the official version? The update action does not seem to support specifying an appstore id.

      One a side note depending on the combination of parameters I get different error messages from the cloudron cli.

      $ cloudron install --appstore-id com.github.xxx --app xxx
      Use "cloudron update" to update an app
      $ cloudron install --appstore-id com.github.xxx
      Location: xxx
      Failed to install app: 409 message: Domain 'xxx.yyy.eu' is in use
      
      1 Reply Last reply
      0
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #2

        Since we separated the install from the update, I don't think that is possible anymore. Before there was quite a bit of flexibility but also magic when it was a new install or an update.

        This also is why the error messages are like this. Previously adding --app would essentially mean updating or more like overwrite that app with this appstoreId or local manifest/build. The update part is now handled by the update subcommand and the install is always a new instance.

        I guess what is missing here is to accept either the appstoreId or the image (which defaults to check for the current folder having a manifest and a corresponding build) for the update subcommand.

        fbartelsF 1 Reply Last reply
        1
        • nebulonN nebulon

          Since we separated the install from the update, I don't think that is possible anymore. Before there was quite a bit of flexibility but also magic when it was a new install or an update.

          This also is why the error messages are like this. Previously adding --app would essentially mean updating or more like overwrite that app with this appstoreId or local manifest/build. The update part is now handled by the update subcommand and the install is always a new instance.

          I guess what is missing here is to accept either the appstoreId or the image (which defaults to check for the current folder having a manifest and a corresponding build) for the update subcommand.

          fbartelsF Offline
          fbartelsF Offline
          fbartels
          App Dev
          wrote on last edited by
          #3

          @nebulon said in Replace custom build with version from appstore?:

          I guess what is missing here is to accept either the appstoreId or the image [..] for the update subcommand.

          yes, that would be nice

          girishG 1 Reply Last reply
          0
          • fbartelsF fbartels

            @nebulon said in Replace custom build with version from appstore?:

            I guess what is missing here is to accept either the appstoreId or the image [..] for the update subcommand.

            yes, that would be nice

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by girish
            #4

            @fbartels Ah, I faced this exact issue the other day (your use case is different, but I wanted a similar CLI option) and made a task for it a week ago - https://git.cloudron.io/cloudron/cloudron-cli/-/issues/56 . Will get to this 🙂

            1 Reply Last reply
            3
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #5

              I have added cloudron update --appstore-id {id} for the next release.

              1 Reply Last reply
              1
              • fbartelsF fbartels referenced this topic on
              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