Oh, I forgot the kicker of the story: They can’t acknowledge that they don’t validate their input fields properly without acknowledging the need for a filter to be added while fixing that same validation code (and they should fix it tbh). But if they don’t fix it, I’ll keep hacking their validation form (my WP Plugin works), and if they do fix it - they’ll add that filter for me I’m next to positive which allows me to code a less hacky solution. Win-win. Just took me forever to realize it.

As i could read in the forum it has not been updated anymore. But that would a good substitute for Google Docs. But here I will investigate some time in researching in the onlyoffice suite. Maybe that fits to my needs. Thanks @scooke, every idea is welcome. My plan is degooglefy my digital presence, and I am very pampered as a current G-Suite user.

@MooCloud_Matt Yes that's true too, but that wasn't what I wanted to achieve in this case. I was specifically trying to teach myself how to use a cloud-init script / boot script, it was a learning project. Always trying to learn new things.

@girish thank you for the insight. If I am extending the existing drive then I'll make sure to keep it SSD as it already is, I may try HDD if going the first route though. I'll check, this isn't an easy task for extending the existing disk unfortunately, but this may be the better move. Of course the drawback there I guess is I'll be paying for way too much disk space and need to do it all over again if I for example lose one of the clients that are using so much email space (as email is the single biggest consumer on my server right now, by a lot). I'll have to run some tests.

@jdaviescoates said in What Android calendar app are you using?: Simple Calendar Pro I'm also using Simple Calendar Pro

@andirahmat said in Running Ubuntu 16.04 as an App on Cloudron: @girish said in Running Ubuntu 16.04 as an App on Cloudron: @andirahmat said in Running Ubuntu 16.04 as an App on Cloudron: I wonder if it possible to run this on cloudron. I mean is there any ubuntu 16.04 served as cloudron app then run this install script on it? All apps on Cloudron use Ubuntu 18. But you can build a custom app with the base image FROM cloudron/base:1.0.0@sha256:147a648a068a2e746644746bbfb42eb7a50d682437cead3c67c933c546357617. That one is ubuntu 16. @girish can you please refer me to the related documentation on doing this? Should i have another cloudron installation for this? Now my cloudron running on ubuntu 18.04 Keep your installation at 18.04. Girlish is talking about the DOCKERFILE’s too FROM line. Cloudron’s base image 1.0 was based on Ubuntu 16 so you should have that entire OSes dependencies to build an app on Ubuntu 16 even though Cloudron itself only runs on 18.04.

@fbartels said in NodeBB Setting Change: Make upvotes and downvotes public: Don't forget that it's not the forum users that decide this, but actually @girish and @nebulon. And that should purely be on what they see value in and can see themselves maintain and support in the future. That's exactly my point, by being able to see what they like, I have a much better idea of what could make it into master. If a bunch of app devs or consumers like it, I know @girish and @nebulon are at least going to look into it. But if a Feature Suggestion even only has 2 likes, if I can see it's girish and nebulon, then I know it's much more likely going to happen in the future over 5 regular users upvoting. Does that make sense?

Just got some basic tests up and running for Homepage! You can find the repo here. It packages version 0.9.6 of homepage-cloudron. I hope to soon add a background color option to the config as well for the more minimalist crowd. @girish what do you think the chances are of publishing this on the store?

@girish I started getting Gitlab build errors in the docs fork I made from something called pipelines (likely how you guys deploy). So I def contributed to this incorrectly. I'll just edit it locally until I'm able to merge request the API docs properly (can't wait to get to the File Manager API, haven't RE-ed that one yet). I also hope there's some secret API calls that you don't even use in Dashboard or Cloudron CLI. I love hidden API endpoints like that. It's like getting to see the beginning of an abandoned (or yet to be implemented) idea.

I know the guys over at OpenEBS.io in case a container storage solution integration is needed.

I like how well thought out "sideloading" apps is. That's one of it's biggest benefits for me as a developer, but I see that from a user side too. Maybe that's why I like this. I've always liked sideloading apps.

@nebulon Haha, everyone needs a little love too

@Lonk If you code faster and cleaner, it's all good

This is great, thanks, I use over 900+ tabs in multiple windows, with some pinning. This will help segregate things a bit more, thanks.

@malvim said in Feasibility of running cloudron inside a vpn with package redirection: What ports do you think I should be concernet about forwarding packages? Is it just 80, 443 and 25? I've taken a look at cloudron_firewall.sh and there's a bit more stuff going on there, isn't there? Heheh https://docs.cloudron.io/security/#cloud-firewall is the full list. But at the barest minimum port 443 is enough.

@girish I did not know the term. I certainly did know the effect ^^ (I might have to invest in an actual rubber duck... maybe they are especially effective)

I realized today that I never answered this question. It's because I was looking for a VPS panel with an OpenVPN Client. Which I'm not sure honestly exists after my research. But it sure does now! Love Cloudron sm.

@robi My idea is a pull through the API. So basically when you’re installing an app or even adding a new sub domain, you have a drop down to select the TLD. I was imagining an item at the end of the list that said “Click here for more domains available from your connected registrar” and if you did, it would pull from the already connected API and add them to the list of TLDs to choose from. When you submit, there would be a pop up warning mentioning that Cloudron will be changing the DNS settings for the external domain chosen and adding it to its database of internal TLDs.

This is almost docs-worthy, under some kind of home-hosting section.