Releases: frappe/bench
Version 2.0
Hi everyone,
We have merged bench v2
into master. Things can break. So, if you want to continue without disruption, you can change the bench branch to v1.x
.
Troubleshooting help at: https://discuss.erpnext.com/t/important-bench-version-2-see-this-before-you-run-bench-update/11352
What's new?
-
frappe-bench/config.json
deprecated and merged intofrappe-bench/sites/common_site_config.json
. This will be done automatically onbench update
-
Some keys in
site_config.json
/common_site_config.json
have changed, which will be changed automatically onbench update
.celery_broker
-->redis_queue
with default asredis://localhost:6379
async_redis_server
-->redis_socketio
with default asredis://localhost:12311
cache_redis_server
-->redis_cache
with default asredis://localhost:11311
-
File names in
frappe-bench/config
have changed. If you get any error about config, run:bench setup redis bench setup procfile # if production setup bench setup supervisor bench setup nginx
-
Multi-bench setup
- Assumes all benches are installed in parallel, i.e.
some-folder/frappe-bench-1
,some-folder/frappe-bench-2
, etc. - On
bench init
, loops through all benches' configuration and sets unique ports forwebserver
,socketio
and variousredis-server
bench setup production
creates symlinks of nginx and supervisor with the bench's name
- Assumes all benches are installed in parallel, i.e.
-
Other improvements
- A new installer using ansible (WIP) - for now creates development setup
(production setup yet to be implemented) - Test cases for bench and refactored code
- Nginx
https
config auto-redirectshttp://
tohttps://
- A new installer using ansible (WIP) - for now creates development setup
Version 1.0
This release marks the end of version 1 of bench. This version supports single bench per machine. The next version support multiple benches per machine.
This is the recommended release to use when migrating from older versions of frappe i.e. frappe version < 7.
Release v0.93
To be used for migration from Frappe/ERPNext v3 to v6
Fix python-mysqldb build issue
- Removed
patch mariadb-config
setup env
installs a patched python-mysqldb
Security Fix
If you installed Frappe/ERPNext using easy install script (setup_frappe.sh) or used the new bench setup production command between 11th November 2014 and 17th November 2014, there was a bug which configured supervisor to run the frappe processes as root. To rectify this, please run,
bench update --bench
bench patch fix-perms
Thanks to Marius Gedminas for reporting this.
Release v0.9
- New easy install script (unattended).
- Automated production setup.
- Ability to run
bench
commands from anywhere if /etc/frappe_bench_dir is set (automatically done by the easy install script).
eg,
echo /home/frappe/frappe-bench > /etc/frappe_bench_dir
- Automatically drops privileges if bench command is run as root if
frappe_user
is set inconfig.json
(automatically done by the easy install script). - Set remote MaridaDB host using,
bench set-mariadb-host
command.