Page MenuHomePhabricator

Split ~/.arcrc between machine and user config
Closed, ResolvedPublic

Description

My setup

As a full-time software developer, I try to keep my setups as much in sync and versioned as possible. To that end, I keep a dotfiles.git repository (see GitHub ❤ ~/ for the many examples of devs keeping things tidy too).

This is were I can host, but also share, my custom setup files: .vimrc, .zshrc, .gitconfig, etc.
When I setup a new machine, I checkout my dotfiles.git repo, make some symlinks and off with it.
I can also try new things, break things, etc. knowing that git has my back and I can revert.

My issue with Arcanist

Arcanist stores its config (like aliases, etc.) in ~/.arcrc. It also stores credentials there. Which means that it is not suitable for backup and versioning by a dotfiles.git.
So my problem is that mixing of local/machine/secret specific data (credentials) and user/sharable configuration data.

Event Timeline

Arcank raised the priority of this task from to Needs Triage.
Arcank updated the task description. (Show Details)
Arcank changed the edit policy from "All Users" to "Custom Policy".
Arcank added a project: Feature Request.
Arcank added a subscriber: Arcank.

Do you have a meaningful amount of configuration in your ~/.arcrc?

chad added a project: Arcanist.
chad added a subscriber: chad.

I have two aliases that I wish I didn't have to have re-typed today between two of my machines.
I particularly like to be able to set up a new machine without thinking of what I might have missed on the old one.

epriestley triaged this task as Wishlist priority.Dec 9 2015, 12:09 AM

As a workaround, you might be able to put aliases in /etc/arcconfig (e.g., symlink that to something which is version controlled) and use ~/.arcconfig for credentials only.

This request is not entirely unreasonable, but the very low complexity of most ~/.arcrc files makes it very difficult to prioritize. It would almost certainly take many, many years for users to save enough time copy/pasting aliases to equal the time we'd spend implementing it. We are unlikely to pursue this unless making other changes to the ~/.arcrc format, which we have no current plans to do.

Actually, what is the difference between ~/.arcconfig and ~/.arcrc?

epriestley claimed this task.

After T10431, aliases are also read from system configuration.