asonix/mastodon
1
1
Fork 1
Code Issues Pull requests Projects Releases Wiki Activity

asonix/changes #11

Merged
asonix merged 8 commits from asonix/changes into asonix/downstream 2022-11-15 15:16:15 +00:00
Conversation 0 Commits 8 Files changed 6 +12 -5
asonix commented 2022-11-15 15:16:04 +00:00
Owner
Copy link

Upgrade notes

As always, make sure you have backups of the database before performing any upgrades. If you are using docker-compose, this is how a backup command might look: docker exec mastodon_db_1 pg_dump -Fc -U postgres postgres > name_of_the_backup.dump

Update steps

The following instructions are for updating from 3.5.3.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

  • The recommended Ruby version has been bumped to 3.0.4. You can upgrade, or you can continue using the old version by overwriting the ``.ruby-version file with e.g. 3.0.3 which was recommended previously
  • Install dependencies: bundle install and yarn install

Both Docker and non-Docker:

⚠️ Incoming federated activity now uses a new ingress queue in Sidekiq. If you customize Sidekiq processes/queues, ensure that there is at least one process handling the ingress queue.

  1. Run the pre-deployment database migrations by specifying the SKIP_POST_DEPLOYMENT_MIGRATIONS=true environment variable:
  • Non-Docker: SKIP_POST_DEPLOYMENT_MIGRATIONS=true RAILS_ENV=production bundle exec rails db:migrate
  • Docker: docker-compose run --rm -e SKIP_POST_DEPLOYMENT_MIGRATIONS=true web rails db:migrate
  1. Precompile the assets:
  • Non-Docker: RAILS_ENV=production bundle exec rails assets:precompile
  • Docker: The assets are already precompiled during the build step
  1. Restart all Mastodon processes
  2. Now that the new code is running, we can finish the database migrations. This will run the post-deployment ones:
  • Non-Docker: RAILS_ENV=production bundle exec rails db:migrate
  • Docker: docker-compose run --rm web rails db:migrate
  1. Restart all Mastodon processes
## Upgrade notes > As always, make sure you have backups of the database before performing any upgrades. If you are using docker-compose, this is how a backup command might look: `docker exec mastodon_db_1 pg_dump -Fc -U postgres postgres > name_of_the_backup.dump` ## Update steps The following instructions are for updating from 3.5.3. If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations. #### Non-Docker only: - The recommended Ruby version has been bumped to 3.0.4. You can upgrade, or you can continue using the old version by overwriting the ``.ruby-version file with e.g. `3.0.3` which was recommended previously - Install dependencies: `bundle install` and `yarn install` #### Both Docker and non-Docker: > ⚠️ Incoming federated activity now uses a new `ingress` queue in Sidekiq. If you customize Sidekiq processes/queues, ensure that there is at least one process handling the `ingress` queue. 1. Run the pre-deployment database migrations by specifying the `SKIP_POST_DEPLOYMENT_MIGRATIONS=true` environment variable: - Non-Docker: `SKIP_POST_DEPLOYMENT_MIGRATIONS=true RAILS_ENV=production bundle exec rails db:migrate` - Docker: `docker-compose run --rm -e SKIP_POST_DEPLOYMENT_MIGRATIONS=true web rails db:migrate` 2. Precompile the assets: - Non-Docker: `RAILS_ENV=production bundle exec rails assets:precompile` - Docker: The assets are already precompiled during the build step 3. Restart all Mastodon processes 4. Now that the new code is running, we can finish the database migrations. This will run the post-deployment ones: - Non-Docker: `RAILS_ENV=production bundle exec rails db:migrate` - Docker: `docker-compose run --rm web rails db:migrate` 5. Restart all Mastodon processes
asonix added 8 commits 2022-11-15 15:16:06 +00:00
b59683c156
Bump nokogiri from 1.13.8 to 1.13.9 (#20041) 
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.13.8 to 1.13.9.
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md)
- [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.13.8...v1.13.9)

---
updated-dependencies:
- dependency-name: nokogiri
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
b46b7c3d5e
Use "unsafe-wasm-eval" instead of "unsafe-eval" in script-src CSP (#20606) 
* Add "unsafe-eval" to script-src CSP

* Use 'unsafe-wasm-eval' instead of 'unsafe-eval'
asonix merged commit 66348a04d1 into asonix/downstream 2022-11-15 15:16:15 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: asonix/mastodon#11
No description provided.
Delete branch "asonix/changes"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?