Cloudron Forum

@SansGuidon good stuff i agree with the approach and sentiment
have you tried bolt.new or any other code assistant that can better generate? I know chatgpt recently added that canvas...but being able to have the ai be aware of the whole project context is right around the corner making this 10x easier. bolt.new has their OS version bolt.diy and can interface with all the usual llms, check it out if you haven't
This whole situation has basically forced me to be a better admin and learn to be a dev so cant really complain, just advocating for more facilitation

@scooke Aww Shit - CJ meme? or what do you mean? we aren't going anywhere, literally lol

pretty sure it has to be via ssh if your app is outside of cloudron
*nvm i now see you're going out from cloudron

imo the main issue in regards to new apps is the developer experience/on-boarding

Cloudron has had their own "standardized" method for packaging apps for many years now and have basically failed in facilitating a thriving marketplace for Open Source and new custom apps. Way before Supabase, Coolify and others "We"/Cloudron have had: Server/Runtime, Auth, DBs, Backups, DNS & so on readily available with absolutely no streamlined method to build an app using Add-On pieces and simply launch it.

This is the extent of it besides the docs

And don't get me started with the fact that we still don't have a single "no code/low code" APP/PAGE builder! No lie it makes me lose sleep at night...We can design a UI with Penpot, build databases with several options, build workflows with n8n, do AI stuff with Typebot/Open WebUI but I only have fucking wordpress to build a page!? (excuse my french & no offense WP but really!? it's basically 2025!!)

Ive been using Wappler over the past 4 years or so and even went as far as contracted a forum member Mitchelle to package the NodeJS app that Wappler outputs into a Cloudron package after trying and struggling for far longer than I'd like to admit. https://git.cloudron.io/murgero/wappler_app
Currently and Finally I have a decent tech stack that isn't missing a core/fundamental feature where I can have the assurance I need to build for and support clients but it could certainly be way more integrated than it is.

Note: Wappler is not open source but does use an open stack and you own the output source*
There are plenty, maybe almost too many App/Page builders now to not have a single one on Cloudron: Budibase, NocoBase, Saltcron, Webstudio, Appsmith, and many more...shit, id even be mildly happy with GrapesJS at this point.

Having met Girish in person and knowing the sheer engineering brilliance between you two I think the best path forward is to cultivate the current community and to streamline the ability for US to make an impact. For example making community positions or methods for us to contribute to Documentation, Press Releases, Video Content, Live Streams, 3rd Party Liaison, and IMO most importantly Education/Resources on Packaging Apps!

I know, I know before anyone says it! Sounds like a "skill issue" this is all just linux, docker and open standards, languages, protocols so you should know all of this already, its ASSumed that you do...and this is where the problem/current attitude toward "new apps" derives and resides.

Besides the Dev Exp the only other major issue is the lack of Docker Compose & Swarm for Multi Node implementation. This is the only other thing that also keeps me up at night. All this debating for years: To Kubernetes? or not? What about this hack with Distributed Replicated Storage System? Or maybe we roll or own? but that will take too long so no let's not do any of it. Meanwhile buddy over at Coolify wrote that functionality by himself, Twice!! And in half the amount of time we were talking about why we aren't using the most obvious implementation: DOCKER SWARM!!!
Its like three main functions: swarm init - take the addy/key and connect the server, update/redeploy. It's not a SpaceX mars mission guys and gals but we are officially late as fuck to the party.
https://forum.cloudron.io/topic/2990/3-node-deployment-unified-dashboard

Don't mistake my passion for hate or anger

TLDR:

1. App/Page Builder
2. Better Docs/Dev Onboarding
3. Compose & Swarm Implementation/Unified Dashboard

I pray this does not continue to fall on deaf ears...Especially since I am willing and able to contribute...
Everyone is here for a mutually beneficial relationship, let's keep that the focus or part ways amicably.

@jadudm so what you're saying is implementing docker-compose into Cloudron would fix this and a ton of other use cases....🫡

@savity As much as i would love to see this or even something similar on Cloudron I don't believe there is any current development happening so i would not get hopes up. Going to have to find another implementation solution for this ONE for now...

@mononym is there a specific command you run to set to PHP 8? or is that in a config file?

Noted, focusing on the error - is the CloudronManifest.json file currently in the system? As the output is suggesting the file is not there, maybe it's gone ‍️

@BetaBreak is https://github.com/njsubedi/cloudron-erpnext/blob/master/CloudronManifest.json in your root dir?

I am seeking some 1on1 assistance packaging a NodeJS app generated using Wappler.io into a Cloudron package

If anyone is interested please send me a direct message and we can discuss compensation

Best,
Nick

Thanks @jdaviescoates & @nebulon - when is the code applied? During account creation or sub purchase?

Regarding Dashboard features - can we get pretty much everything that https://dashy.to/ is doing? Really good reference

Is it all within a cookie? or is there a step in the signup/subscription process where the code is entered? I am going to be helping somebody with their setup and since I have not been through the process in some time I am curious how it works.

+1

this is a huge feature addition
+1 on it being native

Does anyone have a hacked implementation? either with the supported image or a LAMP install?

Being able to deploy all 3 (DB, Backend Cloud Service & Static SPA) on Cloudron would be a Huge Value

• Surfer or minio work fine for the Static SPA front end (I've tested - just drop it in and go)

---

• Getting the Backend Cloud Service Docker File/Image + Mongo or Postgres Cloudron addon into a single Cloudron image seems to be the play
  • Then one can just use the desktop builder app at a minimum*

---

Being able to deploy all 4 (Builder, DB, Backend Cloud Service & Static SPA) on Cloudron would be Even More Value

• They use Electron to build the Noodl Builder Desktop Apps so the builder itself is just NodeJS/TS & can be ran locally. Unfortunately it does not seem to have an official docker implementation.... (Yet! ) only the Backend Cloud Service does...

---

• It Should Not matter if the builder is in the same Cloudron Image as the Backend and DB. From what I understand only the Builder and Backend Service need to communicate - if there is some limitation where the builder talks directly to the DB (looking into this more) then putting all 4 components into a single Cloudron Image could possibly be "ideal" or even required as the desktop app could have issues with direct DB connection in Cloudron - I exp this issue/limitation with the Wappler website/app desktop builder but this solution is Fully Open Source
  

https://noodlapp.github.io/noodl-docs/docs/guides/deploy/using-an-external-backend/
The different parts of a Noodl App
As a background it's good to know that a Noodl App consists of three parts:

The database:
All Noodl applications must be backed by a database, you can use either a MongoDB or Postgres compatible database. This is where users and other records are stored. Nodes like Query Records access the database via the backend web service.

The backend service:
This is the Noodl backend service that is provided via a Docker image and an instance can be started on most cloud providers. The Noodl backend is based on and compatible with the Parse Platform which is a great choice for a backend service. A solid open source project with an active foundation supporting many of the critical functions needed.

Static frontend hosting:
Noodl applications are SPAs (Single Page Applications) and need a place that serves the application frontend created when you deploy your application from Noodl.

https://www.noodl.net/post/noodls-open-source-era-pioneering-ai-powered-low-code-development
https://github.com/noodlapp/noodl
https://github.com/noodlapp/noodl/releases

Announcement
|
January 31, 2024
Noodl's Open Source Era: Pioneering AI-Powered Low-Code Development!

Today, we're excited to share a landmark development in our journey – Noodl has officially transitioned to an open-source platform! This isn't just a shift in our operational model; it's a pioneering stride in the realm of open-source software. As a robust AI-powered low-code platform, Noodl is set to significantly impact how both businesses and individuals craft powerful, custom software solutions.

Transition to a Community-Motivated Project:Moving from a centrally developed commercial platform, Noodl is now embracing a true community-motivated project model. This shift represents a fundamental change in how we develop, innovate, and grow. It's about tapping into the collective intelligence and creativity of a global community, ensuring that Noodl evolves not just as a tool, but as an ecosystem driven by its users.

Why Noodl's Transition is a Game Changer:

• Bridging Gaps in Software Development: Noodl's transition caters to a vital need in the software development sphere. Our platform empowers everyone, from non-technical users to seasoned developers, to swiftly and effectively create complex, enterprise-grade applications.
• A Hub for Innovation: By embracing open source, Noodl opens its doors to a global community of innovators. This means our platform will evolve rapidly, benefiting from diverse contributions and perspectives.
• Leveraging AI for Smarter Development: Noodl uniquely integrates AI technologies within a low-code environment. This fusion sets a new benchmark, offering smarter, more efficient tools for software development.

Exploring the Open Source Noodl:

• Direct Access via GitHub: The latest version of Noodl is now just a click away on our GitHub page. Get your hands on it at Noodl on GitHub.
• The Full Story of Our Evolution: Curious about the changes and enhancements? Dive into our detailed changelog at Noodl Open Source Changelog.
• A Wealth of Resources: Visit Noodl.net for in-depth insights, comprehensive documentation, and the latest updates.

Your Role in Our Community:

• Engage and Grow with Us: Star and watch our project on GitHub – your engagement is crucial for our collective growth and evolution.
• Spread the News: Share the story of Noodl's transformation within your networks and help us expand our reach.
• Join the Noodl Family: Connect with fellow enthusiasts and us in the Noodl Discord Community.

Empowering You with New Features:

• Autonomy and Control: We’ve eliminated dependencies on Noodl servers, giving you greater control over your projects.
• Adaptable Project Management: Choose between local storage or git providers for managing your projects, enhancing both flexibility and collaboration.
• Easy Migration Path: Seamlessly transition from Noodl-hosted git with our guide, available at Migrating from Noodl Hosted Git.
• A Special Note of Thanks:As we embark on this exciting new chapter, we extend our heartfelt gratitude to our incredible team: Kotte Aistre, Flor Diniello, James Haliburton, Daeun Jeong, Anders Larsson, Johan Olsson, Katherine Cerrato, Michael Cartner, Victor Permild, Mikael Tellhed, Eric Tuvesson, Tore Knudsen, and our supportive investors at 42CAP. Their dedication and talent have been pivotal in shaping Noodl's path to this momentous milestone.

Noodl's transition to open source is not just a change; it's a bold step forward in low-code development. By harnessing the power of AI, we are redefining the landscape of software creation.

Thank you for being an integral part of this transformative journey. Together, we are poised to redefine the future of low-code platforms!

Warm regards,The Noodl Team

I'm getting the following:
Jan 28 22:35:41box:dns/waitfordns waitForDns: nameservers are ["ns2.digitalocean.com","ns3.digitalocean.com","ns1.digitalocean.com"]
Jan 28 22:35:41box:dns/waitfordns isChangeSynced: _acme-challenge.EXAMPLE.com (TXT) was resolved to "REDACTED" at NS ns2.digitalocean.com (173.245.59.41). Expecting REDACTED. Match false
Jan 28 22:35:41box:dns/waitfordns waitForDns: _acme-challenge.EXAMPLE.com at ns ns2.digitalocean.com: not done
Jan 28 22:35:41box:dns/waitfordns Attempt 12 failed. Will retry: ETRYAGAIN

When the TXT record is generated the Value returns the string with "REDACTED" around it which have to be removed

Im sure its an easy fix