Instead of having the cognitive load of checking if this is indeed the inverse of `visible`, just wrap it all in sql not
I'd love to have rails take care of this but haven't found something for that
Previous setups will already contain folders created as root. Making a different user the default
will break these setups. So just make it opt-in instead.
Previous commits made docker run as a different user than root.
Unfortunately the checkout action creates the files as root, regardless of what
user might actually be running. As such, docker commands need to be run as
root as well to not run into permission issues when creating the `tmp` folder for example.
This basically reverts 2de0ebb5b8 for CI but since that was intended for local development its not a big deal
Volumes get created on the host as the user that docker is running as (root, most likely)
This is annoying, and creates issues when running the image as a non-root user
* [Posts] Tweak the janitor toolbar
* [Posts] Remove the duplicate count from the modbar
* [Posts] More tweaks to the janitor toolbar
Based on the input from the janitors themselves.
* Linting
The app directory isn't marked as safe => a test fails for accessing nil
Not sure how there's only 1 test failing because of this.
Either way, this is more correct
This removes the need for all the ruby-lsp setup stuff.
ruby-lsp will try to install the debug gem which contains native code, add that to the gemfile so it doesn't cause trouble.
I'm probably going to remove the rubocop/test compose services at some point. With devcontainers you are just able to run the commands directly.
Also adds back something to .env.sample that I accidentally removed last commit.
The installation instructions to properly set up ruby-lsp are pretty convoluted at the moment,
I'm hoping that this will improve in the future. I openend https://github.com/Shopify/ruby-lsp/issues/1303 Let's see how that goes
It just works.
Requires a bit of a workaround for the .rubocop.yml env setup currently in use but thats alright.
The companion ruby-lsp-rails doesn't do much right now but I imagine that to become quite powerful in the future.
