Cloudron Forum

@nebulon thanks for packaging this

One more app I can remove from my non-cloudron VPS

Installed fine, logged in and changed user and password, connected to my iOS app.
All appears working - will try to test more.

@scooke
docker build --platform linux/amd64 -t your docker.tld/cloudron-dawarich:v1 .

Or, you can install from my image :
cloudron install --image tcmbp132021/cloudron-dawarich:v1 --location dawarich.yourdomain.tld

Dawarich package now available at https://ccai.uk for easy installation

Note PostInstall :
Username: demo@dawarich.app
Password: password

@scooke I cloned the repo, built it and used cloudron CLI to install it.
It works

Just adding it to my custom app installer to ease the pain

@adisonverlice2 IMHO you're confusing apples and pears - that's the polite expression, there are others.
It seems you COMPLETELY underestimate or misunderstand the ongoing work needed to maintain and develop Cloudron, and keep it stable.

Cloudron is not providing some hardware, and some base software or reselling / redistributing a 3rd party software (eg pfSense).

I completely fail to understand why anyone would agree to receive a single payment for the next xx years work they have to do, unless that is 20x the annual price.

I repeat : pay a single fee for perpetual licence for a fixed version of Cloudron ? maybe that might work. Want the benefits of a maintained platform with upgrades, forget it.

I've had enough of this discussion, which is IMHO is just plain silly.

@adisonverlice2 maybe you should address your questions to netgate

One-time purchase is a really bad idea and makes no sense at all .... unless the one-time purchase gets you a one-time version, e.g. version 8.5.0 and you then stick with that, no upgrades (ok, well maybe one year).

There are some precedents in financial markets, taking into account present and future value of money, for a fat payment to be made up-front for continuing lifetime service.

But generally it's a silly idea to expect to get lifetime continuing service (current version, plus free future versions) for a single fee, unless the multiple is significant, 10x or 20x.

I think the Cloudron team have got enough to do without being distracted by this kind of suggestion.

@chmod777 will take a look at it

@WiseMetalhead well done on packaging - it's always a bit trial-and-error !

My memory of this app is vague and distant, but if files are not needed, they can be removed from /app/data by adding code for that to start.sh to get a tidy installation, but I'd be tempted to ignore them.

@hakunamatata sadly I didn’t find a solution.
I did get Reolink cameras working through the Reolink plugin but I didn’t go through the process of setting up capture and storage.

Instead I diverted effort into packaging Zonminder for Cloudron but I’m a bit stuck on that at the moment.

Short-term I am using an app called Glancecam for Mac which actually works well for live monitoring, but doesn’t handle capture

@LoudLemur thank you !

Does the world need yet another ai chat interface ?
Or am I missing some important features ?

congrats @girish and whole cloudron team
look forward to the release making it through the remaining stages

@chmod777 understood
Just take into account and be clear about how you’re going to get your sales data into your accounting system

I always feel invoicing is inevitably bound to accounting, and any decent accounting system should be configurable for invoice formats which can include support links.
Maybe I’m not following the train of thought of requirements b

@LoudLemur I can add it if I know the git repo and the built docker image location

might need the health check issue to be resolved

Cloudron’s reliability is what sets it apart in the market.
+1

I’m not a fan of Cloudflare - just put it in as fastest way to address a possible vulnerability.
But proof of work is often a pain for users.
I feel there are only 2 good solutions :
Cloudron re-write as an official utility (resolves authentication much more neatly)
CCAI adds user registration
I’m thinking what direction to take it in if not adopted/rewritten

@scooke raises some valid points about user expectations, and I will freely admit that I am not sure where or how the line should be drawn.

Conceptually there is indeed some friction between :

• user is not comfortable installing CLI tools and docker and using them, effectively setting a competence bar and edging them out of this activity
• making it easier to do what they're not comfortable with, effectively lowering that bar and inevitably encountering support requests if/when it becomes normal/easy to install unsupported apps (via @Kubernetes scripts, my tool or an official way)

However I am clear on these points :

• installing custom apps should be easier (hence my app) : on one level, it's purely and simply a timesaver, e.g. for a user who is competent in installing apps, at least that's how I am using my tool currently
• nothing wrong in concept with Cloudron providing an official GUI for installing custom apps (Cloudron has already provided the CLI and know-how for non-gui)
• support line must be clear : Cloudron as a team/business are not responsible for custom apps (not supported, not maintained)
• if properly handled, easier installation of custom apps can reduce forum pressure on Cloudron team for new apps into the AppStore

I like @scooke idea of a pop-up confirmation box or similar : clarity and disclaimer is good.
Whether it goes as far as requiring a reboot of the Cloudron instance, I'm not sure.
But I will add a disclaimer box to my app.

Beyond that, it gets a bit unclear for me :

• does the packager provide support (my view : only optionally / voluntary / reasonable efforts)
• do packagers need a reputation score (my view : nice but not viable as a formal rating, who has time and authority to set these, instead maybe some unofficial star rating 1-5 from users with successful deployment of a custom app)
• can an installer for custom apps provide a monetisation mechanism (comment from @girish) which effectively incentivises packagers to work through the AppWishlist (my view : yes, it could, but it's another layer on-top)
• should support for installed custom apps be channelled (a) into an UNSUPPORTED category of existing Cloudron forum, or (b) very deliberately into a different forum (my view : B makes a point but A is easier and more natural)

@scooke said in Installing custom Apps on Cloudron:

Please do not turn Cloudron into another messy Yunohost.

I agree 100% on this.
It must definitely be the goal of any efforts in this area.
Equally, IMHO, standing still is not an option.
We have too many well-intentioned but actually not-our-business "lectures" about how Cloudron should expand, and also too many "please please please" requests, pointing to unmet user demand.
We cannot be like King Canute trying to push the waves back.