rhodecode-enterprise-ce Files · docs/contributing/dev-settings.rst

svn: Ignore the content length header from response, fixes ...

svn: Ignore the content length header from response, fixes In case of compressed responses from apache(mod_dav_svn) we can not use the Content-Length header in our own response. The content is automatically decompressed by the requests library and therefore the content length differs. This results in errors when doing e.g. a svn checkout: "svn: E120106: ra_serf: The server sent a truncated HTTP response body."

lisaq - - Load All Authors

File last commit:

r271:401985cc default


                r473:7e153d56

default

Download file

             dev-settings.rst
        
                    46 lines
            
             | 959 B
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / contributing / dev-settings.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      ==========================

       Settings for Development

      ==========================

      We have a few settings which are intended to be used only for development

      purposes. This section contains an overview of them.

      `debug_style`

      =============

      Enables the section "Style" in the application. This section provides an

        lisaq
    
docs: updates to contributor documentation #4039

              r271
            
      overview of all components which are found in the frontend of the

        marcink
    
project: added all source files and assets

              r1
            
      application.

      `vcs.start_server`

      ==================

      Starts the server as a subprocess while the system comes up. Intended usage is

      to ease development.

      `[logging]`

      ===========

        lisaq
    
docs: updates to contributor documentation #4039

              r271
            
      Use this to configure logging to your current needs. The documentation of

      Python's `logging` module explains all of the details. The following snippets

      are useful for day to day development work.

        marcink
    
project: added all source files and assets

              r1
            
      Mute SQL output

      ---------------

      They come out of the package `sqlalchemy.engine`::

        [logger_sqlalchemy]

        level = WARNING

        handlers = console_sql

        qualname = sqlalchemy.engine

        propagate = 0

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

marcink project: added all source files and assets	r1
		==========================
		Settings for Development
		==========================


		We have a few settings which are intended to be used only for development
		purposes. This section contains an overview of them.



		`debug_style`
		=============

		Enables the section "Style" in the application. This section provides an
lisaq docs: updates to contributor documentation #4039	r271	overview of all components which are found in the frontend of the
marcink project: added all source files and assets	r1	application.



		`vcs.start_server`
		==================

		Starts the server as a subprocess while the system comes up. Intended usage is
		to ease development.



		`[logging]`
		===========

lisaq docs: updates to contributor documentation #4039	r271	Use this to configure logging to your current needs. The documentation of
		Python's `logging` module explains all of the details. The following snippets
		are useful for day to day development work.
marcink project: added all source files and assets	r1

		Mute SQL output
		---------------

		They come out of the package `sqlalchemy.engine`::

		[logger_sqlalchemy]
		level = WARNING
		handlers = console_sql
		qualname = sqlalchemy.engine
		propagate = 0