How to reload the vagrant box webserver after code changes?


#1

What is the recommended flow for developing with re:dash with the vagrant box?
Specifically, when I make a code change, what is the shortest path to updating the vagrant box’s server?
The documentation on readthedocs is relatively limited in this respect…

(p.s. I also suggest another category in this discuss form for development, to make it easier to filter/search.)


#2

Or perhaps a better question might be: what’s the best process to debug code changes?


#3

How do you run your Redash server in Vagrant?
What code do you want to reload - the frontend (HTML/JS) or the Python code?

(add Development category and moved this post there)


#4

How do you run your Redash server in Vagrant?
./bin/vagrant_ctl.sh start

What code do you want to reload - the frontend (HTML/JS) or the Python code?
Well, it would be useful to know how to reload the various pieces. It would ultimately help occasional contributors like me/my team to get in there to make pull requests for small fixes.


#5

When you use vagrant_ctl.sh it runs the web server in development mode, which means it will restart automatically on every code change. You will need to manually restart this process, if you want the background workers (Celery) to pick up changes.

To update the frontend stuff, nothing special needs to be done, except of reloading the page (real reload, not just page navigation).