Skip to content

[Feature]: Cosmovisor: Configurable Data directory path instead of hard-coded one  #20947

Open

Description

Summary

The current $DAEMON_HOME location is dependent on the data directory and must be set to the same directory as the application data directory, it would be helpful to let the user decouple these two by setting an optional config for the data directory path

Problem Definition

Users are forced to place cosmovisor inside the application home directory (e.g., $HOME/.simapp), so it can detect upgrade-info.json and perform backups from the data directory.

One case where this can add complexity to the setup is using Cosmovisor inside Docker images. In Docker setups, it is trivial to mount the whole application home directory (e.g., $HOME/.simapp) to a persistent Docker volume, but cosmovisor should be outside of this volume so its underlying binaries can get updated by pulling new image versions.

Proposed Feature

Add an optional configuration like daemon_data_dir to allow users to specify an absolute path to the application data directory, such as /home/bob/.simapp/data. If left empty, it will default to the current behavior, which is $DAEMON_HOME/data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Type

No type

Projects

  • Status

    📋 Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions