You think that i am running it through supervisor? But i run it manually and think that i am running it right way (maybe i am wrong). I am starting bench manually, after every vagrant up or reload.
I am doing it with this command:
ok thanks, will try this too, i had some problems with installing it on my mac few months ago when i started. So i choosed vagrant box. But now i am little bit more familiar with erpnext, so maybe i will be able run it also without vagrant.
bench migrate should update all the python changes made wouldn’t it?
So have your vagrant site up and running.
Make code changes in atom
switch to terminal
bench migrate will read JSON files and make changes to the database accordingly
Maybe used in conjunction with bench reload-doc
bench --site mysite.name reload-doc MYMODULE MYDOCTYPE MYDOCNAME
Or use one of the update variants listed below
Pulls changes for bench-repo and all apps, applies patches, builds JS and CSS, and then migrates.
bench update --pull
Pull changes in all the apps in bench
bench update --patch
Run migrations for all sites in the bench
bench update --build
Build JS and CSS artifacts for the bench
bench update --bench
bench update --requirements
bench update --restart-supervisor
Restart supervisor processes after update
@janecek.mato I know! I don’t know what else it could be. This is exactly that behavior which is why I’m so confused. To be clear it should be in site_config.json, not common_site_config.json
@pipech Yes, when you make changes to python, it works that way, at least on localhost. You can set up remote editing packages with your text editor to make changes to an offsite/cloud server. I know these is available for Atom and VSCode at the very least, it’s usually a combination of mate/rmate and ftp.