Skip to content

Commit

Permalink
fix(docs): correct operational parameters and streamline server confi…
Browse files Browse the repository at this point in the history 
…guration instructions
  • Loading branch information
@fassko
fassko committed Dec 18, 2024
1 parent ce211ee commit e5103af
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 18 deletions.
4 changes: 2 additions & 2 deletions docs/fassets/6-operational-parameters.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -173,8 +173,8 @@ Agents are free to adjust these settings as they see fit.
| [**Minting CR**](/fassets/collateral#minting-cr) | | | |
|  •  **Agent vault** | 1.3 | 1.3 | 1.3 |
|  •  **Collateral pool** | 1.6 | 1.6 | 1.6 |
| [**Exit CR**](/fassets/collateral#exit-cr) | 1.5 | 1.5 | 1.5 |
| [**Top-up CR**](/fassets/collateral#top-up-cr) | 1.6 | 1.6 | 1.6 |
| [**Exit CR**](/fassets/collateral#exit-cr) | 1.6 | 1.6 | 1.6 |
| [**Top-up CR**](/fassets/collateral#top-up-cr) | 1.5 | 1.5 | 1.5 |
|  •  **Top-up discount** | 0.5% | 0.5% | 0.5% |
| [**Discount for agent self-close**](/fassets/liquidation#stopping-liquidations)<br />In a self-close exit, the pool token holder burns FAssets to increase pool CR enough to enable the exit. Usually, the burned FAssets are redeemed in the normal redemption process. However, if the closed amount is less than 1 lot, or on explicit request, the agent buys the underlying assets (at a discounted FTSO price, to compensate the agent for possible price fluctuations) and pays the exiting token holder in vault collateral.<br /> | 1% | 1% | 1% |
</TabItem>
Expand Down
18 changes: 2 additions & 16 deletions docs/fassets/guides/1-deploy-fassets-agent.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -186,22 +186,8 @@ You can obtain the `xrp_rpc` for the XRP Ledger, `btc_rpc` for Bitcoin, and `dog

## Configure the Server

To access the FAssets admin interface, you need to configure the server to route requests to the frontend and backend.

### Backend Configuration

Allow your server to access the URL `fasset-backend`:

1. Route requests from `/fasset-backend` to the backend service (default port `4000`).
2. Rewrite the path from `/fasset-backend/` to `/api/`.
3. Forward necessary headers to the backend for proper communication.

### Frontend Configuration

Route requests from the frontend to the backend service:

1. Route requests from `/` path to the frontend service running on the desired port (default port `3000`).
2. Forward the Host header to the frontend service for proper handling.
To access the FAssets admin interface, configure the server to route requests to both the frontend and backend.
Allow requests on the default port of `4000` for the backend and `3000` for the frontend.

:::warning

Expand Down

0 comments on commit e5103af

Please sign in to comment.