Skip to content

Support Per-user config.ini #33

@kilves76

Description

@kilves76

I'm sorry I didn't actually try the software after reading the config where it seems it only supports a single config per machine.

What about multi user support where every account on the machine could have their own config? In order to support separate, differently named profiles that each user might have. It seems that currently it's only possible to launch a similarly named profile for all users, at most. This will work somewhat if every user's Default profile is a hardened profile for opening new links...and fails when it's not.

The easiest path might be by loading per-user configs saved in User\Appdata\Local\BrowseRouter , where entries with same browser names would override existing entries in main config, and maybe add some new ones too? For example when the user has installed Chrome Canary which only installs into the personal appdata folder. A default per-user config could be easily created by copying the relevant browser definition lines from the machine config at first run.

So in the end a user could define that they want to use
chrome = "C:\...chrome.exe" --profile-directory="Profile 4"
as the default.

In theory users could just create a profile named Hardened and set that as machine default but creating named profiles in (at least) Chrome based browsers seems to be a hit and miss affair -- sometimes a "Profile ##" profile will get renamed to "Newname" or "Profile ## Newname" when renamed inside the browser, and sometimes not. The logic in how that works eludes me, and might be different per Chrome based variant too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions