This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
) is private.
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon () is public.
Every repository with this icon (
) is public.
Command-Line Flags
None of these flags should ever be visible to the application that uses Dyre, so you shouldn’t bother explicitly filtering them out.
External Flags
--force-reconf- This flag does exactly what it says, forcing the custom binary to be recompiled even if Dyre thinks that it’s unnecessary. This is the only flag that an end-user could ever need to use. Consequently, it is the only one not prefixed with
--dyre.
- This flag does exactly what it says, forcing the custom binary to be recompiled even if Dyre thinks that it’s unnecessary. This is the only flag that an end-user could ever need to use. Consequently, it is the only one not prefixed with
--dyre-debug- Dyre will launch in debug mode. This means that the ordinary paths will be ignored, in favor of looking for a configuration in the current directory and storing cache files in the
./cachedirectory.
- Dyre will launch in debug mode. This means that the ordinary paths will be ignored, in favor of looking for a configuration in the current directory and storing cache files in the
Internal Flags
--dyre-master-binary- Used to relay the path to the master binary. Used to support program-initiated restarts.
--dyre-state-persist- Used to relay the path to the state file. Used to restore state after program restarts.
