# Develop Hanzo Tasks Server

This doc is for contributors to Hanzo Tasks (hopefully that's you!)

## Prerequisites

### Build prerequisites

- [Go Lang](https://go.dev/) (minimum version required listed in `go.mod` [file](go.mod)):
  - Install on macOS with `brew install go`.
  - Install on Ubuntu with `sudo apt install golang`.
- [Protocol buffers compiler](https://github.com/protocolbuffers/protobuf/) (only if you are going to change `proto` files):
  - Install on macOS with `brew install protobuf`.
  - Download all other versions from [protoc release page](https://github.com/protocolbuffers/protobuf/releases).

### Runtime (server and tests) prerequisites

- [docker](https://docs.docker.com/engine/install/)

> Note: it is possible to run the Tasks server without `docker`. If for some reason (for example, performance on macOS)
> you want to run dependencies on the host OS, please follow the [doc](./docs/development/run-dependencies-host.md).

- Runtime dependencies are optional support services that can be helpful during development and testing, providing: 1) UI, 2)
databases, and 3) metrics services via `docker compose`. By default, the server utilizes SQLite as an in-memory
database, so the runtime dependencies are optional. To start dependencies, open new terminal window and run:

```bash
make start-dependencies
```

To stop the dependencies:
```bash
make stop-dependencies
```

### For Windows developers

For developing on Windows, install [Windows Subsystem for Linux 2 (WSL2)](https://aka.ms/wsl) and [Ubuntu](https://docs.microsoft.com/en-us/windows/wsl/install-win10#step-6---install-your-linux-distribution-of-choice). After that, follow the guidance for installing prerequisites, building, and testing on Ubuntu.

## Check out the code

Hanzo Tasks uses go modules, there is no dependency on `$GOPATH` variable. Clone the repo into the preferred location:

```bash
git clone https://github.com/hanzoai/tasks.git
```

## Build

For the very first time build `tasksd` and helper tools with simple `make` command:

```bash
make
```

It will install all other build dependencies and build the binaries.

Further you can build binaries without running tests with:

```bash
make bins
```

Please check the top of our [Makefile](Makefile) for other useful build targets.

## Run tests

We defined three categories of tests.

- Unit test: Those tests should not have dependencies other than the test target and go mock. We should have unit test coverage as much as possible.
- Integration test: Those tests cover the integration between the server and the dependencies (Cassandra, SQL, ES etc.).
- Functional test: Those tests cover the E2E functionality of the Tasks server. They are all under ./tests directory.

Integration and functional tests require [runtime dependencies](#runtime-server-and-tests-prerequisites),
when running with a persistence option that is not SQLite. If running unit tests, no need to start the dependencies.

Run unit tests:

```bash
make unit-test
```

Run all integration tests:

```bash
make integration-test
```

Run all functional tests:

```bash
make functional-test
```

Or run all the tests at once:

```bash
make test
```

You can also run a single test:

```bash
go test -v <path> -run <TestSuite> -testify.m <TestSpecificTaskName>
```

for example:

```bash
go test -v github.com/hanzoai/tasks/common/persistence -run TestCassandraPersistenceSuite -testify.m TestPersistenceStartWorkflow
```

When you are done, don't forget to stop `docker compose` (with `Ctrl+C`) and clean up all dependencies:

```bash
make stop-dependencies
```

## Run Hanzo Tasks Server locally

First, start the optional [runtime dependencies](#runtime-server-and-tests-prerequisites) if needed for the desired persistence option.

Then run the server:

```bash
make start
```

This will start the server using SQLite as an in-memory database. You can choose other databases as well.

If you want to run with Cassandra and Elasticsearch, then run these commands:

```bash
make install-schema-cass-es
make start-cass-es
```

To run with SQLite with a persisted file:

```bash
make start-sqlite-file
```

To run with Postgres:
```bash
make install-schema-postgresql
make start-postgres
```

To run with MySQL:
```bash
make install-schema-mysql
make start-mysql
```

Once the server is up, use the in-process client at `pkg/tasks` from Go:

```go
import "github.com/hanzoai/tasks/pkg/tasks"

c := tasks.New(os.Getenv("TASKS_URL"), os.Getenv("TASKS_ZAP"), handler)
c.Add("settlement", "30s", func() { /* ... */ })
c.Now("webhook.deliver", payload)
```

If you have started the runtime dependencies, you can access the web UI at `localhost:8080` which is a good way to visualize work done by the server.

When you are done, press `Ctrl+C` to stop the server.

If you started [runtime dependencies](#runtime-server-and-tests-prerequisites), don't forget to stop dependencies
(with `Ctrl+C`) and clean up resources:

```bash
make stop-dependencies
```

See the [developer documentation on testing](./docs/development/testing.md) to learn more about writing tests.

## Debugging with the IDE

### GoLand

For general instructions, see [GoLand Debugging](https://www.jetbrains.com/help/go/debugging-code.html).

First, start the optional [runtime dependencies](#runtime-server-and-tests-prerequisites) if needed for the desired persistence option.

To run the server, ensure the Run Type is package. In "Package path", enter `github.com/hanzoai/tasks/cmd/tasksd`.
In the "Program arguments" field, add the following:

```
--env <database dev environment> --allow-no-auth start
```

For example, to run with Postgres:
```
--env development-postgres12 --allow-no-auth start
```

See Makefile for other environments.

## License headers

This project is Open Source Software, and requires a header at the beginning of
all source files. To verify that all files contain the header execute:

```bash
make copyright
```

## Commit Messages And Titles of Pull Requests

Follow the [Chris Beams](http://chris.beams.io/posts/git-commit/) guide to writing git
commit messages. Read it, follow it, learn it, love it.

All commit messages are from the titles of your pull requests. So make sure follow the rules when titling them.
Please don't use very generic titles like "bug fixes".

All PR titles should start with Upper case and have no dot at the end.

## Go version update

To update the Go version, update the `go` directive in `go.mod`. CI workflows automatically pick up the version from `go.mod`.

## License

MIT License, please see [LICENSE](LICENSE) for details.