Handle XDG Directories

Handling files and directories correctly in a command-line or TUI application ensures that the application fits seamlessly into a user’s workflow and adheres to established conventions. One of the key conventions on Linux-based systems is the XDG Base Directory Specification.

Why the XDG Base Directory Specification?

The XDG Base Directory Specification is a set of standards that define where user files should reside, ensuring a cleaner home directory and a more organized storage convention. By adhering to this standard, your application will store files in the expected directories, making it more predictable and user-friendly.

Using directories-rs for Path Resolution

The directories-rs library offers a Rust-friendly interface to locate common directories (like config and data directories) based on established conventions, including the XDG Base Directory Specification.

  1. Add directories-rs to your Cargo.toml
cargo add directories

  1. Use the ProjectDirs struct to retrieve paths based on your project’s domain and project name and create helper functions for getting the data_dir and config_dir.

  2. Allow users to specify custom locations using environment variables. This flexibility can be crucial for users with unique directory structures or for testing.

  3. A good practice is to notify the user about the location of the configuration and data directories. An example from the template is to print out these locations when the user invokes the --version command-line argument. See the section on Command line argument parsing

Here’s an example get_data_dir() and get_config_dir() functions for your reference:

use std::path::PathBuf;

use anyhow::{anyhow, Context, Result};
use directories::ProjectDirs;

pub fn get_data_dir() -> Result<PathBuf> {
  let directory = if let Ok(s) = std::env::var("RATATUI_TEMPLATE_DATA") {
    PathBuf::from(s)
  } else if let Some(proj_dirs) = ProjectDirs::from("com", "kdheepak", "ratatui-template") {
    proj_dirs.data_local_dir().to_path_buf()
  } else {
    return Err(anyhow!("Unable to find data directory for ratatui-template"));
  };
  Ok(directory)
}

pub fn get_config_dir() -> Result<PathBuf> {
  let directory = if let Ok(s) = std::env::var("RATATUI_TEMPLATE_CONFIG") {
    PathBuf::from(s)
  } else if let Some(proj_dirs) = ProjectDirs::from("com", "kdheepak", "ratatui-template") {
    proj_dirs.config_local_dir().to_path_buf()
  } else {
    return Err(anyhow!("Unable to find config directory for ratatui-template"));
  };
  Ok(directory)
}

You will want to replace kdheepak with your user name or company name (or any unique name for that matter); and ratatui-app with the name of your CLI.

I own https://kdheepak.com so I tend to use com.kdheepak.ratatui-app for my project directories. That way it is unlikely that any other program will mess with the configuration files for the app I plan on distributing.