@girish said in Cloudron 5.6.2: @jdaviescoates There you go - https://git.cloudron.io/cloudron/box/-/commit/2aa5c387c7a480fdc5048c64b04b9ce0eeb18dde . You can put %VERSION% in the footer now in the next release You da best! I need this for now so I never forget to re-apply my box patches.

I didn't even see this on the App Wish list, this is really cool. This is yet another one of those apps I could never get running on a VPS for my general use. Super work! Thanks to all involved.

All the pending issues are fixed, so this app is now stable.

@murgero I thought your comment was good, in fact Because @nebulon said, don't update Cloudron (but it doesn't affect existing installations). I will edit his post.

@doodlemania2 Thankfully - I was sponsored to get the app created

I have marked this app as stable now.

There's a couple of bugs/regressions. The firewall IP block list has a bug that it does not reliably block connections to the mail server alone. For this, please apply this change On ubuntu 16, the hardware transcoding feature does not work and it also makes the latest emby not run at all. For that, please apply this change

@imc67 said in LAMP with PHP 7.4 is now available: Could it be that this file is re-generated? That should be it, this file is indeed re-generated. It could be that you opened up the file immediately after the import. The file is re-created when the app starts up and until it starts up it will have the contents of the previous app.

There is a SOGo regression in 5.6 . https://forum.cloudron.io/topic/3161/sogo-connectivity-issue-with-cloudron-5-6 has the bug report and workaround.

@mehdi said in Documentation url change: (By the way, didn't you guys do the reverse URL move like a year ago or something ? ^^) I think last time around we tried to split the developer docs (into /developer) and the user docs. That went poorly since people were constantly struggling to find the developer docs. Lesson learnt and we ended up merging them again.

Alright, I had to go the database and reset the lock state of all the posts Unfortunately, this means I had to reset genuinely locked posts as well. But I think we can live with that. For future reference, I had to run this in the MongoDB shell: x = db.getCollection('objects') x.updateMany({ _key: { $regex: /^topic:\d+/ } }, { $set: { locked: 0 } }) On a side note, NodeBB code is so well done

TBH I think if it's content-focused, just go default Casper. The headers don't change regardless of light-dark-mode.

We usually take a day or two to find any regressions and would release a patch version then. Then again we would wait for 1 or 2 days in case a regression is still there. If it goes smooth we will put it for auto-update in a couple of days latest.

It is until 31.12.2020 for Germany.

Very fair - there's always one eh! But I consider them free penetration testers