Local settings folder for portable app

[ivysrono]

After we reinstall the system, or when we use Sabaki between several different computers, we want a file to record the settings modified by the user. The content of this file is equal to settings.json, but has higher permissions. LizGoban, Firefox and other open source projects provide this feature.

[yishn]

Why not just use settings.json?

[ivysrono]

First, it can be modified once and used everywhere;
Second, settings.json may be modified during major version updates, and a separate user configuration file can avoid version conflicts.

[yishn]

settings.json can also be used everywhere. If there's need to modify settings during an upgrade, this would also have to affect your custom settings file.

[ivysrono]

emm, settings.json is hard to store and sync. Could we custom it's path?

[yishn]

How does Firefox support changing the settings path?

[ivysrono]

User.js file - MozillaZine Knowledge Base
1.1 Overview · ghacksuserjs/ghacks-user.js Wiki

There are more disadvantages of direct sync settings.json:
For example, as #586 has not been resolved, users may need to customize the width and height, but their settings may not apply to another computer.

LizGoban support config.json to set engines, path, and so on.

I would like to put config.json into the same folder as sabaki-**-portable.exe, to get realy portable.

[yishn]

Maybe for the portable version, say path\to\sabaki-**-portable.exe, we will resolve the settings folder as path\to\sabaki-profile, and for non-portable, it stays at %APPDATA%\Sabaki.

[ivysrono]

IMO, it is ok.

[yishn]

Would you like to submit a PR? We set the setting folder path in setting.js, line 7.

[ivysrono]

I'll try the next few days.

[ivysrono]

Would you like to submit a PR? We set the setting folder path in setting.js, line 7.

Why sabaki always use sync function?
Could we use async?
Or node-fs-extra which is depended by electron?

[yishn]

Because we are not a server, we don’t need to serve multiple users at the same time, it’s not that critical to use async functions. Also, it simplifies control flow and removes the need to show a busy indicator in the UI.