Simple email application for Android. Original source code: https://framagit.org/dystopia-project/simple-email
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

85 lines
2.7 KiB

  1. npm-adduser(1) -- Add a registry user account
  2. =============================================
  3. ## SYNOPSIS
  4. npm adduser [--registry=url] [--scope=@orgname] [--always-auth] [--auth-type=legacy]
  5. aliases: login, add-user
  6. ## DESCRIPTION
  7. Create or verify a user named `<username>` in the specified registry, and
  8. save the credentials to the `.npmrc` file. If no registry is specified,
  9. the default registry will be used (see `npm-config(7)`).
  10. The username, password, and email are read in from prompts.
  11. To reset your password, go to <https://www.npmjs.com/forgot>
  12. To change your email address, go to <https://www.npmjs.com/email-edit>
  13. You may use this command multiple times with the same user account to
  14. authorize on a new machine. When authenticating on a new machine,
  15. the username, password and email address must all match with
  16. your existing record.
  17. `npm login` is an alias to `adduser` and behaves exactly the same way.
  18. ## CONFIGURATION
  19. ### registry
  20. Default: https://registry.npmjs.org/
  21. The base URL of the npm package registry. If `scope` is also specified,
  22. this registry will only be used for packages with that scope. `scope` defaults
  23. to the scope of the project directory you're currently in, if any. See `npm-scope(7)`.
  24. ### scope
  25. Default: none
  26. If specified, the user and login credentials given will be associated
  27. with the specified scope. See `npm-scope(7)`. You can use both at the same time,
  28. e.g.
  29. npm adduser --registry=http://myregistry.example.com --scope=@myco
  30. This will set a registry for the given scope and login or create a user for
  31. that registry at the same time.
  32. ### always-auth
  33. Default: false
  34. If specified, save configuration indicating that all requests to the given
  35. registry should include authorization information. Useful for private
  36. registries. Can be used with `--registry` and / or `--scope`, e.g.
  37. npm adduser --registry=http://private-registry.example.com --always-auth
  38. This will ensure that all requests to that registry (including for tarballs)
  39. include an authorization header. This setting may be necessary for use with
  40. private registries where metadata and package tarballs are stored on hosts with
  41. different hostnames. See `always-auth` in `npm-config(7)` for more details on
  42. always-auth. Registry-specific configuration of `always-auth` takes precedence
  43. over any global configuration.
  44. ### auth-type
  45. * Default: `'legacy'`
  46. * Type: `'legacy'`, `'sso'`, `'saml'`, `'oauth'`
  47. What authentication strategy to use with `adduser`/`login`. Some npm registries
  48. (for example, npmE) might support alternative auth strategies besides classic
  49. username/password entry in legacy npm.
  50. ## SEE ALSO
  51. * npm-registry(7)
  52. * npm-config(1)
  53. * npm-config(7)
  54. * npmrc(5)
  55. * npm-owner(1)
  56. * npm-whoami(1)