##// END OF EJS Templates
config: updated .ini files.
marcink -
r2125:36911930 default
parent child Browse files
Show More
@@ -73,7 +73,7 b' asyncore_use_poll = true'
73 73 ## The `instance_id = *` must be set in the [app:main] section below
74 74 #workers = 2
75 75 ## number of threads for each of the worker, must be set to 1 for gevent
76 ## generally recommened to be at 1
76 ## generally recommended to be at 1
77 77 #threads = 1
78 78 ## process name
79 79 #proc_name = rhodecode
@@ -601,15 +601,16 b' svn.proxy.location_root = /'
601 601 ### SSH Support Settings ###
602 602 ############################################################
603 603
604 ## Defines if the authorized_keys file should be written on any change of
605 ## user ssh keys, setting this to false also disables posibility of adding
606 ## ssh keys for users from web interface.
604 ## Defines if a custom authorized_keys file should be created and written on
605 ## any change user ssh keys. Setting this to false also disables posibility
606 ## of adding SSH keys by users from web interface. Super admins can still
607 ## manage SSH Keys.
607 608 ssh.generate_authorized_keyfile = false
608 609
609 610 ## Options for ssh, default is `no-pty,no-port-forwarding,no-X11-forwarding,no-agent-forwarding`
610 611 # ssh.authorized_keys_ssh_opts =
611 612
612 ## File to generate the authorized keys together with options
613 ## Path to the authrozied_keys file where the generate entries are placed.
613 614 ## It is possible to have multiple key files specified in `sshd_config` e.g.
614 615 ## AuthorizedKeysFile %h/.ssh/authorized_keys %h/.ssh/authorized_keys_rhodecode
615 616 ssh.authorized_keys_file_path = ~/.ssh/authorized_keys_rhodecode
@@ -622,9 +623,9 b' ssh.wrapper_cmd = ~/.rccontrol/community'
622 623 ## Allow shell when executing the ssh-wrapper command
623 624 ssh.wrapper_cmd_allow_shell = false
624 625
625 ## Enables logging, and detailed output send back to the client. Usefull for
626 ## debugging, shouldn't be used in production.
627 ssh.enable_debug_logging = false
626 ## Enables logging, and detailed output send back to the client during SSH
627 ## operations. Usefull for debugging, shouldn't be used in production.
628 ssh.enable_debug_logging = true
628 629
629 630 ## API KEY for user who has access to fetch other user permission information
630 631 ## most likely an super-admin account with some IP restrictions.
@@ -634,7 +635,7 b' ssh.api_key ='
634 635 ## access
635 636 ssh.api_host = http://localhost
636 637
637 ## Paths to binary executrables, by default they are the names, but we can
638 ## Paths to binary executable, by default they are the names, but we can
638 639 ## override them if we want to use a custom one
639 640 ssh.executable.hg = ~/.rccontrol/vcsserver-1/profile/bin/hg
640 641 ssh.executable.git = ~/.rccontrol/vcsserver-1/profile/bin/git
@@ -650,7 +651,7 b' custom.conf = 1'
650 651 ### LOGGING CONFIGURATION ####
651 652 ################################
652 653 [loggers]
653 keys = root, routes, rhodecode, sqlalchemy, beaker, templates, ssh_wrapper
654 keys = root, sqlalchemy, beaker, rhodecode, ssh_wrapper
654 655
655 656 [handlers]
656 657 keys = console, console_sql
@@ -665,12 +666,11 b' keys = generic, color_formatter, color_f'
665 666 level = NOTSET
666 667 handlers = console
667 668
668 [logger_routes]
669 level = DEBUG
670 handlers =
671 qualname = routes.middleware
672 ## "level = DEBUG" logs the route matched and routing variables.
673 propagate = 1
669 [logger_sqlalchemy]
670 level = INFO
671 handlers = console_sql
672 qualname = sqlalchemy.engine
673 propagate = 0
674 674
675 675 [logger_beaker]
676 676 level = DEBUG
@@ -678,24 +678,12 b' handlers ='
678 678 qualname = beaker.container
679 679 propagate = 1
680 680
681 [logger_templates]
682 level = INFO
683 handlers =
684 qualname = pylons.templating
685 propagate = 1
686
687 681 [logger_rhodecode]
688 682 level = DEBUG
689 683 handlers =
690 684 qualname = rhodecode
691 685 propagate = 1
692 686
693 [logger_sqlalchemy]
694 level = INFO
695 handlers = console_sql
696 qualname = sqlalchemy.engine
697 propagate = 0
698
699 687 [logger_ssh_wrapper]
700 688 level = DEBUG
701 689 handlers =
@@ -73,7 +73,7 b' use = egg:gunicorn#main'
73 73 ## The `instance_id = *` must be set in the [app:main] section below
74 74 workers = 2
75 75 ## number of threads for each of the worker, must be set to 1 for gevent
76 ## generally recommened to be at 1
76 ## generally recommended to be at 1
77 77 #threads = 1
78 78 ## process name
79 79 proc_name = rhodecode
@@ -570,15 +570,16 b' svn.proxy.location_root = /'
570 570 ### SSH Support Settings ###
571 571 ############################################################
572 572
573 ## Defines if the authorized_keys file should be written on any change of
574 ## user ssh keys, setting this to false also disables posibility of adding
575 ## ssh keys for users from web interface.
573 ## Defines if a custom authorized_keys file should be created and written on
574 ## any change user ssh keys. Setting this to false also disables posibility
575 ## of adding SSH keys by users from web interface. Super admins can still
576 ## manage SSH Keys.
576 577 ssh.generate_authorized_keyfile = false
577 578
578 579 ## Options for ssh, default is `no-pty,no-port-forwarding,no-X11-forwarding,no-agent-forwarding`
579 580 # ssh.authorized_keys_ssh_opts =
580 581
581 ## File to generate the authorized keys together with options
582 ## Path to the authrozied_keys file where the generate entries are placed.
582 583 ## It is possible to have multiple key files specified in `sshd_config` e.g.
583 584 ## AuthorizedKeysFile %h/.ssh/authorized_keys %h/.ssh/authorized_keys_rhodecode
584 585 ssh.authorized_keys_file_path = ~/.ssh/authorized_keys_rhodecode
@@ -591,8 +592,8 b' ssh.wrapper_cmd = ~/.rccontrol/community'
591 592 ## Allow shell when executing the ssh-wrapper command
592 593 ssh.wrapper_cmd_allow_shell = false
593 594
594 ## Enables logging, and detailed output send back to the client. Usefull for
595 ## debugging, shouldn't be used in production.
595 ## Enables logging, and detailed output send back to the client during SSH
596 ## operations. Usefull for debugging, shouldn't be used in production.
596 597 ssh.enable_debug_logging = false
597 598
598 599 ## API KEY for user who has access to fetch other user permission information
@@ -603,7 +604,7 b' ssh.api_key ='
603 604 ## access
604 605 ssh.api_host = http://localhost
605 606
606 ## Paths to binary executrables, by default they are the names, but we can
607 ## Paths to binary executable, by default they are the names, but we can
607 608 ## override them if we want to use a custom one
608 609 ssh.executable.hg = ~/.rccontrol/vcsserver-1/profile/bin/hg
609 610 ssh.executable.git = ~/.rccontrol/vcsserver-1/profile/bin/git
@@ -619,7 +620,7 b' custom.conf = 1'
619 620 ### LOGGING CONFIGURATION ####
620 621 ################################
621 622 [loggers]
622 keys = root, routes, rhodecode, sqlalchemy, beaker, templates, ssh_wrapper
623 keys = root, sqlalchemy, beaker, rhodecode, ssh_wrapper
623 624
624 625 [handlers]
625 626 keys = console, console_sql
@@ -634,12 +635,11 b' keys = generic, color_formatter, color_f'
634 635 level = NOTSET
635 636 handlers = console
636 637
637 [logger_routes]
638 level = DEBUG
639 handlers =
640 qualname = routes.middleware
641 ## "level = DEBUG" logs the route matched and routing variables.
642 propagate = 1
638 [logger_sqlalchemy]
639 level = INFO
640 handlers = console_sql
641 qualname = sqlalchemy.engine
642 propagate = 0
643 643
644 644 [logger_beaker]
645 645 level = DEBUG
@@ -647,24 +647,12 b' handlers ='
647 647 qualname = beaker.container
648 648 propagate = 1
649 649
650 [logger_templates]
651 level = INFO
652 handlers =
653 qualname = pylons.templating
654 propagate = 1
655
656 650 [logger_rhodecode]
657 651 level = DEBUG
658 652 handlers =
659 653 qualname = rhodecode
660 654 propagate = 1
661 655
662 [logger_sqlalchemy]
663 level = INFO
664 handlers = console_sql
665 qualname = sqlalchemy.engine
666 propagate = 0
667
668 656 [logger_ssh_wrapper]
669 657 level = DEBUG
670 658 handlers =
General Comments 0
You need to be logged in to leave comments. Login now