Cloudron Forum

This looks lovely. Thank you for requesting it. I hope Cloudron can support it.

@luckow said in CiviCRM | Open source constituent relationship management for non-profits, NGOs and advocacy organizations:

Open civicrm.example.com. Install CiviCRM.
Credentials for mysql -> (easiest way) open credentials.txt in the filemanager

Thanks for this, but I wasn't able to complete it.

For "open civicrm", you can just click on the GLAMP (LAMP) application in cloudron and it will take you to the CiviCRM page.

There were errors which meant the civicrm wasn't installable. I am not sure how to proceed

Could we please have a few notes on how to accomplish this?
Most people, after they install Komga, would like to put some comics on it. What is the procedure? Do we use Cubby, for example, or some other procedure?

@girish said in Dub - an open-source bit.ly alternative for URL redirection:

It seems this requires clickhouse

Via Arya:

"ClickHouse is an open-source column-oriented database management system designed for online analytical processing (OLAP) and real-time reporting. Here are some pros and cons of using ClickHouse: Pros:
High performance: ClickHouse is designed for high-performance querying and data processing, making it suitable for real-time analytics and reporting.
Scalability: It can handle large volumes of data and scale horizontally, allowing for distributed processing across multiple nodes.
Columnar storage: ClickHouse's columnar storage format enables efficient compression and faster querying of specific columns.
SQL support: It supports a SQL-like query language, making it easier for users familiar with SQL to adopt the system.
Open-source: Being open-source, ClickHouse is freely available, and users can customize and extend its functionality as needed.
Cons:
Limited transaction support: ClickHouse does not have full ACID (Atomicity, Consistency, Isolation, Durability) transaction support, which may be a drawback for certain applications.
Not suitable for OLTP: While ClickHouse excels in OLAP workloads, it is not designed for online transaction processing (OLTP) use cases.
Relatively newer system: Compared to other established database systems, ClickHouse is relatively new, which might raise concerns about its maturity and long-term support.
Learning curve: Although it supports SQL, ClickHouse has some unique features and concepts that may require users to invest time in learning and adapting to the system.
Limited ecosystem: As a newer system, ClickHouse's ecosystem of tools, integrations, and third-party support may not be as extensive as more established databases."

Fantastic!

@andirahmat said in Open Journal System (OJS):

Hi. Great work on getting Moodle app @atrilahiji
I would also suggest Open Journal Systems if you mind to take a look https://pkp.sfu.ca/ojs/

Here is example : https://ojs.akbidpelamonia.ac.id/index.php/journal

This is much needed in higher education institution i know for lecturer for peer review their journal/publication. University here in Indonesia always use it together with Moodle for knowledge management apps.

https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request

@WilliamNagel said in Unmark - An open source to-do application for bookmarks:

https://github.com/cdevroe/unmark
https://unmark.it/

https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request

@Grienauer https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request

Update to Cloudron 8.2 went smoothly. Thanks everybody!

Some substantial updates to the Peertube GUI:

https://joinpeertube.org/news

@girish said in LibreChat:

There's many apps in the pipeline already

Gotta love you for that pipeline, @girish!

@girish said in LibreChat:

What's the difference between opebwebui and librechat?

LibreChat is supposedly more difficult to deploy than OpenWebUI. In which case, Cloudron would be able to add greater value by easing deployment of LibreChat.

Here is a quick summary via Grok:

"Here's a comparison between LibreChat and Open WebUI based on the available information:

Open Source:
LibreChat: Yes, LibreChat is open-source, available on GitHub. It uses an MIT license, allowing for free use, modification, and distribution.

Open WebUI: Also open-source, with its code available on GitHub. It uses the Apache 2.0 license, which is similarly permissive.

Development Activity:
LibreChat: It shows active development, with regular updates and contributions from the community. It's noted for integrating with numerous AI providers quickly after their launch.

Open WebUI: Has a healthy development pace with frequent commits and a focus on enhancing user experience and adding new features. The project's community seems engaged, with various pipelines and integrations being developed.

User Base:
LibreChat: While specific user numbers aren't detailed, it's popular among those looking for a customizable, enterprise-level AI chat interface, with a focus on privacy and control over data.

Open WebUI: It's gaining traction for its ease of setup, user-friendly interface, and extensive features, particularly among those interested in self-hosting AI with control over their data.

Docker Support:
LibreChat: Offers robust Docker support for easy deployment, making it accessible for those familiar with containerization.
Open WebUI: Provides a Docker-based installation for both CPU and GPU environments, simplifying setup and deployment.

Supported Features/Models:
LibreChat: Features include AI model switching, conversation branching, multimodality, and integration with various AI services like OpenAI, Azure, Anthropic, and Google. It supports RAG through integration with RAG API.

Open WebUI: Known for its versatility, supporting models from Ollama and OpenAI-compatible APIs, with features like custom RAG, message monitoring, user rate limiting, and real-time translation. It also allows for the creation of custom models and real-time web browsing capabilities.

