tmpfs support in the manifest
-
@robi
OLS, for what we have tested is not good as nginx as container proxy, especially because nginx have push this as his main features.If u use Docker/Kube, and you want the max from your stack, just go on nginx.
There are good proxy on the market especially for API, but nginx proxy cache can be use to speed up, not only json file, and standard API request. But also image, js, css, html ecc eccThat make nginx the king of general proxy for container environment (and it can be use to proxy request to FPM directly no webserver needed inside of the container)
-
@MooCloud_Matt said in tmpfs support in the manifest:
@robi said in tmpfs support in the manifest:
Would love to see OLS used here.
we have OLS ready in beta, just working with cloudron to have 3° party app on the store with a custom license.
We want to use something like a Commons Clause + Apache or Prosperity Public License, so that user can use it, and can read the code and if you want collaborate too, but Cloudron don't need to maintain it.Love this idea. I think they maintain between both of them (@girish and @nebulon) way too many apps already. It’s incredibly impressive, but a 3rd Party App on the store would help with that.
I wonder how that would be implemented. My personal suggestion would be a
Feature Request
for `The App Store code to allow for adding external JSON libraries of new apps since that’s all the current store is right now, only supporting a first party source, Cloudron’s.I think adding custom app
sources
would benefit both developers and users alike, but we’ll have to see how they feel about it since it’s their platform. -
@MooCloud_Matt said in tmpfs support in the manifest:
Prosperity Public License
This would mean it would be forbidden to use this app for commercial use. It would just be a trial.
I must say, I for one am not thrilled to have such apps on the app store.
The Commons clause is still not great, but better.
-
I’m against any licensing that limits use of an app. But I’m for 3rd party persistent sources in the Cloudron App Store. Only tech people will realize it’s a thing, and we’ll always get to be on the bleeding edge. It would also make beta testing new converted apps much easier if the App Store had the ability to add custom
sources
of apps leading to a simple file in JSON format with all the data of the new app or apps. -
@mehdi
In our case, end customer can use it, even in 3° party cloud platform, but can't be use in a SaaS like solution or used ad Selling Point for competitors.If it will be impossible to have custom license on the app store we need to offer those image just to our customer, optimizing a image like that one of OLS or the new image with Nginx take a lot of time, and they have our knowledge inside of them.
Big software that use similar license: Redis, MongoDB
-
@MooCloud_Matt I just realized I could use LDAP to simply grab an
access_token
and create my own Cloudron Alternative App Store for devs. -
@Lonk
you mean for a private docker registry ? -
@MooCloud_Matt said in tmpfs support in the manifest:
@Lonk
you mean for a private docker registry ?Though I could do that yes, I was speaking more in terms to an actual alternative App Store, private or public registries wouldn’t matter. I’d probably originally make it only public registries at first.
Like, I’ve been wanting to create Dot the Repair Bot Cloudron app but it’s more of a Cloudron add-on and probably doesn’t belong in the official store (maybe, not sure). But if it didn’t and I still wanted it to be accessible - I could build an alternative App Store with the
docker
add-on and put apps on there.Orrrr, the official App Store could gain
sources
in which case I would just host a JSON file on BackBlaze and give people thesource
’s URL to use and it would pop up in the store as a third party app.It would make beta testing apps with people wildly easier if the Cloudron App Store allowed for more “app sources” than just its hard coded internal source that @girish and @nebulon maintain alone.