This appears to be S3 compliant, so I guess the generic S3 backend in Cloudron already would work?

@infogulch I think that's doable. I'll see if I can get it working.

@d19dotca we don't know yet when 7.2.1 will be out. If you need the change immediately, you could just adjust the value directly in the code and restart the box daemon. Usually patching the code like this is not recommended, but in this case the change is rather small and will not cause any issues on update later.

@plusone-nick said in Select resources on app creation:

Its nice that every app has its on min requirements set but it would be helpful to be able to select any additional resources upon creation, mainly memory/RAM

Yeah, I'd like this too, mostly because in my experience apps often need more RAM than the minimum. Personally I'd like to just go for double the stated the minimum as a rule of thumb and it'd be nicer if I could set that during app install.

Thank you! Wait and see then ..

@Jeyakumarrathnaselvi said in Search typing issue - page get refresh while typing:

example if i type abcdefgh. it shows only abcdfg. e and h miss while page refresshing

where do I have to test this to reproduce this bug?

ok thank you wait and see then...

Yunohost, for one, does allow an admin to see ALL the possible apps available for installation, BUT they categorize these apps by reliability and stability. 682f4dc1-c041-426a-b147-8313a8c275c1-image.png

Could the same idea/process be adapted for a Superadmin to "categorize" Cloudron App Store apps, making only certain ones visible to the next level Admin. Come to think of it, a Reseller account on MXRoute allows the Superadmin to do exactly this - create a Package, name it, define it's parameters, and allow the Customer the option to choose from the prepared Packages. The Customer never really knows if you've overbooked the VPS or not, or if "better or stronger" options could be available - they only see what the SuperAdmin has packaged as choices.

So, the SuperAdmin would need a way to create a Package, and then assign specific App Store apps to each Package.

In fact, a similar process must already be in use for Cloudron, because only those apps that are "ready" are in the App Store (and even then some are labelled as Unstable)! So, can that be tweaked to let a SuperAdmin make visible only those apps being offered?

I'm babbling on now. Time for bed.

EDIT: I guess the same ability to tweak (using APIs?) could also make the SuperAdmin visible or not in the Admin's Dashboard User list; or hide it from the users in the User List.

Where is this slated release wise?

This is implemented in 7.2.1.

https://community.torproject.org/onion-services/setup/install/ src install at the bottom of the page.

Seemingly would need a front end to show the onion address to copy and use elsewhere.

Hi @pratik, I made the manual payment using the invoice statement, that I got on my email address...

@jimcavoli yes, please 🙂 I will be happy to get this integrated. I think I have addressed the platform issues in the releases since.

@doodlemania2 registration is almost always disabled by default. But some apps like Kutt won't allow anyone to sign up, if registration is disabled.

@girish said in Hiding superadmin to deliver 'managed' cloudron to clients.:

@micmc said in Hiding superadmin to deliver 'managed' cloudron to clients.:

And I guess, that is what would or should happen if we choose to hide the owner. I haven't thought really about this one but yeah, well thought and that should the be case also indeed, the superuser would not be seen in apps as well.

We had this idea of creating a "service account" - https://git.cloudron.io/cloudron/box/-/issues/771 (which is scheduled for 7.3). I think this will get you this feature.

This is how we see how great minds encounter! 😛

Also, there's the discussion about the "email admin" role to which your issue above refers too as well, which several of us have followed as well, which have popped several ideas and views as well and has brought to the creation of such feature.

The API style in Cloudron you are referring to is commonly called REST API, although Cloudron does not strictly follow REST patterns. It can be used with a multitude of clients. Some are libraries to be used withing other programs and they exist for all programming languages by now I would guess. Some other clients are browsers or also commandline clients like CURL.

I think it might help you a lot to read up about REST APIs which should clarify things for you.

Just a simple example, without an access token (so using just public API), run the following on a terminal with curl installed: