first_steps.rst 3.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. .. _first-steps:
  2. First Steps on pagure
  3. =====================
  4. When coming to pagure for the first time there are a few things one should
  5. do or check to ensure all works as desired.
  6. Login to pagure or create your account
  7. --------------------------------------
  8. Pagure has its own user account system.
  9. For instances of pagure such as the one at `pagure.io <https://pagure.io>`_
  10. where the authentication is delegated to a third party (in the case of
  11. pagure.io, the Fedora Account System) via OpenID, the local user account
  12. is created upon login.
  13. This means, you cannot be added to a group or a project before you login for
  14. the first time as the system will simply not know you.
  15. If you run your own pagure instance which uses the local authentication
  16. system, then you will find on the login page an option to create a new
  17. account.
  18. .. _upload-your-ssh-key:
  19. Upload your SSH key
  20. -------------------
  21. Pagure uses gitolite to manage who has read/write access to which git
  22. repository via `ssh <https://en.wikipedia.org/wiki/Secure_Shell>`_.
  23. An ssh key is composed of two parts:
  24. * a private key, which you must keep to yourself and never share with anyone.
  25. * a public key, which is public and therefore can be shared with anyone.
  26. If you have never generated a ssh key, you can do so by running:
  27. ::
  28. ssh-keygen
  29. or alternatively on GNOME using the application ``seahorse``.
  30. This will create two files in ``~/.ssh/`` (``~`` is the symbol for your home
  31. folder).
  32. These two files will be named (for example) ``id_rsa`` and ``id_rsa.pub``.
  33. The first one is the private key that must never be shared. The second is
  34. the public key that can be uploaded on pagure to give you ssh access.
  35. To upload your public key onto pagure:
  36. 1. Login into pagure and click on the user icon on
  37. the top right corner, there, select ``My settings``.
  38. .. image:: _static/pagure_my_settings.png
  39. :target: ../_images/pagure_my_settings.png
  40. 2. In the authentication section of your user settings copy the content of your
  41. ``id_rsa.pub`` file in the Public SSH key text box and save your ssh key settings.
  42. .. image:: _static/pagure_add_ssh_key.png
  43. :target: ../_images/pagure_add_ssh_key.png
  44. .. note:: Pagure supports multiple ssh keys per user. To add more than one ssh key
  45. to your user account just add your new ssh key in your authentication
  46. settings (one key per row), this way you will be able to push commits
  47. to your repository from a different computer.
  48. Configure the default email address
  49. -----------------------------------
  50. If the pagure instance you use is using local user authentication, you can
  51. choose whichever email address you prefer to use during account creation.
  52. But in the case (like pagure.io) where the pagure instance relies
  53. on an external authentication service, the email address provided by this
  54. service may be different from the one you prefer.
  55. The settings page of your account (see above for how to access the page)
  56. allows you to add multiple email addresses and set one as default.
  57. Your default email address is the address that will be used to send you
  58. notifications and also as the email address in the git commit if you merge
  59. a pull-request with a merge commit.
  60. For online editing, when doing the commit, you will be presented with the
  61. list of valid email addresses associated with your account and you will be
  62. able to choose which one you wish to use.
  63. .. note:: All email addresses will need to be confirmed to be activated, this
  64. is done via a link sent by email to the address. If you do not
  65. receive this link, don't forget to check your spam folder!