docs: WIP directions on redirecting to local ficsit-cli build

Author: budak7273

DEPLOYMENT.md

@@ -9,7 +9,7 @@ Since the build action is triggered on every push to any branch,
 non developers can obtain testing builds easily from [GitHub Actions](https://github.com/satisfactorymodding/SatisfactoryModManager/actions/workflows/push.yml) artifact output.
 You need to be signed into GitHub to download them, and they expire after some time.
 
-TODO how to point dev builds to ficsit.dev (staging) instead?
+To point development builds to ficsit.dev instead of production, see the [Readme's configuration section](./README.md#Configuration).
 
 ## Releases
 

README.md

@@ -51,6 +51,10 @@ If you want to point to the SMR staging API instead of production, edit:
 * `main.go` to set `api-base` to the staging api (`https://api.ficsit.dev`)
 * `frontend\.graphqlrc.yml` to set `schema` to the staging api (`https://api.ficsit.dev/v2/query`)
 
+If you want to use a local build of [ficsit-cli](https://github.com/satisfactorymodding/ficsit-cli), TODO probably this replace command?
+<https://go.dev/wiki/Modules#when-should-i-use-the-replace-directive>
+ex. `go mod edit -replace github.com/satisfactorymodding/ficsit-cli=C:\Git\ficsit-cli` and do not commit the change
+
 ### Development Server
 
 The development server will hot reload whenever you make changes to the Go or Typescript code.