Deployed 4390324 to develop in en with MkDocs 1.6.1 and mike 2.1.3

This commit is contained in:
github-actions[bot]
2025-08-25 05:06:28 +00:00
parent adb7b2f5af
commit 7d3ca49be7
5 changed files with 65 additions and 63 deletions

View File

@@ -3695,8 +3695,8 @@ refer to <a href="../stoploss/">the stoploss documentation</a>.</p>
<p>If stoploss on exchange creation fails for some reason, then an "emergency exit" is initiated. By default, this will exit the trade using a market order. The order-type for the emergency-exit can be changed by setting the <code>emergency_exit</code> value in the <code>order_types</code> dictionary - however, this is not advised.</p>
</div>
<h3 id="understand-order_time_in_force">Understand order_time_in_force<a class="headerlink" href="#understand-order_time_in_force" title="Permanent link">&para;</a></h3>
<p>The <code>order_time_in_force</code> configuration parameter defines the policy by which the order
is executed on the exchange. Three commonly used time in force are:</p>
<p>The <code>order_time_in_force</code> configuration parameter defines the policy by which the order is executed on the exchange.<br />
Commonly used time in force are:</p>
<p><strong>GTC (Good Till Canceled):</strong></p>
<p>This is most of the time the default time in force. It means the order will remain
on exchange till it is cancelled by the user. It can be fully or partially fulfilled.
@@ -3709,10 +3709,11 @@ is automatically cancelled by the exchange.</p>
<p><strong>PO (Post only):</strong></p>
<p>Post only order. The order is either placed as a maker order, or it is canceled.
This means the order must be placed on orderbook for at least time in an unfilled state.</p>
<p>Please check the <a href="../exchanges/">Exchange documentation</a> for supported time in force values for your exchange.</p>
<h4 id="time_in_force-config">time_in_force config<a class="headerlink" href="#time_in_force-config" title="Permanent link">&para;</a></h4>
<p>The <code>order_time_in_force</code> parameter contains a dict with entry and exit time in force policy values.
This can be set in the configuration file or in the strategy.
Values set in the configuration file overwrites values set in the strategy.</p>
Values set in the configuration file overwrite values from in the strategy, following the regular <a href="#configuration-option-prevalence">precedence rules</a>.</p>
<p>The possible values are: <code>GTC</code> (default), <code>FOK</code> or <code>IOC</code>.</p>
<div class="highlight"><pre><span></span><code><span class="s2">&quot;order_time_in_force&quot;</span><span class="p">:</span> <span class="p">{</span>
<span class="s2">&quot;entry&quot;</span><span class="p">:</span> <span class="s2">&quot;GTC&quot;</span><span class="p">,</span>
@@ -3721,8 +3722,7 @@ Values set in the configuration file overwrites values set in the strategy.</p>
</code></pre></div>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>This is ongoing work. For now, it is supported only for binance, gate and kucoin.
Please don't change the default value unless you know what you are doing and have researched the impact of using different values for your particular exchange.</p>
<p>Please don't change the default value unless you know what you are doing and have researched the impact of using different values for your particular exchange.</p>
</div>
<h3 id="fiat-conversion">Fiat conversion<a class="headerlink" href="#fiat-conversion" title="Permanent link">&para;</a></h3>
<p>Freqtrade uses the Coingecko API to convert the coin value to it's corresponding fiat value for the Telegram reports.

View File

@@ -2427,7 +2427,7 @@ So, in order to mitigate Kraken API "Rate limit exceeded" exception, this config
<span class="w"> </span><span class="c1">// ...</span>
<span class="p">}</span>
</code></pre></div>
<p>Kucoin supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a>.</p>
<p>Kucoin supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a> with settings "GTC" (good till cancelled), "FOK" (full-or-cancel) and "IOC" (immediate-or-cancel) settings.</p>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Kucoin supports <code>stoploss_on_exchange</code> and can use both stop-loss-market and stop-loss-limit orders. It provides great advantages, so we recommend to benefit from it.
@@ -2466,8 +2466,9 @@ OKX also only provides MARK candles for the past ~3 months. Backtesting futures
<h2 id="gateio">Gate.io<a class="headerlink" href="#gateio" title="Permanent link">&para;</a></h2>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Gate.io supports <code>stoploss_on_exchange</code> and uses <code>stop-loss-limit</code> orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange..</p>
<p>Gate.io supports <code>stoploss_on_exchange</code> and uses <code>stop-loss-limit</code> orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.</p>
</div>
<p>Gate.io supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a> with settings "GTC" (good till cancelled), and "IOC" (immediate-or-cancel) settings.</p>
<p>Gate.io allows the use of <code>POINT</code> to pay for fees. As this is not a tradable currency (no regular market available), automatic fee calculations will fail (and default to a fee of 0).
The configuration parameter <code>exchange.unknown_fee_rate</code> can be used to specify the exchange rate between Point and the stake currency. Obviously, changing the stake-currency will also require changes to this value.</p>
<p>Gate API keys require the following permissions on top of the market type you want to trade:</p>
@@ -2478,8 +2479,14 @@ The configuration parameter <code>exchange.unknown_fee_rate</code> can be used t
</ul>
<p>Without these permissions, the bot will not start correctly and show errors like "permission missing".</p>
<h2 id="bybit">Bybit<a class="headerlink" href="#bybit" title="Permanent link">&para;</a></h2>
<p>Futures trading on bybit is currently supported for USDT markets, and will use isolated futures mode.</p>
<p>On startup, freqtrade will set the position mode to "One-way Mode" for the whole (sub)account. This avoids making this call over and over again (slowing down bot operations), but means that changes to this setting may result in exceptions and errors.</p>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Bybit (futures only) supports <code>stoploss_on_exchange</code> and uses <code>stop-loss-limit</code> orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.
On futures, Bybit supports both <code>stop-limit</code> as well as <code>stop-market</code> orders. You can use either <code>"limit"</code> or <code>"market"</code> in the <code>order_types.stoploss</code> configuration setting to decide which type to use.</p>
</div>
<p>Bybit supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a> with settings "GTC" (good till cancelled), "FOK" (full-or-cancel), "IOC" (immediate-or-cancel) and "PO" (Post only) settings.</p>
<p>Futures trading on bybit is currently supported for isolated futures mode.</p>
<p>On startup, freqtrade will set the position mode to "One-way Mode" for the whole (sub)account. This avoids making this call over and over again (slowing down bot operations), but means that manual changes to this setting may result in exceptions and errors.</p>
<p>As bybit doesn't provide funding rate history, the dry-run calculation is used for live trades as well.</p>
<p>API Keys for live futures trading must have the following permissions:</p>
<ul>
@@ -2494,11 +2501,6 @@ The configuration parameter <code>exchange.unknown_fee_rate</code> can be used t
We therefore recommend the usage of one subaccount per bot. This is especially important when using unified accounts.<br />
Other configurations (multiple bots on one account, manual non-bot trades on the bot account) are not supported and may lead to unexpected behavior.</p>
</div>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Bybit (futures only) supports <code>stoploss_on_exchange</code> and uses <code>stop-loss-limit</code> orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.
On futures, Bybit supports both <code>stop-limit</code> as well as <code>stop-market</code> orders. You can use either <code>"limit"</code> or <code>"market"</code> in the <code>order_types.stoploss</code> configuration setting to decide which type to use.</p>
</div>
<h2 id="bitmart">Bitmart<a class="headerlink" href="#bitmart" title="Permanent link">&para;</a></h2>
<p>Bitmart requires the API key Memo (the name you give the API key) to go along with the exchange key and secret.
It's therefore required to pass the UID as well.</p>
@@ -2524,7 +2526,7 @@ It's therefore required to pass the UID as well.</p>
<span class="w"> </span><span class="c1">// ...</span>
<span class="p">}</span>
</code></pre></div>
<p>Bitget supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a>.</p>
<p>Bitget supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a> with settings "GTC" (good till cancelled), "FOK" (full-or-cancel), "IOC" (immediate-or-cancel) and "PO" (Post only) settings.</p>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Bitget supports <code>stoploss_on_exchange</code> and can use both stop-loss-market and stop-loss-limit orders. It provides great advantages, so we recommend to benefit from it.

