jasonlyle88

View on GitHub

Projects

This user doesn't have any project on FeatHub yet.

Features suggested

Project Feature Score Description
Flexget/Flexget Allow the "label" for deluge to be set via jinja token 2 Name says it all. Right now, instead of replacing the jinja token, the label just gets set to the jinja token name with a leading and trailing underscore. For full details, see https://github.com/Flexget/Flexget/issues/1513#event-1048486571
Flexget/Flexget config.yml location as a known field 2 It would be nice to have the (absolute) location of the flexget config file as a known field. In my case, I have some utility scripts that I run with the exec command on accepted filesystem files. Instead of having to hardcode the path to the utility in the config.yml file, it would be nice if I could use {{flexgetConfigLocation}} or {{flexgetConfigFileLocation|pathdir}} or something of the sort. I realize this can be accomplished by a) hard coding the value wherever it is used, b) using set to set the value then referencing it later, or c) using the variables plugin and putting it in a variables file. But this all essentially ends up as a hard coded value.
Flexget/Flexget New FlexGet-level CLI argument to specify database locations 1 As of writing this, the FlexGet-level CLI arguments currently support providing a config location through the use of the -c argument and a logfile location through the use of the -l/--logfile argument. I would like to suggest the addition of another argument (-d/--dbdir) that specifies the location to create the db-config.sqlite and the db-config-jobs.sqlite files. Right now, they are always created in the same directory as the config. The reason for this request is two fold: the logical separation and the practical application. As for logical separation, it make sense that if you are giving options to specify the config file and the log file, why not also include a database file argument? The configs are different from databases, so it doesn't make sense to always force users to group those together. As for the practical application: I believe there are several FlexGet users that keep their config files in some sort of external file storage option (git, dropbox, google drive, etc). While git can make use of .gitignore, it does not push and pull changes automatically. Services that push and pull automatically don't have this ignore functionality. Because of that, every time a scheduled job gets run, the external file storage gets updated because the database files get updated. If you have tasks that run often (I have a task that checks the status of something every minute), your end up inundated with updates in your external file storage system. It would be extremely nice to be able to separate the database files out from the configuration files and in this case not have store these files in the external file storage system. Thanks for the consideration!

Comments

This user hasn't voted yet.

Votes

Vote When Project Feature
3 months ago Flexget/Flexget New FlexGet-level CLI argument to specify database locations
over 2 years ago Flexget/Flexget config.yml location as a known field
over 2 years ago Flexget/Flexget Please allow the option to specify directory / file modes for the move plugin (and others)
about 3 years ago Flexget/Flexget Allow the "label" for deluge to be set via jinja token