# Unify the two local zed scripts, take a flag for an instance count \(\#3106\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/29ccdb3cd9a81bbec7e8f622d6ca2ee276f1c0fb)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 29ccdb3cd9a81bbec7e8f622d6ca2ee276f1c0fb

Requested commit: 29ccdb3cd9a81bbec7e8f622d6ca2ee276f1c0fb

Commit: 29ccdb3cd9a81bbec7e8f622d6ca2ee276f1c0fb

Tree: d3cda365f76a728308f419e6301b029a2a875320

Author: Max Brunsfeld

Committer: GitHub

## Message

````
Unify the two local zed scripts, take a flag for an instance count (#3106)

This PR introduces a new script for running Zed against a local collab
server, called `script/zed-local`. This script replaces the two existing
scripts that we had for this purpose: `script/zed-with-local-servers`
and `script/start-local-collaboration`.

By default, the script starts one single instance of Zed, but you can
pass a numeric flag to start 1, 2, 3 or 4 instances. So to start up two
instances side by side, (like `start-local-collaboration` script), you'd
do this:

```
script/zed-local -2
```

But you can also start *three* (or even four) instances, each taking up
a quarter of the screen, like this:

```
script/zed-local -3
```

Like before, you can pass other arguments to the script, and they will
be passed through to the first zed instance.

Also, unlike the `start-local-collaboration` script, this script now
requires a call to GitHub to determine your GitHub username. It just
logs you in as Nathan by default, unless you set `ZED_IMPERSONATE`
explicitly.
````

## Parents

- [b2d735e573e830a3b4409e998037b6ce630e50b3](https://git.cafe/gitcafe/zed/commit/b2d735e573e830a3b4409e998037b6ce630e50b3?format=markdown)

- [1e4f5145cf156344e35f451ebb44722fde9111fc](https://git.cafe/gitcafe/zed/commit/1e4f5145cf156344e35f451ebb44722fde9111fc?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/29ccdb3cd9a81bbec7e8f622d6ca2ee276f1c0fb?format=markdown)