feat!: token support for cloning

Readme.md

@@ -20,11 +20,12 @@ Other methods are not supporting:
   Which is acceptable for full account mirroring.
 
 **Security notice.**
-This application uses SSH as git transport layer.
-It is safe enough with right use,
-and for right use you need to save
-git server ssh digest (~/.ssh/known_hosts file).
-To do this you just need to clone any repository over ssh first
+This application can use SSH or HTTP(S) as git transport layer.
+With SSH, you need to save git server ssh digest
+(~/.ssh/known_hosts file). To do this you just need to clone any
+repository over ssh first.
+With HTTP(S), credentials are passed to git through environment-based
+configuration and are not written into repository remote URLs.
 
 **Config**. We use single config for this application.
 It is slightly ancient solution for modern Docker/Kubernetes backends,
@@ -32,6 +33,8 @@ but provides configuration in one place and _secure enough_ place to save token.
 
 
 Example config is available in [config.example.toml](config.example.toml).
+Use `main.api_token` for Gitea API access. Use `fetch.ssh_key` for SSH
+cloning, or `fetch.user` and `fetch.token` for HTTP(S) cloning.
 
 
 ### Native