I published a custom app for ZeroNet : https://git.cloudron.io/timconsidine/cloudron-zeronet not yet published to CCAI master catalogue This is based on Zeronet Conservancy repo as the original Zeronot seems to unmainted. I confess that I am far from an expert on Zeronet. The POSTINSTALL in the app dashboard has some links for learning.

@rmdes wow, brid.gy is cool and connecting it all seems like a good marketing start for any project. Thank you for packaging!

Started packaging Mermaid for Cloudron ...

@timconsidine Well done, Tim! Excellent work. I used to think being on Gogs was leading edge. I think I shall have to try moving over to Forgejo like girish.

I wonder how it is compared to LibreChat For the End/Power User perspective; Lobe-Chat is definitely easier to use than OpenWeb-UI

I wait for Akkoma

@robi Well, we use Stripe in the back/end processing for the in-person operations and have no plans to support PP for the POS operations at this juncture. Now, you could use any of the other gateways in place, or in conjunction with Stripe for the web store. That already works. The list of payment gateways, that includes Paypal which ships also with the core, can be found here: https://www.seotoaster.com/website-plugins-marketplace.html. For the hardware you can use either the phone to take contactless payment or one of the basic Stripe readers like https://stripe.com/terminal/m2 if you use an Ipad or Android tablet. The v3.12.0 package supporting the POS will be released next week and the team is preparing the Cloudtron version of that package for you as I'm writing these words.

@girish said in GLPI - Asset and IT Management Software: @vitetj great stuff! I have asked @vladimir.d to look into this so we can get it published. Was there a reason to use LDAP and not OIDC ? https://help.glpi-project.org/doc-plugins/oauthsso ? Also, if we may reuse your work, can you please put in a LICENSE file at https://github.com/vitetj/Cloudron-GLPI ? Any opensource license (MIT, GPL etc) will work. Hey — thanks! On OIDC: the plugin you linked (oauthsso) is not free (it’s available through a GLPI subscription / GLPI Network), which is why I went with LDAP for a default setup. That said, OIDC is definitely on my todo list. There are community/free options we can build on for OIDC SSO, for example: https://github.com/edgardmessias/glpi-singlesignon And yes — happy to help with reuse: I’ll add a LICENSE file to https://github.com/vitetj/Cloudron-GLPI so it can be published/used properly.

@murgero https://forum.cloudron.io/topic/10465/xmpp-server-prosody/44?_=1769150280326 This is the best place to look. I've pushed a repo, I've made a docker image, and I've listed the steps I followed to set it up on my own server. It's been running for over 8 months now and I haven't had issues, other than the workarounds I have to do for Cloudron packaging limitations.

packaging update : basic functionality working further testing needed Will share package and deployment instructions when proven stable.

I have just pushed an update (fixing some ZM UI rendering) latest docker image build : tcmbp132021/cloudron-zoneminder:v2.0.27 Anyone with an existing installation of CCAI-P and using that to deploy : press logout connect import catalogue select Zoneminder and ensure the build is v2.0.27

@girish thanks, I've only just realised the hosted version seems to have disappeared https://linksta.cc/ Indeed it seems nearly all (but not all) instances are down https://linkstack.org/instances/

A small suggestion for formatting your wish list: --- ## **Title**: Flowise on Cloudron - Build AI Agents Visually *** * **Main Page**: https://flowiseai.com * **Git**: https://github.com/FlowiseAI/Flowise * **Licence**: Apache License Version 2.0 * **Dockerfile**: Yes * **Demo**: https://flowiseai.com (Free tier available with 2 flows) *** * **Summary**: Flowise is an open-source generative AI development platform that enables building AI agents and LLM (Large Language Model) applications visually, without coding. The tool offers a drag-and-drop interface to create custom workflows, integration with various LLM providers (OpenAI, Anthropic, Azure, etc.), RAG (Retrieval-Augmented Generation) support, conversational memory management, and multi-tool agent capabilities. It features a modular architecture with Node.js backend, React frontend, and third-party integration components. *** * **Notes**: Flowise is an excellent alternative for those looking to implement AI solutions without complex programming. It offers advanced features such as Document Stores, vector databases (Pinecone, Qdrant, Chroma, etc.), response streaming, and monitoring with OpenTelemetry/Prometheus/Grafana. Supports deployment via Docker, Docker Compose, and includes Redis queue configuration for scalability. The community is active with over 21 contributors to the main repository. Concerns include managing credentials for external APIs and the need for proper storage configuration for data persistence. *** * **Alternative to / Libhunt link**: https://www.libhunt.com/r/Flowise * **Screenshots**: - Official logo: https://github.com/FlowiseAI/Flowise/blob/main/images/flowise.png - Demo GIF: https://github.com/FlowiseAI/Flowise/blob/main/images/flowise_agentflow.gif - Additional screenshots available in the GitHub repository and official documentation *** **Additional Technical Information:** - Default port: 3000 - Supports SQLite, MySQL, PostgreSQL as database - Storage: Local, AWS S3, Google Cloud Storage - Requires Node.js 18.15.0 or higher - Available on Docker Hub as official image

@girish that's good analysis. That's good example of why we need review before adopting it into AppStore. Honestly ... I didn't encounter the issues you raised, simply because I never work in the way that I sign up to the SaaS aspect. I just use the UI, save a PNG or screenshot and throw away the design. Only use it for quick sketches and explainer diagrams. My package was purely to get it off my Traefik/docker-compose VPS onto Cloudron, because might shut down the Traefik VPS. Yes, entirely viable to just use the main website and did that for a while. Should it go in the AppStore ? I don't have a strong view. Others might, because, as you say, privacy issues. But they don't crop up for me in this app.