workspace 0.4.2

a command-line project manager
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87

## workspace [![build status](https://travis-ci.com/matthias-t/workspace.svg?branch=master)](https://travis-ci.com/matthias-t/workspace) [![crates.io](https://img.shields.io/crates/v/workspace.svg)](https://crates.io/crates/workspace)

`ws` is a CLI to manage and interpret small YAML files that specify tasks to open a project like opening an editor, launching a server or visiting a chat or documentation in the browser. It can be used to efficiently switch between work and side projects.

### Installation

```bash
cargo install workspace
```

Then setup the `ws` command in your shell:

-   **bash**: Add this line to your `.bashrc`

    ```bash
    eval $(workspace shell bash)
    ```

-   **fish**: Add this line to your `config.fish`

    ```fish
    workspace shell fish | source -
    ```

-   **PowerShell**: Add this line to your `profile.ps1`

    ```powershell
    Invoke-Expression "$(workspace shell posh)"
    ```

> `workspace shell` prints a shell function `ws` that delegates output from `workspace` but intercepts commands to run. This lets you change the directory and run commands directly in the shell, e.g. if they need user input.

### Documentation

For the CLI, see:
```
ws --help
```

Workspaces can have the following fields:

-   `path`, list of strings

     path to the workspace

-   `tabs`, list of strings

     tabs to open in `$BROWSER`

-    `commands`, table

     -   `local`, list of strings

         commands to execute in the current shell

     -   `background`, list of strings

         commands to execute as background processes

     -   `external`, list of strings

         commands to execute in a new `$TERMINAL`

> Note: `path` is mandatory and created automatically by `ws new`

For example, this is the workspace I use for my blog:

```
path: /home/matthias/code/web/blog/

commands:
  local:
  - git status
  - sudo systemctl start nginx
  background:
  - code -r .
  external:
  - gulp

tabs:
- https://developer.mozilla.org/en-US/
- localhost
```

It will `cd` into `~/code/web/blog/`, print the git status, open the directory
in visual studio code, start the `gulp` build in a new terminal, launch `nginx`
to serve the files and open `localhost` and MDN in the browser.