@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.

@girish Hey, did just that, and I'm having trouble resolving names AFTER setting them. Cloudron is able to set dns records on aws just fine, but then the check to see if the records are created never gets done. Checked the logs and it's server timeouts. Tried running an nslookup query, to no avail as well. Kinda weird, seems like the same problem I had on the hosting provider, with unbound, maybe? When I try to sudo, it also says sudo: unable to resolve host ubuntu: Resource temporarily unavailable, but it gets me to root anyway. I'm a bit beyond my skills here, though, if anyone would like to chime in, I'd appreciate it.

@p44 Maybe Integromat or RSS-Bridge? https://forum.cloudron.io/topic/2617/rss-bridge-a-good-complement-to-fresh-rss

Hi, fair point, we will add the information there.

@girish thank you for the correction.

@Lonk Yup, that sounds right. In fact, it seems that Cloudflare made the nginx+http3 patch (but not sure if nginx itself ended up using that).

@nebulon Agreed. System is definitely too vague, and there are services you can restart in there, it's not a view only dashboard. Based on the discussion, I'd like to suggest grouping logs and graphs under the same page with Monitoring as name. In terms of concept, it's quite similar, the presentation of the content is different. One counter-argument would be it adds a click to get there, but on the plus side, it will lighten the menu list, which is getting longer (and thus harder) to process.