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

How about a dynamic total of apps in the Store (minus unstables)? --- currently = 84

This app is marked as stable now.

@Hillside502 Ah that explains why the value of 2 never worked for me till I changed system settings.

I have deployed the referral link change. You will now see the full referral link. If you see the link being clipped, just refresh the page (I think it's because browser has cached the old style sheet or some CDN issue, not sure).

I have marked this app as stable. Forum section is at https://forum.cloudron.io/category/95/trilium

Love this! Do you fancy adding some useful plugins to the mix? https://github.com/YOURLS/awesome-yourls And theme option: https://github.com/tomslominski/infinity-squared https://github.com/Flynntes/Sleeky

I have added tests and marked pixelfed as stable. Thanks all for testing!

There is also https://git.cloudron.io/cloudron/tutorial-nodejs-app which is a template for a custom nodejs app

for what it worth, in my /etc/docker/daemon.json I always define. { "no-new-privileges": false } which from what I understand prevent container processes to gain additional privileges after their start. ref: Docker Daemon more explanation from the Project Atomic by RedHat

We now have tests for Metabase and I have marked it as stable.

@necrevistonnezr Good catch. Looks like we got the uniqueness constraint in 5.1 itself wrong. Currently, it is (name, userid). It shoud be (name, appid, userid) or maybe even just (appid, userid). We cannot fix it for this release but maybe the next since we try to do db changes only in new releases.

@girish Sounds promising, Girish. Thanks for the update. I responded to another post from @mehdi in which he pointed at https://www.meilisearch.com/. Not sure if this is something....