Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Use a separate configuration directory for beta and dev releases to avoid contaminating user settings

See original GitHub issue

Can the *.beta releases be updated to use a different assortment of dot files, so .spyder could become .spyder-beta, this would preserve the beta alongside the current 3.3.1 release so that a production and testing environment can co-exist happily. I also wonder whether the same could be possible for the .ipython and .matplotlib subdirs?

Issue Analytics

State:
Created 5 years ago
Comments:22 (15 by maintainers)

Top GitHub Comments

1reaction

CAM-Gerlachcommented, Jan 4, 2019

Heh, its already wiped all my custom keyboard shortcuts and color schemes which is what I deserve for not implementing this sooner, I guess.

1reaction

ccordoba12commented, Aug 16, 2018

but with regard to the version string, should dev builds (checkouts from master) also count as beta for settings isolation

That would be really helpful for the dev team and I haven’t thought about that! So please also make dev as well as beta to count for settings isolation.

Top Results From Across the Web

Maintain Separate Configs for Dev, Beta and Release Build ...

First, we can maintain a different set of config files for each branch – enabling us to use different API keys or service...

Adding a build configuration file to your project

Specify your project's build settings in plain-text files, and supply different settings for debug and release builds.

Track CircleCI Updates

Track our platform changes and updates via the CircleCI Changelog. Stay up to date with the latest in Continuous Integration.

How do you keep user.config settings across different ...

ApplicationSettingsBase has a method called Upgrade which migrates all settings from the previous version.

Nixpkgs 22.11 manual - NixOS

Their configurations are managed separately. A user's nixpkgs configuration is stored in a user-specific configuration file located at ~/.config/nixpkgs/config.