v5.2.1

Change Log

• fix: Show correct src of bench source (#1055)
• fix: supervisor command does not require sudo (#1054)

v5.2

Change Log:

• fix: Update supervisord conf "better" (#1022)
• fix(install.py): Check if Py3.5+ before installing distro (#1049)
• fix: use remote_addr instead of user-defined header ip (#1024)
• fix: don't show warning message in developer mode (#1032)
• fix: run backups every 6 hours, rather than every minute per 6 hours (#1030)
• fix(playbooks): Use libssl1.1 for ubuntu >=18.04 (#1018)
• fix: ubuntu 20.04 easy install hang half way (#1048)
• fix: updated URL for MacOS guide (#1037)
• travis: Separate builds for setup, install script and tests (#1036)
• fix: Bump Nodejs v8 => v12 (#1043)
• fix(install): Show Debian 10 is supported, update MariaDB defaults (#1046)
• fix: maintain worker and worker.error logfile in dev mode (#1008)
• fix: trailing slash deleting apps folder (#1021)
• fix: populate bench.log via bench.utils.log (#1023)
• docs: re-link installation docs (#1009)
• feat: bench start --no-prefix (#1040)
• feat(playbooks): wkthmltox for Ubuntu 20 (#1019)

v5.1

Our default branch, develop has had a few changes since v5.0. We've decided to push only bug fixes to master and all other updates will continue to be pushed to develop and branch v5.x will be maintained as bench version 5 [stable]

Major Updates:

• bench removed from frappe_sudoers

now sudo bench commands will require passwords. The current frappe_sudoers file will only contain NOPASSWD setup for Nginx related commands.

• supervisor runs as frappe_user by default

Here, frappe_user refers to the user under which the current Frappe environment is setup.

Change Log:

• chore(tests): drop PY2 testing for frappe > v12 (#992)
• chore: changed bench.utils.log API prefix (#964)
• chore: drop dead code (#998)
• chore: renamed project to match with PyPI (#961)
• chore: set apps to None by default (#973)
• chore: skip restart on bench setup requirements (#975)
• docs: fix readme docker section (#990)
• docs: fixed typo on running update (#968)
• feat(bench update): allow pull-only update on specified apps (#921)
• feat: check for newer versions on PyPI (#960)
• feat: faster bench (#967)
• fix(backups): setup backups for bench sites (#972)
• fix(get-app): allow ssh urls (#995)
• fix(get-app): update node requirements (#983)
• fix(logging): cleaner bench logs (#999)
• fix(playbooks): pre v5.1 compatibility for playbooks folder (#988)
• fix(playbooks): wkhtmltopdf checksum string for debian 9 (#969)
• fix: IUS release repo (#1004)
• fix: Message per app when installing node deps (#959)
• fix: add playbooks in the python package (#980)
• fix: don't run yarn install while setting up py requirements (#1001)
• fix: exit with appropriate return code (#1006)
• fix: install node modules only if package.json exists (#985)
• fix: remove bench and supervisor from sudoers (#955)
• fix: restart supervisord process after change in conf (#991)
• fix: show warning if bench is not installed via PYPI (#934)
• refactor: bench readme and rename license file (#958)

v5.0

We're moving away from continuous deployment. For production usage, it is recommended to use the PyPI package. Remove the editable install from your system and run a pip install frappe-bench instead. All future updates can be handled through pip.

---

So there's been a lot of changes since the last release, about 800 commits in between. Some of the noteworthy changes are mentioned categorically:

Features:

• bench pip: utilizes the current Python's environment to update packages
• bench find: find benches from the specified path(via DFS)
• cleaner UX: formatted outputs
• executing bench commands in subdirectories

Development:

• Different CI tests for basic and production bench setups and easy install runs
• Cleaner and updated API usages

Other changes:

• fixed switch-to-branch
• fixed git depth while get-app
• updated cronjob for SSL renewal
• updated bench help commands and docs
• added "rollback" feature in case of failures during bench init

Deprecated:

• update_bench_on_update from config
• switch-to-master command
• bench shell command
• Removed auto_update from cronjob

---

This release was previously tracked at bench v5.0

v4.1

Minor fixes and moved to node6.x

Version 4.0

Improvements for frappe/erpnext v7 release

Version 3.1

Compatibility fixes between Celery and RQ configurations

Version 3.0

Deprecated Celery and moved to using Python RQ

If you have a Frappé app with background jobs that are NOT called via scheduler, you need to read Celery to Python RQ

Version 2.1

• Fixes dev installer for Mac OS X
• Permissive sudoers
• Improved release script

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?

1. frappe-bench/config.json deprecated and merged into frappe-bench/sites/common_site_config.json. This will be done automatically on bench update

2. Some keys in site_config.json / common_site_config.json have changed, which will be changed automatically on bench update.

   • celery_broker --> redis_queue with default as redis://localhost:6379
   • async_redis_server --> redis_socketio with default as redis://localhost:12311
   • cache_redis_server --> redis_cache with default as redis://localhost:11311

3. 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
   

4. 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 for webserver, socketio and various redis-server
   • bench setup production creates symlinks of nginx and supervisor with the bench's name

5. 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-redirects http:// to https://