Topics created by nebulon

@robi said in Cubby - Open Source File Sharing:

@nebulon said in Cubby - Open Source File Sharing:

@robi ha, yes lots of placeholder content still.

For anyone interested in the collabora integration, if you install collabora on the same Cloudron and then edit the config.json for cubby like the following with your collabora domain, it can already open ods and odt files:

{ "collabora": { "host": "https://office.example.com" } }

Does this not work with OnlyOffice?

OnlyOffice uses a different kind of API and iframe integration, which is currently not implemented. I've created a feature request for this at https://github.com/cloudron-io/cubby/issues/18

@jeau I started to explore OmekaS and created an instance for testing.
I just wanted to say THANK YOU for a really impressive piece of software. 👍 👏 👏 👏

@atrilahiji said in Cannot reach backend server:

So this appears to be an issue on Firefox rn that has been reported on their forum.

https://community.n8n.io/t/connection-lost/1471/49

Using a chromium based browser seems to be fine in my testing.

Edit: This post seems to have a suggested solution via the NGINX config https://github.com/n8n-io/n8n/issues/36#issuecomment-539647882
@nebulon @girish

The mentioned fix is already active.
See https://git.cloudron.io/cloudron/n8n-app/-/blob/master/pkg/nginx.conf#L64
But the issue persists.

Additional information: There is no API_Secret in the ENV file in the standard app package. Depending on your thousands of clients, it takes some time to migrate. For me, it was done in less than 5 minutes.

The only moment of confusion was: when installing IN v. 5. you have to fill in the name of the company in a modal frame. After the migration it took me a few seconds to realise that there is a multi-company option in IN v. 5 and I had to switch to the "other" (migrated) company (which has the same company name).

It looks like everything has migrated well.

ah great thanks for the explanation and details. Good for other users if they hit the same issue/question.

@imc67
yep, @girish fixed in seconds, like a superhero! was an issue with the system link in rsync, and I discovered the output of the error was on the app log file, not on the container that's why we couldn't find anything on the log in Cloudron initially.

If you have a Dockerfile, you can package custom apps for deploying on Cloudron. No need to add/change nginx entries etc. Please see https://docs.cloudron.io/custom-apps/tutorial/

I will remove the apt installation and make it npm installation because that's what upstream recommends - https://classic.yarnpkg.com/en/docs/install/#debian-stable

Effectively the UK can now do what Jersey (where I live and has always been outside the EU) has done for years.

Europe I LOVE! The EU, well, we'll leave that for the remaining members to decide what works best for all — which I expect still needs some work given the variety of economies and industries.

Anyway, not to distract — great job being on top of the accounting!

@mehdi yes we now decided to simply not have anonymous contributions there, but for anyone interested, just send us a mail with the intended username and language to contribute to. I've also updated the docs accordingly.

My 2 cents about this: it would be great to be able to do this but only for a specific port of a certain app. Like, keeping the web interface accessible for all, but limit access for a given tcpPort.

Bonus points if limiting access to clients accessing from openVPN server is automated 😛

Did not know this was existing till now... thanks man

I didn't even see this on the App Wish list, this is really cool. This is yet another one of those apps I could never get running on a VPS for my general use. Super work! Thanks to all involved.

@murgero I thought your comment was good, in fact 🙂 Because @nebulon said, don't update Cloudron (but it doesn't affect existing installations). I will edit his post.

This app is now marked as stable in our library! Thanks @BrutalBirdie for all the hard work!

If issues are encountered please report them as usual in the app's forum section.

@mehdi said in Documentation url change:

(By the way, didn't you guys do the reverse URL move like a year ago or something ? ^^)

I think last time around we tried to split the developer docs (into /developer) and the user docs. That went poorly since people were constantly struggling to find the developer docs. Lesson learnt and we ended up merging them again.