Cloudron Forum

It looks like it's working now.

Release 1.20.0 included these PRs related to mirroring, maybe one of them caused the issue: Refactor Pull Mirror and fix out-of-sync bugs #24732 Use the type RefName for all the needed places and fix pull mirror sync bugs #24634 Allow skipping forks and mirrors from being indexed #23187

@jdaviescoates said in Meetsy - an online booking system: looks like it only works with a Google login and Google Calendars, The Github has some requests for Free alternatives, so it might be worth checking back with the project later.

See Minio for a more mature implementation already available on Cloudron.

Oh cool thanks for pointing that out, I hadn't noticed before. I guess the downsides don't really apply to me right now, but I'm not sure I'd want to enable arbitrary masquerading if there were a bunch of other people on this cloudron. I still think it's reasonable for users to be able to send with a subaddress of any of their aliases, without opening the floodgates and allowing them to send from any address at all.

Ok, finally sorted after stopping queries that were locking old txnids and then doing a full vacuum. I suppose restarting the postgres container could have done that. This was useful to find blocking queries, in addition to pg_terminate_backend: SELECT pid, datname, usename, state, backend_xmin, query FROM pg_stat_activity WHERE backend_xmin IS NOT NULL ORDER BY age(backend_xmin) DESC; Went from 88% full to 38% full in about 10 minutes.

@infogulch thanks for this topic, I had GB of binlogs as well!

@infogulch I hadn't heard of either of the things this was inspired by before, but it made me think of Cobudget

Your plan to use the VPS for email and home for web apps makes sense. Keeping email on the VPS ensures stable deliverability while hosting apps at home is cost-effective. It’s a solid plan and can use a Mail Relay setup with Postfix for SMTP and Dovecot for inbound mail. Cloudron doesn’t natively support email proxy, but you can configure it to send via your VPS’s SMTP relay and forward incoming mail via Postfix. It Works for web apps but may cause SSL and DNS propagation issues, so check automation for SSL renewals. You might want to check Cloudron forums for similar setups!

I was able to help the project get their dockerfile off the ground so that it builds and runs with just docker, but it still has a ways to go. Here are some things I think would need to be improved before it would be suitable for cloudron: Reduce image size by copying binary results out of the build stages. This is a bit complex because the project is built with rust/wasm-pack and runs a wasm on the frontend, and uses haskell stack for the backend. I'm not familiar with doing docker optimizations with either of these technologies. Change the backend to save all data into a /data volume. This will require some changes in the haskell code. Get deps-only build steps working. This would be a nice-to-have for the devs to reduce build times after the first build (which can reach to 40min!), but this one isn't a deal breaker for cloudron. I tried, but it causes some compilation output issues so it was commented out for now. The author was very nice and quite receptive to changes. If anyone else works on this you may want to just aim at getting them merged upstream.

I have also added Service events in the event log for the next release. So, this way, we can know if the service was automatically restarted after cert update.

@infogulch ah thanks, i will remove it.

@moocloud_matt As soon as someone comes in reporting a real case that their NIC is saturated and it's slowing down their server I'd be interested in pursuing a solution. I've never seen such a real case on these forums (though I may just be misinformed) so I'd have to tilt towards YAGNI until one appears. Object storage is not magic, it's just data like everything else. If it's just used to serve file attachments for an app with 25 users I wouldn't expect it to be a bottleneck.

Unfortunately, Mintable hasn't been updated for 10 months:- https://github.com/kevinschaich/mintable/tags

@girish said in Installing JupyterHub extensions: @infogulch OK, I tried this quickly now and it looks like 1GB is not enough for those webpack builds. I just put it to 4GB and that worked out. Maybe 2GB will suffice too... I tried several different memory settings. In my use case 4G was the minimum needed for rebuilding.

I began packaging up this app with a custom Dockerfile (though the project does have its own dockerfile). You can find the source at: https://source.infogulch.com/infogulch/promnesia-app though it is just barely running. I have published the app package to my docker hub repo at infogulch/promnesia-app:v1.0.20210415-4 You may be well served by reviewing the app's own install docs from the README.md, or the users guide. As for the cloudron integration, these are the steps that worked for me (I just got it working for the first time moments ago so...): Install the server component with: cloudron install -l subdomain --image infogulch/promnesia-app:v1.0.20210415-4 Then login to authenticate with proxyauth at the subdomain you choose to install it. The https://promnesia.my.example.com/status endpoint displays a short JSON status (the app is not designed to be interacted with from the web) Install the extension. Go to extension options and set the "Backend source" url to your domain, (e.g. https://promnesia.my.example.com) It seems that logging into the app in the browser enables the extension to authenticate correctly. (This makes me want to critically review which extensions I have installed .)

@girish I think that would be a good change. I also think I should have gone through the Troubleshooting document sooner : https://docs.cloudron.io/troubleshooting/ Thanks!