u/pc/rhodecode-enterprise-ce-fork-pc Files · docs/usage/gist-editing.rst

auth: don't break hashing in case of user with empty password....

auth: don't break hashing in case of user with empty password. In some cases such as LDAP user created via external scripts users might set the passwords to empty. The hashing uses the md5(password_hash) to store reference to detect password changes and forbid using the same password. In case of pure LDAP users this is not valid, and we shouldn't raise Errors in such case. This change makes it work for empty passwords now.

marcink - - Load All Authors

File last commit:

r1:854a839a default


                r2203:8a18c3c3

default

Download file

             gist-editing.rst
        
                    33 lines
            
             | 1.3 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / usage / gist-editing.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      .. _gist-edit:

      Gist Editing

      ^^^^^^^^^^^^

      Gists are standalone files that only the creator can edit. To work with

      gists, click on the :guilabel:`Gists` tab on the |RCM| header. The gist

      editor also has syntax highlighting.

      You can set the following properties for each gist:

      * :guilabel:`Public`: Public gists are as the name suggests,

        and will show up in searches.

      * :guilabel:`Gist Lifetime`: You can set a gist to expire after a set

        period by using the :guilabel:`Gist Lifetime` dropdown menu.

        This means that when the gist expires it will be deleted from the |RCM|

        gist database.

      * :guilabel:`Private`: This means that the gist will not show up in searches.

      * :guilabel:`Gist access level`: If you create a private gist you can have

        two levels of privacy with the gist link.

        * :guilabel:`Requires registered account`: This option requires users to

          have a registered account on the |RCE| instance, otherwise they will not

          have access to the gist.

        * :guilabel:`Can be accessed by anonymous users`: This option hides the

          link so that it does not show up in searches, but you can still share it

          with people outside of your organisation.

      For more advanced use of gists, see the gist API options in the :ref:`api`

      .. image:: ../images/gists-acl.png

         :alt: Gist Management

         :scale: 50 %

	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	.. _gist-edit:

		Gist Editing
		^^^^^^^^^^^^

		Gists are standalone files that only the creator can edit. To work with
		gists, click on the :guilabel:`Gists` tab on the \|RCM\| header. The gist
		editor also has syntax highlighting.

		You can set the following properties for each gist:

		* :guilabel:`Public`: Public gists are as the name suggests,
		and will show up in searches.
		* :guilabel:`Gist Lifetime`: You can set a gist to expire after a set
		period by using the :guilabel:`Gist Lifetime` dropdown menu.
		This means that when the gist expires it will be deleted from the \|RCM\|
		gist database.
		* :guilabel:`Private`: This means that the gist will not show up in searches.
		* :guilabel:`Gist access level`: If you create a private gist you can have
		two levels of privacy with the gist link.

		* :guilabel:`Requires registered account`: This option requires users to
		have a registered account on the \|RCE\| instance, otherwise they will not
		have access to the gist.
		* :guilabel:`Can be accessed by anonymous users`: This option hides the
		link so that it does not show up in searches, but you can still share it
		with people outside of your organisation.

		For more advanced use of gists, see the gist API options in the :ref:`api`

		.. image:: ../images/gists-acl.png
		:alt: Gist Management
		:scale: 50 %