File diff suppressed because one or more lines are too long

View File

@@ -2,190 +2,190 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://www.freqtrade.io/en/stable/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/advanced-backtesting/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/advanced-hyperopt/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/advanced-orderflow/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/advanced-setup/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/backtesting/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/bot-basics/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/bot-usage/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/configuration/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/data-analysis/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/data-download/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/deprecated/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/developer/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/docker_quickstart/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/exchanges/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/faq/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/freq-ui/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/freqai-configuration/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/freqai-developers/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/freqai-feature-engineering/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/freqai-parameter-table/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/freqai-reinforcement-learning/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/freqai-running/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/freqai/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/hyperopt/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/installation/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/leverage/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/lookahead-analysis/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/plotting/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/plugins/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/producer-consumer/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/recursive-analysis/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/rest-api/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/sql_cheatsheet/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/stoploss/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/strategy-101/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/strategy-advanced/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/strategy-callbacks/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/strategy-customization/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/strategy_analysis_example/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/strategy_migration/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/telegram-usage/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/trade-object/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/updating/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/utils/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/webhook-config/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
<url>
<loc>https://www.freqtrade.io/en/stable/windows_installation/</loc>
<lastmod>2025-08-24</lastmod>
<lastmod>2025-08-25</lastmod>
</url>
</urlset>

Binary file not shown.