Added a note re .pyw and Windows as suggested in #27
This commit is contained in:
parent
e40a5447ee
commit
871cfdeab6
1 changed files with 4 additions and 0 deletions
|
@ -18,6 +18,8 @@ FediFetcher will store posts it has already pulled in, as well as profiles it ha
|
|||
|
||||
**Be aware, that this script may run for a *very* long time.** This is particularly true, the first time this script runs, and/or if you enable all parts of this script. You should ensure that you take steps to prevent multiple overlapping executions of this script, as that will lead to unpleasant results.
|
||||
|
||||
For detailed information on the how and why, please read the [FediFetcher for Mastodon page](https://blog.thms.uk/fedifetcher?utm_source=github).
|
||||
|
||||
## Setup
|
||||
|
||||
You can run FediFetcher either as a GitHub Action, as a scheduled cron job on your local machine/server, or from a pre-packed container.
|
||||
|
@ -61,6 +63,8 @@ When using a cronjob, we are using file based locking to avoid multiple overlapp
|
|||
|
||||
If you are running FediFetcher locally, my recommendation is to run it manually once, before turning on the cron job: The first run will be significantly slower than subsequent runs, and that will help you prevent overlapping during that first run.
|
||||
|
||||
*Note:* if you wish to run FediFetcher using Windows Task Scheduler, you can rename the script to the `.pyw` extension instead of `.py`, and it will run silently, without opening a console window.
|
||||
|
||||
### 2.3) Run FediFetcher from a container
|
||||
|
||||
FediFetcher is also available in a pre-packaged container, [FediFetcher](https://github.com/nanos/FediFetcher/pkgs/container/fedifetcher) - Thank you [@nikdoof](https://github.com/nikdoof).
|
||||
|
|
Loading…
Reference in a new issue