@@ -8,21 +8,29 @@ The nice thing is that it allows you to setup a postactivate command which can
8
8
setup your environment for you. Below is a sample postactivate script which
9
9
performs several actions upon getting into the project.
10
10
11
- $ workit someproject
12
-
13
- #! /bin/zsh
14
-
15
- # variables needed for some script
16
- export JS_PATH="$PROJ_PATH/src";
17
-
18
- # define a custom function we can use to launch tests
19
- qunit() { chrome "http://project/javascript/tests/runtests.html" }
20
-
21
- # run ctags so vim is up to date when we start working on a project
22
- ctags -f $PROJ_PATH/tags -R $PROJ_PATH/src 2> /dev/null &!
23
-
24
- # use the reusable methods for start/stop serives. This project shuts down mysql
25
- # and starts up pgsql for use
26
- zmysql_stop
27
- zpgsql_start
11
+ > $ workit someproject
12
+ >
13
+ > #! /bin/zsh
14
+ >
15
+ > # variables needed for some script
16
+ > export JS_PATH="$PROJ_PATH/src";
17
+ >
18
+ > # define a custom function we can use to launch tests
19
+ > qunit() { chrome "http://project/javascript/tests/runtests.html" }
20
+ >
21
+ > # run ctags so vim is up to date when we start working on a project
22
+ > ctags -f $PROJ_PATH/tags -R $PROJ_PATH/src 2> /dev/null &!
23
+ >
24
+ > # use the reusable methods for start/stop serives. This project shuts down mysql
25
+ > # and starts up pgsql for use
26
+ > zmysql_stop
27
+ > zpgsql_start
28
+
29
+ You can also run a postdeactivate to shut down or clear settings from the
30
+ project. This is run whenver the command `deactivate` is run or you switch to
31
+ another project.
32
+
33
+ Projects are directories within the directories specified in the WORKIT_HOME.
34
+ You can create an array of locations to used. Any directory in these paths will
35
+ be used to complete/switch projects.
28
36
0 commit comments