Cloudron Forum

Note: I believe this will also allow me to host a main TLD at one Cloudron and all of it's subdomains at another. Which would be a further benefit to users.

Ok, I will mark this as solved but let's investigate further if this comes up again.

FWIW, if you do docker exec -ti mysql /bin/bash then the details mysql logs are located at /tmp/mysqld.err .

@Lonkle He's alive! Where you been for 2 years?

@d19dotca @Lonkle , had the same issues with Cloudron installation on vpsdime. Fixed it using the same workarounds in this thread. Seems to work fine now. Not sure if there will be any issues in the future..

Haven't tried but echo "yes" | ./cloudron-setup probably works as well to automate reboot.

@lonkle I forgot I turned automatic updates off, Domain Aliases are supported in v6.1.2. 🤦

But on top of that, you should note that you only enabled Domain Aliases on subdomain multisite installs, not subdirectory multisite installs. Both of those types of Multisite Modes support multi-domains. That's important to note since many like to use subdirectories and still use multiple domains.

@lonk That's a totally valid, effective way to do it. Probably the most instantaneous of all the things mentioned, since it seems speed/latency is a priority for you. Lambda's not that bad to write code for - if you get pretty advanced with it, you can really run nearly any language on the platform, though the officially supported Java, Go, PowerShell, Node.js, C#, Python, and Ruby are the easiest options. You've got a lot of choices there.

@girish Nope, tried to debug it. Tried to even repair it. In the end a reboot fixed the problem, but that was pretty weird.

Should be back now. I think it got disabled when we updated yesterday to NodeBB 1.6.0. I updated the plugin and now it's back.

@girish Oh, absolutely with a custom app, I mentioned in the original post that I'm going to build my own Wordpress Stack to simply and only add this. But I saw benefit to other user's being able to script something post-update as that's literally the only thing my stack will do differently than the default Wordpress app (I'll have to integrate your updates into my stack manually each time so I still wish there was a way to run an external custom sh script post-installation).

As you can see my custom script simply uses the CLI to upgrade all databases with any new required formatting if and only if any updated Wordpress core or updated plugin require it. When you update from the Cloudron interface, it simply updates all the files and Wordpress has this really annoying tendency to not upgrade the databases post-upgrade invisibly. The script above is the only way to make sure file versions and database versions stay in sync 100% of the time every update.

This becomes nearly unavoidable if you want to support multisite in the future since the problem becomes more convoluted in that installation type so my script detects multisite installations and runs database upgrades accordingly with WP CLI commands or single site only commands if it's a single site.

I actually think the script below should be an optional "automatic upgrade plugin and themes checkbox when updating Wordpress core" option for Wordpress installations as well, here's the WP CLI code for it:

# Plugin updates wp plugin update --all wp plugin update --all --skip-plugins --skip-themes # Theme updates wp theme update --all wp theme update --all --skip-plugins --skip-themes

@lonk Yeah I figured we had the same issue but apparently not, my bad. Didn't mean to hijack the thread earlier. haha. Mine was actually caused by v6.0 due to a breaking change in how SFTP works - by default for admins only, meaning any non-admin users are rejected out of the box. But I think yours was different as you filed it before v6.0.

I had to work hard to find this setting. Found it finally under Plugins -> Mentions

@mehdi you're right, my poor choice of words..

apt is a binary that can call libapt-pkg libraries and provides a subset of interactive options and commands for apt-get/cache by default.

apt-get is not limited to those options.

I could really really use this.
If u couple this with an ability to divert searx traffic to the VPN this would be a huge benefit towards at least partial anonymous searching.

@nebulon said in I swear the favicon on NodeBB was stated to be fixed:

Can you refresh your browser cache? Seems to work here for me.

That did it! 😂 Thanks.

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

@girish said in Is it possible to configure the Apache Logs in Wordpress (Developer)?:

Currently, you cannot change this, no. You have to use the LAMP app if you want to change the apache configs. In the LAMP app, there is an app.conf which gives you control over logging.

You'd expressed interest in more fine-control over logging in another thread. If that's still true, I'll deal with the Apache over-Logging for now looking forward to a time where we figure out a solution for a way to best configure logs for the end-user.

Going to LAMP would just feel like I'd be contributing less and less to the Wordpress (Developer) and (Managed) codebase(s) and that's my real goal. To make Wordpress (Developer) the best it can be in Cloudron.

So maybe, one day, those access logs will be configurable. 😉

@girish said in Can I send the Wordpress Debug Log to the Cloudron Logs:

I agree we should visit this at some point for better logging

This fixes the Wordpress "custom log path issue". But I do think we should revisit in the future about other apps and how we might be able to symlink the logs together. Anyway, you got me 75% there on this one, so thank you for that! ☺️

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