Step 1. Set up kbase-ui work environment

Read the prerequisites guide to ensure your host machine is up to snuff.

macOS

A kbase-ui project requires a dedicated directory, into which you will clone the repos you are working with. Go ahead and create this folder, which we’ll refer to in this document as project.
First, you need to ensure that you have a fork of kbase-ui at github.
Open a terminal into this folder, either the built-in Terminal program, iTerm, or your terminal app of choice.
Clone the kbase/kbase-ui repo into this folder:
```
git clone -b develop https://github.com/{YOUR_ACCOUNT}/kbase-ui
```
where {YOUR_ACCOUNT} is your personal github account to which you have forked the upstream https://github.com/kbase/kbase-ui. Of course, if you prefer to work with ssh authorization, use that form instead:
```
git clone -b develop ssh://git@github.com/{YOUR_ACCOUNT}/kbase-ui
```
Create and launch the kbase-ui image:
```
cd kbase-ui
make dev-start
```
Since that container is now running in the terminal, you’ll need to open a new terminal window for the next steps. ¹
Point ci.kbase.us to your local computer:

Edit
```
sudo vi /etc/hosts
```
adding the line
```
127.0.0.1	ci.kbase.us
```
at the end of the file, then save it [Shift][Z][Z]

Why? There have been complaints about this. However, it is a small task, and provides some advantage in being able to seamlessly develop and test against all kbase environments (ci, next, appdev, prod, etc.) Also, some ui code determines the correct full url based on the browser window current location.
Open a browser, in private browsing mode, to https://ci.kbase.us.
Since the proxy uses a self-signed certificate to support https, your browser will likely complain. Just suffer through the prompts to allow the connection to proceed.²

If you tire of the self-signed cert dance, you may want to try using a local kbase cert
You should now see kbase-ui 😊
When done, you can simply press [Control][C] in the original terminal window to stop the containers.³
1. If you won’t be conducting further builds for this instance, you’ll want to clear out the intermediate build image:⁴
```
make dev-clean
```

Next Step

Step 2. Create Plugin Repos

-–

If you use Terminal or iTerm, pressing [Cmd][T] will open a new tab in the terminal window, with the same directory. ↩
If your browser hangs when attempting to connect, you should have better luck using the private mode of your browser. Both Safari and Chrome work fine in private mode with self-signed certs, Firefox will still hang. ↩
Currently docker-compose does not always clean up after itself when using [Control][C] to stop it; see this github issue. ↩
This also removes the Docker network “kbase-dev” created during image-building process. ↩