base on Harness Open Source is an end-to-end developer platform with Source Control Management, CI/CD Pipelines, Hosted Developer Environments, and Artifact Registries. # Harness Harness Open Source is an open source development platform packed with the power of code hosting, automated DevOps pipelines, hosted development environments (Gitspaces), and artifact registries. ## Overview Harness Open source is an open source development platform packed with the power of code hosting, automated DevOps pipelines, Gitspaces, and artifact registries. ## Running Harness locally > The latest publicly released docker image can be found on [harness/harness](https://hub.docker.com/r/harness/harness). To install Harness yourself, simply run the command below. Once the container is up, you can visit http://localhost:3000 in your browser. ```bash docker run -d \ -p 3000:3000 \ -p 22:22 \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /tmp/harness:/data \ --name harness \ --restart always \ harness/harness ``` > The Harness image uses a volume to store the database and repositories. It is highly recommended to use a bind mount or named volume as otherwise all data will be lost once the container is stopped. See [developer.harness.io](https://developer.harness.io/docs/open-source) to learn how to get the most out of Harness. ## Where is Drone? Harness Open Source represents a massive investment in the next generation of Drone. Where Drone focused solely on continuous integration, Harness adds source code hosting, developer environments (gitspaces), and artifact registries; providing teams with an end-to-end, open source DevOps platform. The goal is for Harness to eventually be at full parity with Drone in terms of pipeline capabilities, allowing users to seamlessly migrate from Drone to Harness. But, we expect this to take some time, which is why we took a snapshot of Drone as a feature branch [drone](https://github.com/harness/harness/tree/drone) ([README](https://github.com/harness/harness/blob/drone/.github/readme.md)) so it can continue development. As for Harness, the development is taking place on the [main](https://github.com/harness/harness/tree/main) branch. For more information on Harness, please visit [developer.harness.io](https://developer.harness.io/). For more information on Drone, please visit [drone.io](https://www.drone.io/). ## Harness Open Source Development ### Pre-Requisites Install the latest stable version of Node and Go version 1.20 or higher, and then install the below Go programs. Ensure the GOPATH [bin directory](https://go.dev/doc/gopath_code#GOPATH) is added to your PATH. Install protobuf - Check if you've already installed protobuf ```protoc --version``` - If your version is different than v3.21.11, run ```brew unlink protobuf``` - Get v3.21.11 ```curl -s https://raw.githubusercontent.com/Homebrew/homebrew-core/9de8de7a533609ebfded833480c1f7c05a3448cb/Formula/protobuf.rb > /tmp/protobuf.rb``` - Install it ```brew install /tmp/protobuf.rb``` - Check out your version ```protoc --version``` Install protoc-gen-go and protoc-gen-go-rpc: - Install protoc-gen-go v1.28.1 ```go install google.golang.org/protobuf/cmd/[email protected]``` (Note that this will install a binary in $GOBIN so make sure $GOBIN is in your $PATH) - Install protoc-gen-go-grpc v1.2.0 ```go install google.golang.org/grpc/cmd/[email protected]``` ```bash $ make dep $ make tools ``` ### Build First step is to build the user interface artifacts: ```bash $ pushd web $ yarn install $ yarn build $ popd ``` After that, you can build the Harness binary: ```bash $ make build ``` ### Run This project supports all operating systems and architectures supported by Go. This means you can build and run the system on your machine; docker containers are not required for local development and testing. To start the server at `localhost:3000`, simply run the following command: ```bash ./gitness server .local.env ``` ### Auto-Generate Harness API Client used by UI using Swagger Please make sure to update the autogenerated client code used by the UI when adding new rest APIs. To regenerate the code, please execute the following steps: - Regenerate swagger with latest Harness binary `./gitness swagger > web/src/services/code/swagger.yaml` - navigate to the `web` folder and run `yarn services` The latest API changes should now be reflected in `web/src/services/code/index.tsx` # Run Registry Conformance Tests ``` make conformance-test ``` For running conformance tests with existing running service, use: ``` make hot-conformance-test ``` ## User Interface This project includes a full user interface for interacting with the system. When you run the application, you can access the user interface by navigating to `http://localhost:3000` in your browser. ## REST API This project includes a swagger specification. When you run the application, you can access the swagger specification by navigating to `http://localhost:3000/swagger` in your browser (for raw yaml see `http://localhost:3000/openapi.yaml`). For registry endpoints, currently swagger is located on different endpoint `http://localhost:3000/registry/swagger/` (for raw json see `http://localhost:3000/registry/swagger.json`). These will be later moved to the main swagger endpoint. For testing, it's simplest to just use the cli to create a token (this requires Harness server to run): ```bash # LOGIN (user: admin, pw: changeit) $ ./gitness login # GENERATE PAT (1 YEAR VALIDITY) $ ./gitness user pat "my-pat-uid" 2592000 ``` The command outputs a valid PAT that has been granted full access as the user. The token can then be send as part of the `Authorization` header with Postman or curl: ```bash $ curl http://localhost:3000/api/v1/user \ -H "Authorization: Bearer $TOKEN" ``` ## CLI This project includes VERY basic command line tools for development and running the service. Please remember that you must start the server before you can execute commands. For a full list of supported operations, please see ```bash $ ./gitness --help ``` ## Contributing Refer to [CONTRIBUTING.md](https://github.com/harness/harness/blob/main/CONTRIBUTING.md) ## License Apache License 2.0, see [LICENSE](https://github.com/harness/harness/blob/main/LICENSE). ", Assign "at most 3 tags" to the expected json: {"id":"2204","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"