##// END OF EJS Templates
system-info: unified data structures for usage in API....
system-info: unified data structures for usage in API. - most datastructures now use dicts, and consisten return value for human and regular values - added detection of high load average - improved inodes/archive/gist storage limits - fixed problems with references of setting value as human_value and data overrides - re-did search info (more useful for 2 backends that we use)

File last commit:

r1:854a839a default
r1112:ff9a513b default
Show More
gist-editing.rst
33 lines | 1.3 KiB | text/x-rst | RstLexer

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`

Gist Management