Project

General

Profile

Feature #4451

Configuration support for readonly filesystems

Added by Mono Polimorph over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Configuration
Target version:
-
Start date:
2017-06-20
Due date:
% Done:

0%

Estimated time:

Description

Hi,

I like to run TVH in a Raspberry Pi with readonly filesystem.
After a lot of reading, for a long running is preferable to not write a lot in SD cards.

So I like to deploy my environment in this way:

- Use one Pi with root mounted readonly, and /tmp readwrite in RAM.
- TVH installed in the readonly filesystem.
- TVH "static" configuration in the readonly filesysten.
- TVH "dynamic" configuration in /tmp.

Will be possible to achieve this?
Thank you for your responses!

History

#1

Updated by Jaroslav Kysela over 7 years ago

The TVH's configuration directory (-c argument) must be R/W - all settings are stored there including the actual MPEG-TS stream parameters. You can use /tmp, but you should backup this directory on reboot and copy files back on boot (when tvheadend is not running to avoid inconsistencies).

#2

Updated by Mono Polimorph over 7 years ago

Jaroslav Kysela wrote:

The TVH's configuration directory (-c argument) must be R/W - all settings are stored there including the actual MPEG-TS stream parameters. You can use /tmp, but you should backup this directory on reboot and copy files back on boot (when tvheadend is not running to avoid inconsistencies).

Hi,

I know. For this reason I ask for a solution. For example I suggest different options:

1) Implement in TVH the function to "export" and "import" the current configuration. This exporting tool will copy all configuration in a single file (or package). Then is only required to add a command line parameter to "auto-import" the configuration. In this way is posible to "load" (=import) the configuration when starting TVH, and then use "-c /tmp/tvh/" for the running configuration. The only drawback is the efimeral configuration, as when restarting the /tmp/ can be deleted.

2) Add support for two configuration directories. One is "ro" and the other "rw". Any data in the "rw" overrides the value in the "ro".

What you think? In my opinion, the option for import/export the configuration will be very useful... and not only for this.

#3

Updated by kodiaq kodiaq over 7 years ago

+1 for import/export the configuration option - It would save time during migration and would make sleep of many people better when they backed up their configuration before going to bed :)

#4

Updated by Rafal Kupiec over 7 years ago

No need to do that as you can change config directory.
+1 for backup (export & import configuration).

There is also a ticket for channels import & export so would be nice to have it independently.

Also available in: Atom PDF