If you wish to have integrations working correctly via SSH please configure
Set base_url for instance to enable proper event handling (Optional): Disabling this still allows users # to add their own keys.
#TORTOISEHG WEB SERVER EXECUTABLE GENERATOR#
ssh.enable_debug_logging = false # Paths to binary executable, by default they are the names, but we can # override them if we want to use a custom one = ~/.rccontrol/vcsserver-1/profile/bin/hg = ~/.rccontrol/vcsserver-1/profile/bin/git = ~/.rccontrol/vcsserver-1/profile/bin/svnserve # Enables SSH key generator web interface. Useful for debugging, shouldn't be used in production. # e.g ~/.rccontrol/community-1/profile/bin/rc-ssh-wrapper ssh.wrapper_cmd = ~/.rccontrol/community-1/rc-ssh-wrapper # Allow shell when executing the ssh-wrapper command ssh.wrapper_cmd_allow_shell = false # Enables logging, and detailed output send back to the client during SSH # operations. The binary is available in the # rhodecode installation directory. # AuthorizedKeysFile %h/.ssh/authorized_keys %h/.ssh/authorized_keys_rhodecode ssh.authorized_keys_file_path = ~/.ssh/authorized_keys_rhodecode # Command to execute the SSH wrapper. # It is possible to have multiple key files specified in `sshd_config` e.g. ssh.generate_authorized_keyfile = true # Options for ssh, default is `no-pty,no-port-forwarding,no-X11-forwarding,no-agent-forwarding` # ssh.authorized_keys_ssh_opts = # Path to the authrozied_keys file where the generate entries are placed. Super admins can still # manage SSH Keys. Setting this to false also disables posibility # of adding SSH keys by users from web interface. # SSH Support Settings # Defines if a custom authorized_keys file should be created and written on # any change user ssh keys.
0 kommentar(er)
