If you don’t use these tools, remove the venvwrapper & workon my_project portion of the examples. They just make working with multiple Python projects easier. Note that you do not need to use either of those tools to set up or tear down a Django development environment with Tmux. My example uses virtualenv and virtualenvwrapper. If you are a Screen user, then I suggest you try Tmux, but you can probably achieve a similar method to the one described in this post using Screen and one of the automation scripts designed to work with it. So, I tried Tmux, and I haven’t gone back. However, I grew dissatisfied with the pace of development in the project, the lack of new features, and the inconsistent availability of vertical splits across different platforms. Until earlier this year, I had used GNU Screen for managing persistent terminal sessions. Virtualenvwrapper, a set of extensions to virtualenvīy the end of this post, you will have a new command available in your terminal that will create a Tmux session with multiple views into your Django project.Virtualenv, a tool for creating isolated Python environments.Tmuxinator, a nice Ruby gem for automating Tmux. ![]() Tmux, a terminal multiplexer like GNU Screen. ![]() While my examples are geared toward Django development, the approach I describe works equally well with Rails and other frameworks. Without automation, you have to manually kill and reconstruct any Django shell and development server instances for each branch (and sometimes the database shell, too). I’ve found that such automation is most useful when switching between branches in source control. This post describes how to use a few common tools to instantly set up and tear down Django development environments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |