You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ warpdrive project --create mydjangosite
Error: unknown command "project" for "warpdrive"
Run "warpdrive help for usage.
Not sure if docs are out of date or whether the Pypi package is out of date. I've got warpdrive==0.34.0 according to pip freeze.
One other small point. It seems strange to have an entry in my bash profile that points to a virtualenv. I started out with a virtualenv dedicated to the project to that's where it ended up. Maybe I was supposed to create a new virtualenv with just warpdrive in it but that goes against my usual "one virtualenv per project" habit. In any case - making the thinking behind this clear in the docs would be helpful.
The text was updated successfully, but these errors were encountered:
The project sub command only exists if you had incorporated the shell functions into your shell profile scripts. Only Bourne style shells are support, eg. bash.
If you don't want to have warpdrive installed as a global command, then manage your own virtual environments and install warpdrive into the virtual environment yourself and use it from there. The globally installed version is only to bootstrap a virtual environment for you and activate it, with warpdrive installed into it already. So you can skip that so long as you install warpdrive into your own virtual environment.
Not sure if docs are out of date or whether the Pypi package is out of date. I've got warpdrive==0.34.0 according to pip freeze.
One other small point. It seems strange to have an entry in my bash profile that points to a virtualenv. I started out with a virtualenv dedicated to the project to that's where it ended up. Maybe I was supposed to create a new virtualenv with just warpdrive in it but that goes against my usual "one virtualenv per project" habit. In any case - making the thinking behind this clear in the docs would be helpful.
The text was updated successfully, but these errors were encountered: