Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make rsshell configurable #31

Open
jgonggrijp opened this issue Apr 8, 2013 · 1 comment
Open

make rsshell configurable #31

jgonggrijp opened this issue Apr 8, 2013 · 1 comment

Comments

@jgonggrijp
Copy link
Member

I would like rsshell to be highly configurable, so the user could pick

  • which underlying shell to use,
  • initial working directory,
  • optimization levels (e.g. PYTHONOPTIMIZE),
  • the location of RED_SPIDER_ROOT (which should include all subdirectories versioned by Git),
  • independently, the installer-created directories (bin, build, lib, work),

and possibly other things. The options should be accessible through commandline arguments, but should be retrieved from a configuration file when not specified. It should also be possible to specify the configuration file itself with a commandline argument so that multiple configurations can be stored in parallel. If no argument is given, rsshell should pick the configuration file that is pointed to by an environment variable (say RED_SPIDER_CONFIG) which is permanently stored in the user's environment (HKEY_CURRENT_USER on Windows, ~/.profile on unixy systems). The latter could replace the permanent storing of RED_SPIDER_ROOT. The initial configuration file should be created by setup.py, which might benefit from the parser proposed in issue #32.

Doing all of the above would allow users to, for example,

  • have two local copies of the project which check out different branches, and have the same copy of rshell switch between them;
  • customize the default working directory and temporarily switch to another default working directory;
  • install the red spider commands in one place and install them with different build settings in another place, and allow rsshell to work with either installation.

My preferred layout for the configuration file would be JSON.

@jgonggrijp
Copy link
Member Author

Removed the "low priority" from the title because of the issue referenced above.

Configuring the teleportation directory should be done first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant