CODESH (COllaborative DEvelopment SHell) is an automatic persistent logbook for sessions of personal command line work. It records what and how is being done, for private use/reuse and for sharing selected parts with collaborators. It is an intelligent shell that automatically logs user's shell sessions. Sessions are uniquely tagged and stored in local or distributed backend repositories (ASCII flat file or Subversion or CVS based) and can be extracted and reproduced at any time by the user who created the session or by collaborators located anywhere in the world.
|Tags||Communications File Sharing Scientific/Engineering Shells Utilities Information Management|
|Implementation||Python Unix Shell|
Release Notes: This release deprecates code like os.popen and string exceptions (brought to Python 2.6 standards). Corresponding warnings disappear.
Release Notes: This is the starting point for a new development cycle. The Web server hosting codesh has migrated to new hardware.
Release Notes: The test suite was streamlined to produce shorter and more focused output, making it easier to scan the results from each test. The code for the various backends was cleaned up. A problem when extracting flex sessions (the log-modify-and-replay mechanism of CODESH) from remote CVS backends was fixed.
Release Notes: The focus of this version is the distributed computing (remote) aspects of CODESH. A new subdirectory "remote" is introduced. It contains sample scripts showing how to set up remote (client/server based) Subversion, CVS, and ASCII backends, along with detailed documentation. The scripts can be used not only to set up CODESH backends, but general purpose remote Subversion or CVS pserver repositories as well. As usual, extreme caution and studying the documentation in advance is recommended before setting up servers.
Release Notes: This version improves the user experience by hardening the frontend and the Subversion, CVS, and ASCII backends. The checks on user input are extended, and now users are warned in basically all situations if they try to run commands with wrong number of parameters. The verifications if the backend repositories are up and running when the users try to access them are extended with dynamic checks, approaching complete coverage.