I'm trying the vagrant box on the current master and it's failing during provisioning.
To be exactly during:
"Running setup.py install for cryptography"
...
"ImportError: No module named setuptools_ext"
the following rollback seems to mess up the pip installation itself on that box.
I'm totally new to redash and thinking about developing / contributing. So I'm curious if the recommended way to run redash on my dev machine is a) with the vagrant image, b) "native" or c) with the docker image?
If the vagrant is in fact still supported I could also have a look on fixing this, just want to be sure I'm not reviving some no longer supported legacy.
Yes, should upvote this. I use Redash at work and really like it.
I'm frontend developer and there are plenty of issues with "Frontend" label. Maybe I can help with some. But I'm not familiar with python and its tools, so it seems I can't easily set up development environment.
It seems there are many developers who are willing to help, but stuck on vagrant up =(
@44px You're so right :-( I will update the Vagrant box along with 1.0 release. I'm just wondering -- what will be more helpful: a new Vagrant box or just proper documentation on how to setup dev environment on Linux and OS/X?
It's good news. Thank you for response!
Vagrant box looks like more universal solution since it can be used on any OS and provides isolated environment (no need to install anything on host OS).
Opened #1480 to track the work on the dev guide. Keeping this one open until I'm done.
The developer guide has been updated along with new documentation on how to use Docker for easy setup of your dev environment (instead of Vagrant).
https://redash.io/help-onpremise/dev/guide.html
Thank you for all your feedback!
Your feedback on the new guide & flow is always welcomed.
Thank you for your work on this!
New docker dev env is easier to setup and works fine.
Thanks for the feedback!