B
Looks interesting, but if you haven't seen it, NocoDB has a view that lets you build custom forms https://nocodb.commonscomputer.com/dashboard/#/nc/form/f22133cb-7261-48b1-a803-0d9073bf26ef
There's a "survey" mode that gives you Typeform-style one question at a time, too.
This is very similar to how I've used Airtable in the past, so was impressed that NocoDB supports this.
@marcusquinn funny enough, it turns out YOU posted a wishlist item for what @tennox is building -- an IPFS node to be run on Cloudron.
https://gitlab.com/wovin/deploy/ipfs
I made a request in their issue queue https://gitlab.com/wovin/deploy/ipfs/-/issues/2
And funded their open collective https://opencollective.com/wovin/projects/ucan-host-ipfs
IPFS desktop totally works from your desktop. Figuring out how to configure it and connect it with an always on Cloudron node could be a future feature.
And as you mentioned, I'm interested in the DNS mapping too.
@shanelord01 thanks for bringing this up Shane. I would like to see it packaged, it will probably need to start as a custom app.
I installed one myself taking over a full KVM-1 VPS at Hostinger ($4/month).
I'm an AT Protocol expert and maintain a tech talks Ghost blog at https://atprotocol.dev (hosted on my Cloudron server!).
There are some misunderstandings in this thread about architecture and frankly I'm not going to argue about decentralization. Running a PDS means user ownership of your data, which seems very on mission for Cloudron.
It also handles auth, acting as your OAuth server wherever you log into with your account. There are multiple non-Bluesky apps with different data types (called Lexicons). A few of my favourites:
When you log into other AT Prototocol powered apps, the data is written to your own PDS. Here's my (Bluesky hosted) account with all the data types: https://atproto-browser.vercel.app/at/bmann.ca
It is also extremely low resource usage. Runs on NodeJS and SQL lite and some web socket connections.
I haven't gotten far in learning Cloudron packaging myself yet, but I'll update this thread if I get something guying.
I’d like to pool funds to get ElasticSearch packaged to be deployed on Cloudron and set up to integrate with a Cloudron installed Mastodon.
See this for background notes https://forum.cloudron.io/topic/5427/how-to-install-elasticsearch-on-mastodon/40
This adds useful search to your Mastodon instance.
I’m looking for both a developer that wants to be paid to do the work, and people who are interested in contributing some funds.
I can host an OpenCollective or similar to pool funds — I’m also looking to experiment with Polar.sh https://polar.sh
The output would be a git repo with dockerized Elastic Search and necessary Cloudron Manifest, as well as instructions on how to install.
The install could use the Cloudron CLI interface to install remotely.
Yep, I had no problems with this -- once I figured out enabling POP3 
forum@yourdiscoursedomain.com as a mailboxWant unique addresses for categories? Set up aliases for forum@yourdiscoursedomain.com like myothercategory@yourdiscoursedomain.com
In Discourse, you'll need to enable email in
For initial Discourse setup, I also have better instructions:
Rather than resetting the email address, you can / should reset the password -- which you need to do right away. Run the rake admin:create task from the Terminal for the root / admin account.
Hit "Y" to reset password and change the password.
The account already is an admin, and I didn't bother changing the email because I really only see it as a backup account.
Once I logged in with OIDC with my Cloudron account, I followed this same process to make my account an admin account -- same rake admin:create command, say "Y" to making it an Admin, but don't change password.
I don't know how to contribute better setup instructions -- are they in git so I can send a PR?
Setting up the sieve rule means I have to have the password and set all of that up.
Using the "mailing list" settings means I don't have to do any of that, don't need to create an inbox, and it doesn't need to be owned by any accounts (and cloudron users with email admin / admin / superadmin can modify as needed).
So I guess I answered my own question I'll write it up. for people who ask in the future. "How do I set up email forwarding to external accounts without having to provision Cloudron accounts" == mailing list.
@luckow thanks for the SoGo -- looks like that does take care of everything.
I put together a bunch of notes on Cloudron, including hosting costs for some setups https://bmannconsulting.com/notes/cloudron/
My next goal is to get some funding for developing images of a couple of different apps.
I’ll post about them here when I write up more about them, but I wanted to ask if anyone has thoughts on “crowdfunding” creation of packaging and maintenance of apps over time?
@LoudLemur a Penpot install and named projects
Hey @steveruizok -- there's lots of differently licensed apps here. e.g. Outline wiki is BSL, and specifically restricts paid hosting. Cal.com is open core. n8n has Sustainable Use License.
This would be the same case for TLDraw. For example, I have a personal shared computer Commons Computer https://commonscomputer.com. I believe I could run tldraw on there for my own non-commercial purposes -- in the same way that I could run it on Digital Ocean or anywhere else.
I am in the same boat.
Discourse has IMAP support but only for group inboxes, not for "reply by email".
Discourse was one of the big apps I want to be running on Cloudron, and having to add an external email provider just for POP3 really sucks.
Discourse has their "mail receiver" docker container that runs all of this for you if you self install elsewhere, and works really well.
"Don't run Discourse on Cloudron" seems like a bad solution. Is this on a backlog somewhere to solve?
I had already been running my first Cloudron on Hostinger. Just turned on a second with this one click -- thanks!
On home hosting: you’re making my point for me.
“It’s easy” -> is there a step by step guide? There’s a blog post from 2018 and various tips scattered across forum threads.
“Just buy it on eBay” -> even more of my time that I’d have to figure out. I’m also not looking for a minimal box and I priced it out. There are ALWAYS cheaper options, with different trade offs.
The most recent post I found was about CloudflareD https://forum.cloudron.io/topic/8962/cloudflared-as-proxy-for-home-hosting
If Cloudron were serious about home hosting, building in first class support for Tailscale, Cloudflare, and similar providers would be the way to go.
I’d also love a built in config for one or more CDN providers (not just for home hosting!) which would take load off a server AND keep static sites up and running in the case of a server outage.
And of course, the email issue, where you need to add an SMTP relay, as a home IP isn’t going to have good mail delivery. Maybe with a VPN and a “gateway” box, but that’s a separate cost again.
Don’t get me wrong: I’m really intrigued with home hosting. I work on p2p and edge computing myself, and an IPFS server app is one of the custom apps I want to fund. But the majority of Cloudron apps are “classic web2 server apps”, which are mostly designed to run on servers.
A cloud hosted Cloudron to act as always on coordinator / relay / bootstrap connection to eg simple desktop apps (and/or connecting via Tailscale to the Cloudron box) is probably a nice trade off to serve many more people.
@jdaviescoates @robi thanks! Here's the presentation https://assets.cloudron.io/presentations/baylisa-august-2019.pdf for others not clicking through / wanting a written version.
For context: I've been running and creating Heroku buildpacks since they launched 10+ years ago, precisely because buildpacks are simpler than Docker and make things easier for mortals to self host
Now, thinking about a broader "app store", and more hands maintaining common apps, I'm wondering about connecting with other communities to make lighter maintenance work.
Effectively: what is the difference between some-form-of-buildpacks and Cloudron's current packaging format?
OK, followed this to temporarily disable IPv6 and everything worked right away for install https://linuxconfig.org/how-to-disable-ipv6-address-on-ubuntu-22-04-lts-jammy-jellyfish
This should be noted in install settings...
I'm now setting up some company stuff. We use Route53 with custom nameservers.
Trying to use Route53 for a domain complains "Domain nameservers are not set to Route53" ... they are, we just have our own ns1.ourcompanyname.com set for them.
For now, we're just going to set back to default AWS nameservers, but we'd appreciate a way to get past this in the future.
I’ve used LogSeq extensively and setup Git-based sync and publishing https://notes.bmannconsulting.com
It doesn’t really HAVE a backend.
What you could do is use WebDAV on Surfer or Nextcloud, or SyncThing, and sync your LogSeq to any devices that need it.