540a0640a6
The upgrade process was triggering the database migrations, and then calling `User.find()`. This is problematic because the `users` table may have been changed by the migrations, and accessing it with the 'old code' will raise an exception. This commit tweaks the Upgrader so that it loads the user object into memory **before** running database migrations. |
||
|---|---|---|
| .github/workflows | ||
| admin/assets/javascripts/discourse | ||
| app/controllers/docker_manager | ||
| assets/stylesheets/common | ||
| config | ||
| lib/docker_manager | ||
| scripts | ||
| spec | ||
| test/javascripts | ||
| .discourse-compatibility | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .npmrc | ||
| .prettierrc.cjs | ||
| .rubocop.yml | ||
| .streerc | ||
| .template-lintrc.cjs | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| README.md | ||
| package.json | ||
| plugin.rb | ||
| pnpm-lock.yaml | ||
| translator.yml | ||
README.md
Docker Manager
This plugin works with the Discourse docker image. It allows you to perform upgrades via the web UI and monitor activity in the container.
Running tests
- Ruby
- Run
RAILS_ENV=test bin/rails "plugin:spec[docker_manager]"in your discourse directory
- Run
- JS
- Run
RAILS_ENV=test bin/rails "plugin:qunit[docker_manager]"in your discourse directory
- Run
Contributing
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request
License
MIT