Chicken and egg problem with Tails about pyro HOT 5 CLOSED

Sorry, I should have mentioned that in the README. If you run ./setup.sh, that script will create a dummy colors file.

I'm thinking about a better way to deal with this in the future.

from pyro.

That did it! I can PR in an update to the readme, if you'd like?

from pyro.

Appreciate the offer, but I think my plan is to remove the requirement for a colors file and remove that feature from the Phlegethon theme so you can just run w/ the default colors. I'll change the instructions to reflect that, and it should also speed up the compilation. Will take me a little while because I have to refactor the themes to not rely on the brand and brand-fg colors.

from pyro.

Ok! Thanks for the answer, I'll close this then

from pyro.

No problem. Just pushed a major colors refactor and updated the get-started.md guide. You don't need the colors.json file or the Tails config anymore. If you remove it, you will need to force a tails recompile with mix deps.compile tails --force.

from pyro.