Release/5.3.0 #698
Merged
Release/5.3.0 #698
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hyperlink DOIs to preferred resolver
Bumps [rack](https://github.com/rack/rack) from 2.0.7 to 2.0.8. - [Release notes](https://github.com/rack/rack/releases) - [Changelog](https://github.com/rack/rack/blob/master/CHANGELOG.md) - [Commits](rack/rack@2.0.7...2.0.8) Signed-off-by: dependabot[bot] <support@github.com>
Bump rack from 2.0.7 to 2.0.8
Bumps [rake](https://github.com/ruby/rake) from 12.3.1 to 13.0.1. - [Release notes](https://github.com/ruby/rake/releases) - [Changelog](https://github.com/ruby/rake/blob/master/History.rdoc) - [Commits](ruby/rake@v12.3.1...v13.0.1) Signed-off-by: dependabot[bot] <support@github.com>
when doing a restore some functions would fail to find other functions or tables. Prefixing these with public. fixes problem.
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.8.5 to 1.10.8. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md) - [Commits](sparklemotion/nokogiri@v1.8.5...v1.10.8) Signed-off-by: dependabot[bot] <support@github.com>
creates docker image pecan/betydb that contains full dump of database and script to quickly restore.
instead of depending on hardcoded url, use information in database.
Remove gunload, was deprecated and removed #551
…-1.10.8 Bump nokogiri from 1.8.5 to 1.10.8
Bump rake from 12.3.1 to 13.0.1
use public. prefix in functions
docker image with databae
use database to get sync info
Use github actions instead of travis - push to github registry and dockerhub - remove travis scripts
* script to dump database * docker push + cron * only push to dockerhub if username/password set * only run on PecanProject/bety * script to easily add users to BETY * make sure to use environment variable for secret The environment variable SECRET_KEY_BASE was ignored. This fixes #696. If you had SECRET_KEY_BASE set, please unset it now, otherwise you can no longer login. load-bety.sh script now uses script/betyuser.sh to add users with correct password.
typo in dump workflow
This was referenced Mar 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This marks official release of BETY 5.3.0, following are the release notes.
Please read the next two steps to upgrade your system. Not following these steps could break your instance of BETY.
Password encryption
The previous versions of BETY would ignore the environment variable SECRET_KEY_BASE and use the default value defined in
config/defaults.yml. If you have set SECRET_KEY_BASE and upgrade BETY you will not be able to login anymore!. It is best to remove SECRET_KEY_BASE if set and default back to the default SECRET_KEY_BASE.This release requires a migration.
Steps Needed for Upgrade (Non Docker)
bundle exec rake db:migrate RAILS_ENV=productiontouch tmp/restart.txtSteps Needed for Upgrade (Docker)
docker-compose rm --stop betydocker-compose pull betydocker-compose run --rm bety migratedocker-compose up -d betyPEcAn dump script
There is a change to the script/dump.bety.sh that will keep the creation/update times of the users in the database. This is needed for future work to speed up database synchronizations. If you use the script standalone, please copy latest script.
Complete list of changes
Fixes
Added