Relatedly, for the benefit of the team here, I'm a ghostwriter for some of the content at HostingAdvice.com. I've nominated Cloudron as a potential future feature article, and the staff there added y'all to the list of companies to research for future interviews. (And if they conduct one, I'll end up doing the write-up.) HA gets pretty decent traffic from a CIO perspective, so here's hoping that Cloudron comes up on the list sometime soon.
@robi everything you referenced to the install lol worked for ATT installing U-verse and I've seen all types of IW - single family homes, multi dwelling unit, duplex, from band new homes with ethernet to every jack an a nice patch panel to 100+ year old Victorians with no cat5 and where you cant drill anywhere lol I understand Star Links hands off approach could be good for local techs but yeah the complexities of install a new connection into an existing home network is not always as simple as: "run the line and connect it"
@girish This is part of my problem I posted about yesterday (in fact mastodon.host doesn't even work via HTTP anymore), but also, note the Sidkiq errors I mentioned that might be somewhat related to relays in general.
mine is at https://pixel.rmendes.net/rmdes
you can follow me from your fediverse client @email@example.com
EDIT : I tried to add some of you but if you only share your instance URL
it's really hard if not impossible to find your exact profile.
No matter if it's on peertube, pixelfed, mastodon, pleroma, zap the structure worth sharing so that people find you is always @firstname.lastname@example.org - with this, a simple search from within Pixelfed or Peertube or Mastodon allow anyone to follow you from where they want, indeed you can follow a pixelfed account from mastodon (not vice versa) or a peertube account from mastodon or pixelfed from pixelfed, or peertube from peertube account, the idea is you get the information from where you interact the most or from the same protocol, or both, yeah it's a mess 😁 😇
@girish I also think about this. The use case is. I need the first db and dbuser for the web app. And the second db and dbuser for view tables from the first db. This second db and db user is used for metabase report so the original db and table structure not shown for the metabase user.
Another case i can think of is to make a slave db on the lamp app from external db.
@nebulon Yeah, I wrote this pretty exhausted. That said I could probably rewrite it sometime in the coming weeks. Basically, I made the VM because it's what I use to develop apps for Cloudron - and the OVA is nice cause I rebuild my computer every so often and kinda tired of rebuilding it over and over again. Figured if I did this, and wrote a quick tutorial on it, it could benefit everyone 🙂
@murgero Thanks for following up, apologies for not seeing this sooner.
I don’t really know if they are fully compatible. I started using it a number of years ago since it then was a more secure and faster VNC implementation. It works cross platform by downloading a server application from RealVNC, and then registering an account with them. The free tier allows for 5 desktops/servers. The added benefit from a simplicity point of is that you connect via the client app through their servers, eliminating the need to open standard VNC ports in your firewall.
I never did manage to find out how, and if, it is possible to connect in other ways. That’s why I was hoping someone else knew...
@murgero (you probably know this but just writing it out for the wider audience)...
Cloudron was primarily made to install and manage pre-packaged apps. This meant that addons were defined by the package and we don't want end users to make difficult decisions as to what database to use and what caching backend to use. Lesser choices cover 90% of the use cases.
But over time, we saw a lot of demand about custom apps. And thus LAMP app and even allowing custom packages. And now we probably also need dynamic addons (ie. select which database post installation or just before installation). While this is doable, this moves Cloudron more and more into PaaS territory. My initial instinct is that it's fine to venture into this space and maybe cover 90% of the use cases but we have to think through it 🙂
Thanks for the trace. This is an issue on the client side only, apparently the error object is not correctly set here. Will try to reproduce this to fix it. This should not really impact the Cloudron server as such though.