Retrieval Augmented Generation (RAG):
LibreChat: Integrates with RAG API for uploading files and asking questions, enhancing its capability for document-based Q&A. However, it lacks advanced file management features.

Open WebUI: Offers an integrated RAG process that works well for small-scale document interaction, although it's noted to be less scalable for larger sets.

License:
LibreChat: MIT License.

Open WebUI: Apache 2.0 License.

Pros/Cons:

LibreChat Pros:
Enterprise-level authentication and flexibility.
Supports a wide variety of AI models and services.
Strong focus on privacy with data retention control.
LibreChat Cons:
Configuration might be more complex for some users.
Lacks some of the administrative controls found in Open WebUI.
Open WebUI Pros:
Streamlined user management with a user-friendly interface.
Strong support for custom integrations and pipelines.
Excellent for those looking for an easy-to-set-up AI interface.
Open WebUI Cons:
Less granular user management compared to LibreChat.
RAG implementation might not scale well for large document sets.

Both platforms serve different needs, with LibreChat leaning towards enterprise solutions and Open WebUI providing a more consumer-friendly setup with robust community support. Your choice might depend on your specific requirements, particularly regarding ease of use, control over AI models, and data privacy.
"

https://bitwarden.com/download/

If we have Komga supported on Cloudron, we could try and have that mentioned as an official installation method on the Komga documentation. That might help more people discover Cloudron and enjoy their comics with Komga.

@eyecreate said in Komga on Cloudron - A media server for your comics, mangas, BDs, magazines and eBooks:

I've made a first build of Komga for cloudron:
https://git.eyecreate.org/eyecreate/cloudron-komga
I didn't know if it was worth setting it up with OIDC, but otherwise should be fully usable.
I also included kepubify to help make more compatible with Kobo devices.

Hey, that is wonderful! Thank you for packaging this. @girish might we be able to put komga into the unstable to encourage people to test it?

@eyecreate What prompted you to package Komga? Was it a fun experience? Any problems with the documentation? Now that you have completed Komga, do you think you might like to try packaging another application? Do you think you will suggest that your friends try packaging, too?

@humptydumpty said in Cloudron email Server - multiple domains:

No ugly. Set up the Cloudron. Use mail.cheapo.com as the mail server. Add the domain cheapo.com in CR dash under domains. Create mailboxes like Alice@cheapo.com and have folks access it through snappy.

If manual dns, don’t forget to set up records for spf, dkim, and dmarc.

Hey, thank you! Would it matter what domain was used for the registration of the cloudron in this case? For example, could I setup the cloudron with the name e.g. anythingwilldo.com (rather than as I had originally suggested using a subdomain of cheapo.com), register that with cloudron.io and then do the important part of configuring the mail server for anythingwilldo.com to be (in this case) mail.cheapo.com and in the cloudron dashboard add cheapo.com as domain?

I really am amazed at you all. You are quite awesome in your ability to keep these complexities clear in your mind. I find it difficult to even phrase the issues let alone understand them.

Let me try this and hopefully somebody will be able to help me:

There is one server over there (not a Cloudron) doing its own thing, but without individual mailboxes for people, because of the costs. Lets call it cheapo.com

Purely (initially anyway) to help solve cheapo's lack of emails problem, we have this idea: setup a new server on a completely different VPS, a cloudron, on a sub-domain of cheapo.com, for example mail.cheapo.com

Would we be able to do that? Once it was up and running, then setup snappy and give everybody in cheapo.com email addresses? e.g.

alice@cheapo.com
bob@cheapo.com
charlie@cheapo.com

or would the email addresses need to have some "ugly" appearance, like:
alice@mail.cheapo.com
or something like that.

@Kubernetes said in Cloudron email Server - multiple domains:

Yes, this is a possible setup. What exactly are your concerns?

Hey, kubernetes! Thank you for looking at my post. (I hope I am not distracting you from packaging applications!)

One concern would be whether the example.com would start appearing in the email headers for mail sent by alice, bob and charlie.
Another concern would be how to allocate a, b and c an email passphrase.

Also, what would be the situation with the idea.com domain name provider? For example, if one wanted a "backup" paid email account with the provider (in this case porkbun) would it conflict with having a, b and c hosting their emails on the cloudron?

Actually, if you had a paid email box for that idea.com domain with porkbun, would you be able to use that to provide all the a, b, c email boxes you need? e.g.

• porkbun paid mailbox: everything@idea.com
• everything.alice@idea.com
• everything.bob@idea.com
• everything.charlie@idea.com

Would the following be possible on Cloudron, or even desirable:

• Register domain with e.g. gandi: example.com
• Setup cloudron server at e.g. linode
• Cloudron account is found at: my.example.com
• Setup email e.g. snappy mail at: snappy.example.com
• register second domain with e.g. porkbun: idea.com
• create mailboxes on the cloudron for e.g. alice@idea.com bob@idea.com charlie@idea.com

@syben https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request