first_steps.rst 3.5 KB

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