docs(README): added some more milestones and fixed docker-compose

Signed-off-by: kjuulh <contact@kjuulh.io>

README.md

@@ -1,24 +1,31 @@
 # Contractor - A renovate bot for gitea and github
 
-Contractor is a chatops like bot, integrating with github/gitea issues, allowing commands to trigger renovate runs.
+Contractor is a chatops like bot, integrating with github/gitea issues, allowing
+commands to trigger renovate runs.
 
 ```bash
 /contractor refresh
 ```
 
-Contractor runs in a regular docker image and uses the official renovate slim image behind the scenes, this can be changed in the configuration.
+Contractor runs in a regular docker image and uses the official renovate slim
+image behind the scenes, this can be changed in the configuration.
 
 ![command](./assets/command.png)
-<small>Do note that the contractor was run under a personal user, hence the same user replied</small>
+<small>Do note that the contractor was run under a personal user, hence the same
+user replied</small>
 
 ## DISCLAIMER
 
-The project is still 0.x.x As such the api is subject to change, and the examples will probably be out of date. The below should be seen as an example of what the project will look like once feature-complete.
+The project is still 0.x.x As such the api is subject to change, and the
+examples will probably be out of date. The below should be seen as an example of
+what the project will look like once feature-complete.
 
 ## Milestones
 
 - [x] 0.1.0
-  - Includes basic setup such as working server bot, and installation command, automation is missing however. Also only gitea support for now, because this is where the project initially is supposed to be in use.
+  - Includes basic setup such as working server bot, and installation command,
+    automation is missing however. Also only gitea support for now, because this
+    is where the project initially is supposed to be in use.
 - [ ] 0.2.0
   - Add GitHub support
 - [ ] 0.3.0
@@ -27,12 +34,16 @@ The project is still 0.x.x As such the api is subject to change, and the example
   - Slack integration
 - [ ] 0.5.0
   - GitHub App and such support
+- [ ] 0.6.0
+  - Add api key support
 
 ## Getting started
 
-First you need to pull and run the contractor image, docker is the preferred way of execution, but golang is also available from source.
+First you need to pull and run the contractor image, docker is the preferred way
+of execution, but golang is also available from source.
 
-Docker compose is given as an example, but you're free to run using `docker run` if you prefer.
+Docker compose is given as an example, but you're free to run using `docker run`
+if you prefer.
 
 See example for a ready-to-run image
 
@@ -41,18 +52,17 @@ See example for a ready-to-run image
 version: "3"
 services:
   contractor:
-	  image: docker.io/kjuulh/contractor:latest
+  image: docker.io/kjuulh/contractor:latest
-		restart: unless-stopped
+  restart: unless-stopped
-		commands:
+  commands:
-		- contractor server serve
+  - contractor server serve
-		volumes:
+  volumes:
-	  - "./templates/contractor:/mnt/config"
+  - "./templates/contractor:/mnt/config"
-		- "/var/run/docker.sock:/var/run/docker.sock"
+  - "/var/run/docker.sock:/var/run/docker.sock"
-		env_file:
+  env_file:
-	  - .env
+  - .env
 ```
 
-
 ```bash
 # file: .env
 GITEA_RENOVATE_TOKEN=<gitea application token> # needs repo and pull request permissions
@@ -74,15 +84,19 @@ CONTRACTOR_API_KEY='<some sufficiently secret password used for webhooks to auth
 // Remember to fill out the options as you see fit, this is not a complete example
 ```
 
-Use renovate secret for each `{{ secrets.HARBOR_SERVER_PASSWORD }}` in your config, replace `HARBOR_SERVER_PASSWORD` with your own
+Use renovate secret for each `{{ secrets.HARBOR_SERVER_PASSWORD }}` in your
+config, replace `HARBOR_SERVER_PASSWORD` with your own
 
 And then run the server with: `docker compose up`
 
-This has started the server, but github doesn't know that it needs to talk to you yet.
+This has started the server, but github doesn't know that it needs to talk to
+you yet.
 
-As such host the server somewhere with a public hostname, such that github or gitea webhooks can reach it, i.e. contractor.some-domain.com:9111
+As such host the server somewhere with a public hostname, such that github or
+gitea webhooks can reach it, i.e. contractor.some-domain.com:9111
 
-To install the webhook, either use the docker image, or download the cli from source.
+To install the webhook, either use the docker image, or download the cli from
+source.
 
 ### CLI
 
@@ -92,10 +106,15 @@ To install the cli
 go install git.front.kjuulh.io/kjuulh/contractor@latest
 ```
 
-contractor will automatically read any .env file, so you can leave out the secrets.
+contractor will automatically read any .env file, so you can leave out the
+secrets.
 
 ```bash
-contractor install --owner kjuulh --repository contractor --url https://git.front.kjuulh.io/api/v1 --backend gitea	
+contractor install  \
+--owner kjuulh \
+--repository contractor \
+--url https://git.front.kjuulh.io/api/v1 \
+--backend gitea
 ```
 
 If you leave any of these out, contractor will prompt your for required values.
@@ -105,9 +124,15 @@ If you leave any of these out, contractor will prompt your for required values.
 You can also use docker for it.
 
 ```bash
-docker compose run contractor install --owner kjuulh --repository contractor --url https://git.front.kjuulh.io/api/v1 --backend gitea	
+docker compose run contractor \
+install \
+--owner kjuulh \
+--repository contractor \
+--url https://git.front.kjuulh.io/api/v1 \
+--backend gitea
 ```
 
 ### GitHub App
 
-TBD, this should automatically install the webhook for allowed repositories, I just haven't gotten around to it yet. It is on the 0.3.0 Roadmap.
+TBD, this should automatically install the webhook for allowed repositories, I
+just haven't gotten around to it yet. It is on the 0.3.0 Roadmap.