Cloudron Forum

@james that was actually something different, ie changing the link not the logo.

But Girish misunderstood and so his response does still apply here I

In short: seems this option has not yet been implemented upstream.

https://github.com/pixelfed/pixelfed/issues/2802

@SolarSimon I've always just gone to /settings/apps/updates to see available updates for Nextcloud apps amd have never noticed anything about them in
/settings/admin/overview nor anything about "Stable" apps (but there is a "Featured" label on some apps)

Sounds great, thanks for sharing!

Sounds like whilst there is a web app it's mostly a local app though:

Check out the web version even though it is a bit limited: Time tracking only works if the app is open and for idle time tracking to work, the chrome extension must be installed.

I guess it would still be nice to have that on Cloudron

@hollosch so, it doesn't exist, it's just made up by the LLM.

TBH I thought that might be the case.

@james should that day come, sure!

@avatar1024 in short they said yes, then changed their minds and said no again

@SansGuidon said in Upgrading from Ubuntu 20.04 to 22.04 and get errors..:

My 2 cents, I never upgraded the same VM with Cloudron running on it, I just bootstraped a new VM with a fresh upgraded Ubuntu and migrated Cloudron to it ^^ , which allows me to test safely.

Reason: too many topics about problematic Ubuntu upgrades that break things or Cloudron

Yeah, that's mostly what I've always done too. Not sure what I'll do next now that I'm on a dedicated server though...

Might this conceivably be related? https://forum.cloudron.io/post/115812

I just noticed you're both using iDrive

@IniBudi I'd also highly recommend watching this video:

https://videos.cloudron.io/w/206fc4b7-9641-4453-8be0-67450f2574b1

It's quite old, but watching that was how I finally understood how Cloudron works

I made some notes on it here:
https://forum.cloudron.io/post/21183

The good design of Cloudron and the read-only filesystem design stuff is also how/ why Backups, Upgrades, Cloning, Migrating and Restoring apps (or even your whole Cloudron server) also mostly Just Works too!

@girish said in OpenCloud - Secure, Simple & Reliable File Sharing:

I think cubby is actually much better.

Why? in what way?

@necrevistonnezr heh, good point. But I wonder why they don't point people there.

@Beardmann such a request needs to be upstream to Roundcube itself - looks like this is the best place for them https://www.roundcubeforum.net/index.php?board=16.0 (why they don't just use Gitsomething I don't know )

@LoudLemur said in OpenStreetMap on Cloudron:

thanks to @timconsidine, we have facilmaps available on Cloudron

I thought for a moment you meant in the actual Cloudron app store, but alas it doesn't seem we do have it there yet

@hgieldanowski yes, hopefully. And ElasticSearch or maybe Open Search for full text search too.

@hakunamatata too complex and too many moving parts. I think the best we can hope for is some of the features of AIO coming to Cloudron.

@hakunamatata tbh I don't think we'll ever have AIO on Cloudron

@nebulon I think @firmansi is referring to this https://forum.cloudron.io/topic/14359/cloudron-9.0-beta-bug-reports/87?_=1762939432122 (not that that is particularly clear to me)

This is a duplicate of https://forum.cloudron.io/topic/2248/grocy-erp-beyond-your-fridge

Perhaps @james could do some merging

Now I'm wondering if Nextcloud can be configured to use OpenSearch instead of Eleasticsearch!

And it sounds like the answer is yes!

Excellent question — and you’re right to wonder!

Here’s the situation as of late 2025:

---

Nextcloud and OpenSearch Compatibility

The good news:
Yes — Nextcloud can use OpenSearch instead of Elasticsearch for full-text search.

OpenSearch is a drop-in fork of Elasticsearch 7.10, and Nextcloud’s full-text-search ecosystem (the core Full Text Search app plus back-ends like Full Text Search – Elasticsearch Platform) works with any API-compatible engine — which OpenSearch still is.

Nextcloud’s own documentation and issue tracker confirm that OpenSearch works if you’re running:

• Nextcloud ≥ 23
• OpenSearch ≥ 1.0
• The app Full text search – Elasticsearch Platform version ≥ 1.9.0 (latest is fine)

---

️ How to configure Nextcloud to use OpenSearch

1. Install OpenSearch
   (either via Docker, Cloudron addon, or standalone service)

2. Enable the required Nextcloud apps

   • fulltextsearch
   • fulltextsearch_elasticsearch (this works with OpenSearch too)

