StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<h2>There are three ways to do this: use the .hgrc file, use ssh or use the keyring extension</h2> <p><br></p> <h2>1. The INSECURE way - update your ~/.hgrc file </h2> <p>The format that works for me (in my ~/.hgrc file) is this</p> <pre><code>[ui] username=Chris McCauley <chris.mccauley@mydomain.com> [auth] repo.prefix = https://server/repo_path repo.username = username repo.password = password </code></pre> <p><br> You can configure as many repos as you want by adding more triplets of prefix,username, password by prepending a unique tag. <p> This only works in Mercurial 1.3 and obviously your username and password are in plain text - not good.</p> <p><br></p> <h2>2. The secure way - Use SSH to AVOID using passwords</h2> <p>Mercurial fully supports SSH so we can <i>take advantage of SSH's ability to log into a server without a password</i> - you do a once off configuration to provide a self-generated certificate. This is by far the safest way to do what you want. <p> <br> You can find more information on configuring <a href="http://www.debian-administration.org/articles/152" rel="noreferrer">passwordless login here</a></p> <p><br></p> <h2>3. The keyring Extension</h2> <p>If you want a secure option, but aren't familiar with SSH, why not try this? </p> <p>From the docs ...</p> <blockquote> <p>The extension prompts for the HTTP password on the first pull/push to/from given remote repository (just like it is done by default), but saves the password (keyed by the combination of username and remote repository url) in the password database. On the next run it checks for the username in .hg/hgrc, then for suitable password in the password database, and uses those credentials if found.</p> </blockquote> <p>There is more detailed information <a href="https://www.mercurial-scm.org/wiki/KeyringExtension" rel="noreferrer">here</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload