@avatar1024 A lot of the same thought process as here, on block vs file sync.

https://www.enterprisestorageforum.com/storage-networking/nas-vs.-san-differences-and-use-cases.html

"SANs are the higher performers for environments that need high-speed traffic such as high transaction databases and ecommerce websites. NAS generally has lower throughput and higher latency because of its slower file system layer, but high-speed networks can make up for performance losses within NAS."

Here is the thing, Nextcloud is half baked on just about everything outside of file sync. I'd be VERY wary to trust it to handle external syncing. It might be easy to setup, but you're betting on their external storage plugin working as advertised under all conditions.

An interesting idea to be sure!

FWIW, I filled yet another form now to get a response from them. 🤞

@d19dotca Thanks for the write up, I will repurpose it for some our docs.

Another user had actually informed us about this and it's been working reliably for them. So, we already had added OVH storage in the backups UI for the next release.

357c53be-e4aa-4bcc-8cac-b8d7d543e388-image.png

I can attest that it is definitely NOT a good idea to add more Docker images to a CR box outside of CR. CR assumes it has full use of the box, so, anything additional you add can and possibly will break things 🙂

It basically means it's in Beta ^^

OK, @Trankery informed that this happens more most/all freenom domains. This includes .tech as well.

@girish Will do. It's actually not the first time I've run into the problem and a re-fresh of the API credentials solved the problem, although this is the first time I specifically observed that it was a 500 error vs. a 401.

@Hillside502 yes, that was a ui bug!

That makes sense. BlobFuse is what MS uses for Azure and it is definitely, not amazing.

@nebulon Oh! That's awesome, thank you for being patient and clarifying that for me. I appreciate it. So I see that now, it looks like if I'm reading it right it will only run that part to deploy the plugins if that directory does not already exist, and since it will exist of course then it would never be executed. Makes sense. Thanks again! This definitely helps, I appreciate the education on it too. 🙂

@yusf ah

It's a shame no one from OnlyOffice actually explains why they "HAD" to remove mobile editing.

"The fact is we HAD to limit the mobile web version feature since the question is about the future of ONLYOFFICE."

Also learned something on that thread about how apparently collaborative editing won't work with mobile app version 😐

@nebulon You are all doing amazing work, thank you!

Oh, I’m glad to hear it. Either they did rely on AWS at one point or I got it backwards completely. Either is fine if they now have their own infra. 🎉

@jdaviescoates from what I understand Chatbot fall under Social Network Login or OmniChannel Integrations which are only available under SaaS and/or with a license, which I'm not sure or to deal with via Cloudron since you have to contact them and they talk about docker deployement.

@yusf said in Who want to share recipes ?:

Botpress app request here 😁

I tried botpress almost 2 years ago, it was already pretty impressive and intuitive.

for the Rocket.Chat / BotPress it seams to be in development

@girish really great to see Freescout is a WIP, my local Covid 19 mutual aid group are interested in using it...

@hendrikvl said in sender rewriting when using external SMTP:

And no, my mail relay does not accept IP whitelisting. It's not a proper mail relay service to be exact, but just a regular mail service with outgoing smtp for authenticated users.

Ah yes, someone was trying to do this with a gmail account as well sometime back (and more recently with a mailbox.org account). I think we have to implement this feature in Cloudron to make this use case work.

@RoboMod Thanks for the script and @ruihildt thanks for the suggestion. We will look into this in a coming release. It makes sense to keep them in sync. I have long wanted better backup rotation policies as well - https://git.cloudron.io/cloudron/box/issues/441

I would say:

Learn docker. This is the base deployment tool for Cloudron. No need to learn compose/swarm etc. Take some time to learn Heroku. Also see 12 factor app. A lot of ideas for Cloudron app deployment are inspired from these two PaaS concepts. Heroku can deploy lots of different frameworks/stacks, so just pick one you are comfortable with. And then the tutorial link above should be easy to follow. Without knowing 1 & 2, the tutorial can be hard to understand.

Finally, there is lots of code at https://git.cloudron.io/box (looks for -app suffixed repos).

@rfg You have to setup a mail relay for your outbound mails. The big cloud providers like aws, gce, azure will all block emails from VMs directly. See https://cloudron.io/documentation/email/#relay-outbound-mails

@JOduMonT Yeah I came down too harshly, sorry my friend!
Any question is worthwhile when the intention is good!

@girish this all sounds great - looking forward to the next release! 🙂

It would also be really nice if there was a simple way to limit the visibility of apps by domain (perhaps using groups?).

I realise that at present it's possible to create groups and then limit access to specific apps to specific groups, and that could be used now to achieve this, but I'd like a quicker and easier way to say to Cloudron: "this group has access to all apps on this domain" (but none of the other domains) than having to do it app by app.

Make sense?

We are quite attached to hastebin since it's one of the first apps that we packaged on Cloudron 🙂

For mail client, I use thunderbird on desktop and k9 on android. I use rainloop to setup filters. The thunderbird managesieve extension is not the best.

@girish said in I believe in Cloudron's mission 200%. How can I help?:

what the issue is here

sometimes warning are only to warn you such as asking you to take a look, often if you able to explain why it's like that and it sound reasonable from a security perspective it's fine.

The grub and kernel issues (which are the bulk of it) are outside the scope of Cloudron especially on a VPS.

I also don't applied all recommendation because it restrain too much the instance such as an example it will be impossible to login as root from the console unless you reboot at the level 1