Advanced Args
--profile
You can combine this with '--config'.
This option holds precedence over the currently active profile within the configuration file
--users-first
This adjustment alters the download order to prioritize fetching links for all selected users initially. While this may lead to a longer wait for downloads to commence, it can prove beneficial in specific scenarios.
multiple configs
The program attempts to intelligently guess the location of your config folder.
You can observe the locations it's scanning in the table. The checks will cease upon reaching a successful match (True) or reaching the failback check.
| Check | config file if True | config folder if True |
|---|---|---|
--config is not passed | $HOME/.config/ofscraper/config.json | $HOME/.config/ofscraper/ |
config_arg is an existing file | config_arg | config_arg parentdir |
config arg is an existing dir | config_arg/config.json | config_arg |
config arg has no extension | config_arg/config.json | config_arg |
config_arg ends is just a single file i.e test.json | $HOME/.config/ofscraper/config_arg | $HOME/.config/ofscraper |
Failback always true Note: The only option is for config_arg to be something like /home/me/test.json | config_arg | config_arg parentdir |
Shared information
Two configs within the same folder can share
Profiles
log files
cache
authorization
Duplication check
This relies on your configuration settings. If two configurations share identical metadata settings, duplicates won't exist between those configurations.
multiple profile auth
Authentication for various accounts is managed via profiles. You can modify the default profile either through the configuration or by using the '--profile' argument.
Example
The profile is consistently located within the parent folder of the configuration file and is always appended with '_profile'.
Hence, in this scenario, the profile would be
--no-cache
Disables all caching mechanisms and removes retrieval of past data for all data
As a result, synchronous processing is enforced for APIs to ensure each request is completed before the next one begins, since processing multiple API requests concurrently relies on past data This will also disable the use of cache to speed up decryption key retrieval
-no-api-cache
Similar to --no-cache, but only disables caching mechanisms and removes retrieval of past data for API use only
As a result, synchronous processing is enforced for APIs to ensure each request is completed before the next one begins, since processing multiple API requests concurrently relies on past data.
Last updated