/usr/share/doc/monotone/html/Creating-a-Database.html is in monotone-doc 1.0-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 | <html lang="en">
<head>
<title>Creating a Database - monotone documentation</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="monotone documentation">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Tutorial.html#Tutorial" title="Tutorial">
<link rel="prev" href="Tutorial.html#Tutorial" title="Tutorial">
<link rel="next" href="Generating-Keys.html#Generating-Keys" title="Generating Keys">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
--></style>
<link rel="stylesheet" type="text/css" href="texinfo.css">
</head>
<body>
<div class="node">
<a name="Creating-a-Database"></a>
<p>
Next: <a rel="next" accesskey="n" href="Generating-Keys.html#Generating-Keys">Generating Keys</a>,
Previous: <a rel="previous" accesskey="p" href="Tutorial.html#Tutorial">Tutorial</a>,
Up: <a rel="up" accesskey="u" href="Tutorial.html#Tutorial">Tutorial</a>
<hr>
</div>
<h3 class="section">2.3 Creating a Database</h3>
<p>The first step Jim, Abe and Beth each need to perform is to create a
new database. This is done with the <samp><span class="command">mtn db init</span></samp> command,
providing a <samp><span class="option">--db</span></samp> option to specify the location of the new
database. Each programmer creates their own database, which will
reside in their home directory and store all the revisions, files and
manifests they work on.
<p>In real life, most people prefer to keep one database for each project
they work on. If we followed that convention here in the tutorial,
though, then all the databases would be called <code>juicebot.mtn</code>, and
that would make things more confusing to read. So instead, we'll have
them each name their database after themselves.
<p>Thus Jim issues the command:
<pre class="smallexample">$ mtn db init --db=~/jim.mtn
</pre>
<p>and Abe issues the command:
<pre class="smallexample">$ mtn db init --db=~/abe.mtn
</pre>
<p>Beth decides to use monotone's built-in database management
functionality. monotone then expects to find managed database files
in a list of directories (default <samp><span class="file">$HOME/.monotone/databases</span></samp> on
Unix and <samp><span class="file">%APPDATA%\monotone\databases</span></samp> on Windows, see
<a href="Managed-Databases.html#Managed-Databases">Managed Databases</a> for more info) and acts upon those by knowing
only their file or basename.
<p>To create a new managed database, Beth issues the <samp><span class="command">mtn db init</span></samp> command
like this:
<pre class="smallexample">$ mtn db init --db=:beth
</pre>
<p>Beth can distinguish a managed database name from an unmanaged one by
the leading colon in its name. This special alias can now be used
interchangeably in every monotone invocation. If Beth wants to see
where monotone actually created the database and what other databases
monotone knows of, she uses the <samp><span class="command"><a href="mtn-list-databases.html#mtn-list-databases">mtn list databases</a></span></samp> command
(or <samp><span class="command">mtn ls dbs</span></samp>) for that. We'll come back to this in a bit.
</body></html>
|