3. Set connection details in config.php

   'fulltextsearch' => [
       'elasticHost' => 'http://localhost:9200',  // your OpenSearch endpoint
       'elasticIndex' => 'nextcloud',
       'elasticUser' => 'yourusername',
       'elasticPassword' => 'yourpassword',
   ],
   

   or via occ commands:

   sudo -u www-data php occ config:app:set fulltextsearch elasticHost --value="http://opensearch:9200"
   sudo -u www-data php occ config:app:set fulltextsearch elasticIndex --value="nextcloud"
   

4. Index content

   sudo -u www-data php occ fulltextsearch:index
   

---

️ Things to watch out for

• TLS/HTTPS: Nextcloud’s app requires valid HTTPS certificates if the OpenSearch endpoint is remote.
• Authentication: If you enable OpenSearch security, provide credentials via the above config keys.
• Version mismatch: Some users report minor compatibility warnings in logs (harmless) because OpenSearch identifies itself differently, but functionality works.

---

Summary

Feature	Elasticsearch	OpenSearch
Works with Nextcloud FTS
Open Source (Apache 2.0)	(Elastic 2.0)
Multi-tenant security	Paid feature	Built-in
Best choice for Cloudron addon	️

---

So yes — Nextcloud can happily talk to OpenSearch, making it the perfect backend for a Cloudron-style addon that multiple apps (including Nextcloud) could use securely.

Would you like me to show how that addon provisioning could look (so Nextcloud would automatically get its own OpenSearch index and credentials when installed)?

@girish I'd love to be able to use Eleasticsearch on Cloudron so we can have full text search on Nextcloud (because I keep thinking of moving my Nextcloud away Cloudron and search is one of the reasons why - high performance backends and other shiny features that come as standard in the AIO package being other reasons)...

...so I was intrigued by you question and didn't know the response. ChatGPT say:

Right — so what Girish is asking about hinges on whether Elasticsearch supports secure multi-tenancy, meaning:
can multiple apps share a single ES instance safely, with each app isolated to its own dataset (index or namespace) and credentials?

Here’s how that works in Elasticsearch:

---

Multi-tenancy in Elasticsearch

Elasticsearch does not natively provide hard multi-tenant isolation in the open-source (Basic) tier. All indices in a cluster are accessible to any client that can authenticate, unless you’re running a commercial licence (Elastic’s “Gold” or higher) with role-based access control (RBAC) via Elastic Stack Security (formerly X-Pack).

However, you can approximate multi-tenancy in several ways:

---

1. Single cluster, per-app indices (no true isolation)

• Each app gets its own index (e.g. app1_*, app2_*).
• Credentials: You can create separate API keys or users per app if you’re using Elastic Stack Security.
• Without X-Pack security, you can’t restrict one user to only their own indices.
• Simple to manage
• No isolation without paid security features

---

2. Single cluster, per-app namespaces with RBAC (requires paid Elastic licence)

• You create roles limiting each user to their own index patterns (e.g. role_app1 → indices: app1_*).
• Then create a user per app and assign its role.
• True logical isolation
• ️ Requires enabling security features (which are part of Elastic’s commercial licence, not open source)

---

3. Separate Elasticsearch instances per app

• Each app gets its own single-tenant ES container.
• Cloudron would manage these automatically as separate addons (like how Postgres addons work).
• Strong isolation, no need for commercial features
• More resource usage, less efficient

---

4. OpenSearch alternative

If you switch to OpenSearch (the fully open-source fork of Elasticsearch 7.10), it includes fine-grained access control (FGAC) and multi-tenancy features under the Apache 2.0 licence.
That makes it more suitable for Cloudron’s addon model, since you can:

• Create tenants
• Restrict users to specific indices
• Use internal user databases or LDAP for auth
• Do all this without paid licensing

---

Summary (for Girish / Cloudron dev context)

Option	Isolation	Licensing	Suitable for Addon Model?	Notes
Elasticsearch OSS	None	Open source		No way to restrict users per index
Elasticsearch (with X-Pack Security)	Yes	Commercial	️	Technically possible, but licence issue
Multiple ES containers	Full	Open source		More resource-heavy
OpenSearch	Yes	Open source		Best fit for Cloudron addon use-case

---

Recommendation

If the goal is to package Elasticsearch as a Cloudron addon shared by multiple apps with per-app credentials:

• Use OpenSearch, not Elastic’s OSS build.

• Implement addon hooks to:

  • Create an index pattern per app (app_<id>_*)
  • Create a user + password via the OpenSearch security API
  • Assign permissions for that index pattern
  • Inject credentials into the app container’s env vars

That way, the model matches existing Cloudron addons like PostgreSQL: single shared service, isolated logical databases per app.

---

Would you like me to sketch a quick pseudo-flow (in YAML or JSON) showing how Cloudron could auto-provision an OpenSearch user/index when an app requests the addon?