A version control software that comes with a restricted shell designed to prevent unauthorized access to critical parts of the system. It secures the version control system by limiting access to specific commands and functionalities, making it a reliable tool for collaborative work among teams.
RunVCS is a remarkable software tool that enables users to run version controlling programs and restricts them to access predetermined repositories. It comes with a host of valuable features, including the ability to modify the passed username. Currently, the software only supports SVN, but the developers have plans to support other version controlling programs in the future.
To install RunVCS, users can follow two simple steps. The first is to run the "make" command, followed by "make install." The software is customizable to users' preferences through the following environment variables:
- PREFIX: an installation prefix (by default, /usr/local)
- ETCDIR: a global configuration directory (by default, $(PREFIX)/etc)
- BINDIR: a program installation directory (by default, $(PREFIX)/bin)
- MANDIR: a man page installation directory (by default, $(PREFIX)/share/man)
Using RunVCS is relatively easy. Users can create individual accounts for developers and configure repositories on the global configuration file. Alternatively, they can set up a communal account and provide each developer with a public and private keypair. In such a case, they can use the command option in ~/.ssh/authorized_keys to run RunVCS with the -u and -s/-c options. However, this method restricts the use of more than one VCS.
To install RunVCS, users can follow two simple steps. The first is to run the "make" command, followed by "make install." The software is customizable to users' preferences through the following environment variables:
- PREFIX: an installation prefix (by default, /usr/local)
- ETCDIR: a global configuration directory (by default, $(PREFIX)/etc)
- BINDIR: a program installation directory (by default, $(PREFIX)/bin)
- MANDIR: a man page installation directory (by default, $(PREFIX)/share/man)
Using RunVCS is relatively easy. Users can create individual accounts for developers and configure repositories on the global configuration file. Alternatively, they can set up a communal account and provide each developer with a public and private keypair. In such a case, they can use the command option in ~/.ssh/authorized_keys to run RunVCS with the -u and -s/-c options. However, this method restricts the use of more than one VCS.
What's New
Version 0.2: N/A