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


Skip to content
  • Backup import fails on new Cloudron instance

    Solved Support
    16
    0 Votes
    16 Posts
    902 Views
    girishG

    @yusf OK, thanks, when you find time, feel free to reach on the support mailbox.

  • Trouble importing mongodb data to Rocket.Chat

    Rocket.Chat
    10
    2 Votes
    10 Posts
    2k Views
    girishG

    @robw @alex-adestech An update on this.

    Crux of the issue is that the indices name generated are too long. @alex-adestech pointed out to me that this issue only sorted out in MongoDB 4.4 and not even MongoDB 4.2. Searching through the rocket.chat issue tracker I saw only person hit this and nobody replied. Search further, I found that Rocket.Chat doesn't even support MongoDB 4.2. The releases page mentions the versions they test with - https://github.com/RocketChat/Rocket.Chat/releases. This got me wondering why we hit this issue. Well, the answer it turns out is that Cloudron generates 32 byte mongodb database names for apps. This in turn ends up affecting the length of the index.

    I have made a fix now for Cloudron 5.6 that generates shorter names. (We have had to do something similar for apps using MySQL as well in the past).

  • 2 Votes
    16 Posts
    6k Views
    L

    Never used Git, will keep that in mind for reporting any issues that I might come across with Cloudron apps!

    Now that I know that shared volumes is what I'm after 😜 (I thought it might be different somehow if it was a specific permission for an app to read data outside of it's docker container), how can I set up and use a shared volume if it's not exposed on the interface? Or is this something that's not trivial and best left alone till it's stably implemented?

  • Redmine database?

    Solved Redmine
    8
    0 Votes
    8 Posts
    1k Views
    girishG

    I have added a clear section in the guide - https://cloudron.io/documentation/guides/import-mysql/#import

  • Strange email folder naming behavior/errors

    Support
    6
    0 Votes
    6 Posts
    709 Views
    girishG

    BTW, for the "dot" thing, the mailbox separator in Cloudron is ".". This is why folders with dot don't work. If you create a folder named "foo.bar.baz", it is like subfolder bar under foo and subfolder baz under bar.

    While using "." as a seperator is not a bug as such, using "/" as a separator instead of "." would have been a better choice for Cloudron but we didn't know this when we started (sadly, "." is the dovecot default too). And also using "/" as separator is required for mailbox sharing to work. We are slowly working towards moving the separator to be "/", step by step.