# Contributing
## How-To
### Contribute code
1. Start the wasmCloud host using the `wash` CLI. Read more about it [here](#start-the-wasmcloud-host-using-wash-cli).
1. Ensure the Nats service is running with the websocket listener enabled.
2. Start a local frontend development server. Read more about it [here](#start-a-local-ui-development-server).
3. Make changes to the UI.
4. Commit your changes.
5. Open a pull request.
6. Wait for the CI to pass.
7. Wait for a maintainer to review your changes.
8. Wait for a maintainer to merge your changes.
9. 🚀 🏁 Done
### Start a local UI development server
Run the following command to start a local frontend development server:
```bash
npm run dev
```
### Start the wasmCloud Host using wash CLI
Run the following command to start the wasmCloud host using the wash CLI:
```bash
wash up
```
### Explanations
#### Nats
`wasmcloud` uses [NATS](https://nats.io/) as its message broker. The `wash` CLI can be used to start a local NATS
or connect to an existing NATS server.
The Washboard UI connects to a NATS server at [ws://localhost:4001 by default][0], although this can be overridden via
the UI.
In case you use `wash up` to spawn up the Nats server, you can control the websocket port using the
`--nats-websocket-port` flag or `NATS_WEBSOCKET_PORT` environment variable. For example:
```bash
wash up --nats-websocket-port 4008
```
Otherwise, verify the port you are using to connect to the NATS server. Visit [Nats Websocket Configuration][1] for more
information.
[0]: https://github.com/wasmCloud/wash/blob/a74b50297496578e5e6c0ee806304a3ff05cd073/packages/washboard/src/lattice/lattice-service.ts#L70
[1]: https://docs.nats.io/running-a-nats-service/configuration/websocket/websocket_conf