For those that would be interested. I have just created a live stream on Youtube for Sunday 21.06. 14:00 (CET). During that stream I want to show a bit how to make a Cloudron app and will use Matterbridge as the example for it.
I would timebox the whole stream to a max of two hours, lets see how far I'll get in that time, maybe I won't even need that much time.
There will be an unedited recording of the stream later on.
You can follow the stream at https://www.youtube.com/watch?v=RKcH2yJiLUo
Hi,
I'm thinking about creating a Cloudron app that uses fetchmail to fetch external mailboxes and deliver their mails to local accounts. Depending if I find a good example for a config ui this would then be configurable either from a small web ui or by simply editing the fetchmailrc file from the console.
Anyone else interested?
@girish said in Incorporate a WAF built into cloudron:
it should totally possible to move to apache instead of nginx for the reverse proxy, with some effort
I'm not sure if moving from Nginx to Apache is a very "modern" decision. There has been a buzz on this forum about Crowdsec a few weeks ago, maybe this would another approach that is possible (although the downside seems to be that you lock people into a third party SaaS).
In regards to reverse proxies. I recently spent quite some time working with apisix, which is basically nginx/openresty with an additional manage api in lua. It can get its route configuration either from etcd or a yaml file (other backends could afaik be implemented as plugins). And since its based on Nginx its quite fast.
Hello everyone. See you on half an hour at https://youtu.be/RKcH2yJiLUo!
Hi,
I am not using it myself, but could imagine this being useful to others. Looking at their deployment structures this only needs node and a postgres database.
@girish said in What's coming in 6.4:
I added a last item "Make it easy to install non-app store apps".
That is great news. In case you do not yet have a better idea how this could be designed, I want to pitch the way this is organised in Portainer again. I explained it already a while back in https://forum.cloudron.io/topic/4485/proposal-the-cur-cloudron-user-repository/14?_=1626194230000. Basically a local admin can override/extend the entries from their official "appstore". Additional entries are defined in a json structure. When opening the Cloudron appstore it makes a request to https://my.cloudron.host/api/v1/appstore/apps which gets a json response with all the appstore data. What if opening the store would in addition to this also make a request to https://user:password@store.my.domain/apps.json and also show a category "community" that lists apps from this json listing. Plus points if the listing can be password protected (like the private docker registry). This could also be a nice revenue model for external app developers.
@msbt said in Proposal: Free-Tier Alterations 
:
Not sure if paying for updates defeats the purpose of having a secure system with rolling auto-updates
Exactly. I think it's bad practice to hide things like updates and 2FA behind an extra paywall.
Plus it was like this in the past already and was changed for the very same reason: you don't want to have people with vulnerable old versions out in the wild.
A post of @luckow has made me interested in baserow (which is already available as an app on Cloudron). With it you can define databases and fill these through a form. It already has the ability to trigger a webhook if an entry was created.
At the moment the webhook payload cannot be freely defined, but if it would add this feature one could make a simple sign up page for Cloudron. User would be created, but sadly one needs to make multiple requests to also send out an invitation mail and to add the user to groups. But this way the admin can decide on their own if the signup should be confirmed.
I recently talked to the CEO of Humhub and also made him aware of Cloudron and this topic. He said that they are currently busy with investigating ways to automate deployments in container scenarios and once that is solved they would be open to collaborate on an app for Cloudron.
@jdaviescoates said in Better notifications:
going to do this using Uptime Kuma
In case you have not yet seen it, I have explained how to query the Cloudron API from Uptime Kuma in this post:
Hi @necrevistonnezr,
I have domain name field where I can enter my mail domain in the username generator. Values entered there seem to persist.
@robi their claim is
Seed your development database with real data
Slitting apps over multiple servers does not seem to be their goal.
For me it’s either the git cli directly, or git lens in vs code. Although the latter feels more technical, than the cli.
@robi said in ntfy.sh : self-hostable notifications:
our Server Monitor App
Which app is that exactly?
@robi said in ntfy.sh : self-hostable notifications:
each monitor each other.
yeah, if you want to be serious about monitoring then it should run with a different provider and in a different region than the rest of your stack. Or even better pay someone else to host a geo distributed monitoring for you.
For my own use case Uptime Kuma is quite sufficient and can also send notification via Telegram.
@d19dotca said in Trigger full backup from cli / scripted migration:
Yes, email would be my main concern as well, as this comes from unknown third parties. Other cases would be systems where customers could upload data.
In my original case I wanted to see if I can reach minimal disruption for my own migration. I made a small writeup of my my approach in https://blog.9wd.eu/posts/cloudron-migration/.
Notify.sh is indeed quite a cool project and has also seen good growth over the last few months.
Depending on the use case I prefer to rely on third parties for checks/notifications. What good is a chat or email notification if my mail or chat server are down as well 
Slightly more complicated curl, but this posts a message into a telegram message:
curl https://api.telegram.org/bot$telegramApi/sendMessage -d chat_id=$telegramChat -d text="Backup successful 😀"
Hi @girish
somehow I missed to reply to you, so now more than one year later
The dry run option indeed seems pretty handy. Depending on the apps running on the server I see myself using that in the future.
@d19dotca said in Email / Dovecot, possible data corruption:
or do I need to be running this from inside of a container instead perhaps?
Yes, exactly that.
root@my-cloudron:~# docker exec mail doveadm -h
usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
acl add|debug|delete|get|recalc|remove|rights|set
altmove [-u <user>|-A] [-S <socket_path>] [-r] <search query>
auth cache|login|lookup|test
backup [-u <user>|-A] [-S <socket_path>] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g <mailbox_guid>] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest>
batch [-u <user>|-A] [-S <socket_path>] <sep> <cmd1> [<sep> <cmd2> [..]]
config [doveconf parameters]
copy [-u <user>|-A] [-S <socket_path>] <destination> [user <source user>] <search query>
deduplicate [-u <user>|-A] [-S <socket_path>] [-m] <search query>
dict get|inc|iter|set|unset
director add|down|dump|flush|kick|map|move|remove|ring|status|up|update
dump [-t <type>] <path>
exec <binary> [binary parameters]
expunge [-u <user>|-A] [-S <socket_path>] [-m] <search query>
fetch [-u <user>|-A] [-S <socket_path>] <fields> <search query>
flags add|remove|replace
force-resync [-u <user>|-A] [-S <socket_path>] [-f] <mailbox mask>
fs copy|delete|get|iter|iter-dirs|metadata|put|stat
fts expand|lookup|optimize|rescan|tokenize
help <cmd>
import [-u <user>|-A] [-S <socket_path>] [-U source-user] [-s] <source mail location> <dest parent mailbox> <search query>
index [-u <user>|-A] [-S <socket_path>] [-q] [-n <max recent>] <mailbox mask>
instance list|remove
kick [-a <anvil socket path>] <user mask>[|]<ip/bits>
log errors|find|reopen|test
mailbox cache|cache|create|delete|list|metadata|mutf7|path|rename|status|subscribe|unsubscribe|update
move [-u <user>|-A] [-S <socket_path>] <destination> [user <source user>] <search query>
oldstats dump|reset|top
penalty [-a <anvil socket path>] [<ip/bits>]
process status
proxy kick|list
purge [-u <user>|-A] [-S <socket_path>]
pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V]
rebuild attachments
reload
replicator add|dsync-status|remove|replicate|status
save [-u <user>|-A] [-S <socket_path>] [-m mailbox]
search [-u <user>|-A] [-S <socket_path>] <search query>
service status|stop
sieve activate|deactivate|delete|get|list|put|rename
sis deduplicate|find
stats dump
stop
sync [-u <user>|-A] [-S <socket_path>] [-1fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g <mailbox_guid>] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest>
user [-a <userdb socket path>] [-x <auth info>] [-f field] [-e <value>] [-u] <user mask> [...]
who [-a <anvil socket path>] [-1] [<user mask>] [<ip/bits>]
zlibconnect <host> [<port>]