Dress to Impress, a big fancy Neopets customization tool!
Matchu
d79b6b6c33
I upgraded our local MariaDB for compatibility with the latest server dumps (https://mariadb.org/mariadb-dump-file-compatibility-change/), and I thiiiink what I'm seeing is that, also in this version of MariaDB, the default value for the `ssl` option is `true`? That is, command-line clients will try to connect over SSL by default—which isn't generally supported on development servers, where this task runs. I could probably fix this with a change to my local config? But I figure I can't really picture a scenario where this option being set in the task would be *wrong*, but I *can* see it saving future people time if they're working in a similar environment. So, let's just set it! |
||
|---|---|---|
| .devcontainer | ||
| .husky | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| deploy | ||
| lib | ||
| public | ||
| test | ||
| vendor | ||
| .eslintrc.json | ||
| .gitignore | ||
| .ruby-version | ||
| .solargraph.yml | ||
| .yarnrc.yml | ||
| config.ru | ||
| falcon.rb | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE.md | ||
| package.json | ||
| Procfile.dev | ||
| Rakefile | ||
| README.md | ||
| yarn.lock | ||
