Skip to content

Commit fe9de41

Browse files
committed
docs: fix Note boxes not rendering correctly
1 parent daff50e commit fe9de41

File tree

2 files changed

+9
-12
lines changed

2 files changed

+9
-12
lines changed

docs/advanced-setup.md

Lines changed: 8 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -315,28 +315,25 @@ $RepeatedMsgReduction on
315315
316316
The syslog address can be either a Unix domain socket (socket filename) or a UDP socket specification, consisting of IP address and UDP port, separated by the `:` character.
317317
318-
319318
So, the following are the examples of possible addresses:
320319
321320
* `"address": "/dev/log"` -- log to syslog (rsyslog) using the `/dev/log` socket, suitable for most systems.
322321
* `"address": "/var/run/syslog"` -- log to syslog (rsyslog) using the `/var/run/syslog` socket. Use this on MacOS.
323322
* `"address": "localhost:514"` -- log to local syslog using UDP socket, if it listens on port 514.
324323
* `"address": "<ip>:514"` -- log to remote syslog at IP address and port 514. This may be used on Windows for remote logging to an external syslog server.
325324
326-
327325
??? Info "Deprecated - configure syslog via command line"
326+
`--logfile syslog:<syslog_address>` -- send log messages to `syslog` service using the `<syslog_address>` as the syslog address.
328327
329-
`--logfile syslog:<syslog_address>` -- send log messages to `syslog` service using the `<syslog_address>` as the syslog address.
330-
331-
The syslog address can be either a Unix domain socket (socket filename) or a UDP socket specification, consisting of IP address and UDP port, separated by the `:` character.
328+
The syslog address can be either a Unix domain socket (socket filename) or a UDP socket specification, consisting of IP address and UDP port, separated by the `:` character.
332329
333-
So, the following are the examples of possible usages:
330+
So, the following are the examples of possible usages:
334331
335-
* `--logfile syslog:/dev/log` -- log to syslog (rsyslog) using the `/dev/log` socket, suitable for most systems.
336-
* `--logfile syslog` -- same as above, the shortcut for `/dev/log`.
337-
* `--logfile syslog:/var/run/syslog` -- log to syslog (rsyslog) using the `/var/run/syslog` socket. Use this on MacOS.
338-
* `--logfile syslog:localhost:514` -- log to local syslog using UDP socket, if it listens on port 514.
339-
* `--logfile syslog:<ip>:514` -- log to remote syslog at IP address and port 514. This may be used on Windows for remote logging to an external syslog server.
332+
* `--logfile syslog:/dev/log` -- log to syslog (rsyslog) using the `/dev/log` socket, suitable for most systems.
333+
* `--logfile syslog` -- same as above, the shortcut for `/dev/log`.
334+
* `--logfile syslog:/var/run/syslog` -- log to syslog (rsyslog) using the `/var/run/syslog` socket. Use this on MacOS.
335+
* `--logfile syslog:localhost:514` -- log to local syslog using UDP socket, if it listens on port 514.
336+
* `--logfile syslog:<ip>:514` -- log to remote syslog at IP address and port 514. This may be used on Windows for remote logging to an external syslog server.
340337
341338
### Logging to journald
342339

docs/freqai.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ pip install -r requirements-freqai.txt
7979
If you are using docker, a dedicated tag with FreqAI dependencies is available as `:freqai`. As such - you can replace the image line in your docker compose file with `image: freqtradeorg/freqtrade:stable_freqai`. This image contains the regular FreqAI dependencies. Similar to native installs, Catboost will not be available on ARM based devices. If you would like to use PyTorch or Reinforcement learning, you should use the torch or RL tags, `image: freqtradeorg/freqtrade:stable_freqaitorch`, `image: freqtradeorg/freqtrade:stable_freqairl`.
8080

8181
!!! note "docker-compose-freqai.yml"
82-
We do provide an explicit docker-compose file for this in `docker/docker-compose-freqai.yml` - which can be used via `docker compose -f docker/docker-compose-freqai.yml run ...` - or can be copied to replace the original docker file. This docker-compose file also contains a (disabled) section to enable GPU resources within docker containers. This obviously assumes the system has GPU resources available.
82+
We do provide an explicit docker-compose file for this in `docker/docker-compose-freqai.yml` - which can be used via `docker compose -f docker/docker-compose-freqai.yml run ...` - or can be copied to replace the original docker file. This docker-compose file also contains a (disabled) section to enable GPU resources within docker containers. This obviously assumes the system has GPU resources available.
8383

8484
### FreqAI position in open-source machine learning landscape
8585

0 commit comments

Comments
 (0)