[Request] Look for config file in other set directories #761

New Issue

Closed

opened 2026-01-29 16:21:51 +00:00 by claunia · 0 comments

claunia commented 2026-01-29 16:21:51 +00:00

Owner

Copy Link

Originally created by @Whovian9369 on GitHub (Nov 29, 2024).

Originally assigned to: @mnadareski on GitHub.

Is your feature request related to a problem? Please describe.
Look for config.json in directories other than the current working directory to make packaging for other environments more feasible.

For example, NixOS (or other systems that just use Nix as a package manager) has the application and pre-requisite files in a read-only directory/mount point, so unsuccessfully writing to config files in read-only directories can cause runtime issues or frustrations with the config file not being writable or available in the first place. Having that file available for MPF.Check in other directories, such as $HOME/.config/mpf/config.json, would help remedy that issue.

Describe the solution you'd like
config.json to be found in other directories, such as $HOME/.config/mpf/config.json, to make it easier for users where the main binary is in a read-only directory.

Describe alternatives you've considered
Hardcoding a config file into the built system presents a security issue where having a saved login could be viewed by all users of the system.

Additional context
N/A

Originally created by @Whovian9369 on GitHub (Nov 29, 2024). Originally assigned to: @mnadareski on GitHub. **Is your feature request related to a problem? Please describe.** Look for `config.json` in directories other than the current working directory to make packaging for other environments more feasible. For example, NixOS (or other systems that just use Nix as a package manager) has the application and pre-requisite files in a read-only directory/mount point, so unsuccessfully writing to config files in read-only directories can cause runtime issues or frustrations with the config file not being writable or available in the first place. Having that file available for `MPF.Check` in other directories, such as `$HOME/.config/mpf/config.json`, would help remedy that issue. **Describe the solution you'd like** `config.json` to be found in other directories, such as `$HOME/.config/mpf/config.json`, to make it easier for users where the main binary is in a read-only directory. **Describe alternatives you've considered** Hardcoding a config file into the built system presents a security issue where having a saved login could be viewed by all users of the system. **Additional context** N/A

claunia added the enhancement label 2026-01-29 16:21:51 +00:00

claunia closed this issue 2026-01-29 16:21:51 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

rolling

3.6.0

3.5.0

3.4.2

3.4.1

3.4.0

3.3.3

3.3.2

3.3.1

3.3.0

3.2.4

3.2.3

3.2.2

3.2.1

3.2.0

3.1.9

3.1.8

3.1.7

3.1.6

3.1.5

3.1.4

3.1.3

3.1.2

check-rolling

ui-rolling

3.1.1

3.1.0

3.0.3

3.0.2

3.0.1

3.0.0

2.7.5

2.7.4

2.7.3

2.7.2

2.7.1

2.7.0

2.6.6

2.6.5

2.6.4

2.6.3

2.6.2

2.6.1

2.6

2.5

2.4

2.3

2.2

2.1

2.0

1.18

1.17.1

1.17

1.16.1

1.16

1.15

1.14

1.13

1.12.2

1.12.1

1.12

1.11

1.10

1.07

1.06

1.05.1

1.05

1.04b

1.04a

1.04

1.03

1.02b

1.02

1.01d

1.01c

1.01b

Labels

Clear labels

bug

duplicate

enhancement

good first issue

help wanted

invalid

pull-request

Mirrored from GitHub Pull Request

question

regression

wontfix

No Label enhancement

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

claunia

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#761