Config unavailable if ran as root

[aspauldingcode]

if running as root, config will not be available (obvious to unix config structure)

however, this means I need a root mode config (probably /etc/gowall/config.yml) for a custom theme
This is important for running the gowall command under nix, with postActivation scripts.

When I run a gowall list as root, the themes are not available. I try making /etc/gowall/config.yml, or /etc/gowall.yml, but no success. I am on macOS. What is my solution?

[0bCdian]

Hi! I'm not achno, but I'm helping him with some features. This is normal as when you are the root user, the $HOME environment variable changes to /root, so you'll have to manually create the file inside /root/.config/

try impersonating the root user and creating the file

sudo su
cd
touch .config/gowall/config.yml 
# do your edits 
vi .config/gowall/config.yml 

or just copy it from wherever you already have it, for example:

sudo su
cd
mkdir ./config/gowall
cp /home/yourNormalUser/.config/gowall/config.yml ./.config/gowall/

[aspauldingcode]

Hiii.

I have solved my issue.
I created a config json at /etc/gowall/theme.json by creating the following nix darwin config:

{
  config,
  lib,
  pkgs,
  ...
}:

let
  inherit (config.colorScheme) palette;
in
{
  environment.etc."gowall/theme.json" = {
    enable = true;
    text = ''
      {
        "name": "${config.colorscheme.slug}",
        "colors": [
          "#${palette.base00}",
          "#${palette.base01}",
          "#${palette.base02}",
          "#${palette.base03}",
          "#${palette.base04}",
          "#${palette.base05}",
          "#${palette.base06}",
          "#${palette.base07}",
          "#${palette.base08}",
          "#${palette.base09}",
          "#${palette.base0A}",
          "#${palette.base0B}",
          "#${palette.base0C}",
          "#${palette.base0D}",
          "#${palette.base0E}",
          "#${palette.base0F}"
        ]
      }
    '';
  };
}

Then, I can pass in a command using a ran-as-root nix postActivation Script by passing in the json file declaritively from /etc/gowall/theme.json

[aspauldingcode]

It's to be noted, we cannot impersonate a user with sudo su userName when using nix activation scripts.

[Achno]

Hey @aspauldingcode i'm happy you managed to figure out a workaround, i'm not really a Nix wizard myself so i couldn't provide you with a temporary solution right now.

If more people ask for it i can consider implementing reading the config files from /etc/...

[aspauldingcode]

Hey @aspauldingcode i'm happy you managed to figure out a workaround, i'm not really a Nix wizard myself so i couldn't provide you with a temporary solution right now.

If more people ask for it i can consider implementing reading the config files from /etc/...

That would be great!
Then, I could use my whole yml config there too.

Maybe at some point, a nix flake or home manager module could be created to manage gowall