Opened 12 years ago

Last modified 7 years ago

#2028 new feature-request

Don't save state information in configuration files

Reported by: daenney Owned by:
Priority: minor Milestone: 2.x
Component: Core Version: master
Keywords: Cc:


I've recently taken up the habit of storing configuration files in git, for better or for worse in case my server explodes I still have my configuration backed-up.

However, Deluge saves state-information in certain .conf files. For example, blocklist.conf contains information on when the blocklist was last updated and how many entries it contains.

Web.conf for some reason actually stores the current sessions and labels.conf stores torrent hashes with their label association.

Though this information is useful it makes it impossible to version Deluge configuration files as every so often git will see the file as changed without it containing actual configuration changes, only state changes.

I'd like to propose to split off this state information into state/file.conf and keep the actual configuration files in .conf/deluge as static as possible.

I'm willing to work on a patch for this myself as long as one of the developers thinks this makes sense so I don't do work that will never get merged.

Change History (2)

comment:1 Changed 10 years ago by Cas

  • Milestone changed from Future to 2.0.x

I think this is a good idea and does tie in with #2234

comment:2 Changed 7 years ago by Cas

  • Milestone changed from 2.0.x to 2.x

Milestone renamed

Note: See TracTickets for help on using tickets.