- <code>data/ipbans.php</code> - banned IP addresses
- <code>data/updates.txt</code> - contains all automatic update to the configuration and datastore files already run</p>
<p>See <ahref="../Shaarli configuration">Shaarli configuration</a> for more information about Shaarli resources.</p>
<p>It is recommended to backup this repository <em>before</em> starting updating/upgrading Shaarli:
- users with SSH access: copy or archive the directory to a temporary location
- users with FTP access: download a local copy of your Shaarli installation using your favourite client</p>
<h3id="migrating-data-from-a-previous-installation">Migrating data from a previous installation</h3>
<p>As all user data is kept under <code>data</code>, this is the only directory you need to worry about when migrating to a new installation, which corresponds to the following steps:</p>
<ul>
<li>backup the <code>data</code> directory</li>
<li>install or update Shaarli:<ul>
<li>fresh installation - see <ahref="../Download and installation">Download and installation</a></li>
<li>update - see the following sections</li>
</ul>
</li>
<li>check or restore the <code>data</code> directory</li>
</ul>
<h2id="recommended-upgrading-from-release-archives">Recommended : Upgrading from release archives</h2>
<p>All tagged revisions can be downloaded as tarballs or ZIP archives from the <ahref="https://github.com/shaarli/Shaarli/releases">releases</a> page.</p>
<p>We recommend that you use the latest release tarball with the <code>-full</code> suffix. It contains the dependencies, please read <ahref="../Download and installation">Download and installation</a> for <code>git</code> complete instructions.</p>
<p>Once downloaded, extract the archive locally and update your remote installation (e.g. via FTP) -be sure you keep the content of the <code>data</code> directory!</p>
<p>After upgrading, access your fresh Shaarli installation from a web browser; the configuration and data store will then be automatically updated, and new settings added to <code>data/config.json.php</code> (see <ahref="../Shaarli configuration">Shaarli configuration</a> for more details).</p>
<h2id="upgrading-with-git">Upgrading with Git</h2>
<h3id="updating-a-community-shaarli">Updating a community Shaarli</h3>
<p>If you have installed Shaarli from the <ahref="../Download#clone-with-git-recommended">community Git repository</a>, simply <ahref="https://www.git-scm.com/docs/git-pull">pull new changes</a> from your local clone:</p>
<pre><codeclass="bash">$ cd /path/to/shaarli
$ git pull
From github.com:shaarli/Shaarli
* branch master -> FETCH_HEAD
Updating ebd67c6..521f0e6
Fast-forward
application/Url.php | 1 +
shaarli_version.php | 2 +-
tests/Url/UrlTest.php | 1 +
3 files changed, 3 insertions(+), 1 deletion(-)
</code></pre>
<p>Shaarli >= <code>v0.8.x</code>: install/update third-party PHP dependencies using <ahref="https://getcomposer.org/">Composer</a>:</p>
<h3id="migrating-and-upgrading-from-sebsauvages-repository">Migrating and upgrading from Sebsauvage's repository</h3>
<p>If you have installed Shaarli from <ahref="https://github.com/sebsauvage/Shaarli">Sebsauvage's original Git repository</a>, you can use <ahref="https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes">Git remotes</a> to update your working copy.</p>
<p>The following guide assumes that:
- you have a basic knowledge of Git <ahref="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell">branching</a> and <ahref="https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes">remote repositories</a>
- the default remote is named <code>origin</code> and points to Sebsauvage's repository
- the current branch is <code>master</code>
- if you have personal branches containing customizations, you will need to <ahref="https://git-scm.com/book/en/v2/Git-Branching-Rebasing">rebase them</a> after the upgrade; beware though, a lot of changes have been made since the community fork has been created, so things are very likely to break!
- the working copy is clean:
- no versioned file has been locally modified
- no untracked files are present</p>
<h4id="step-0-show-repository-information">Step 0: show repository information</h4>
<p>After migrating, access your fresh Shaarli installation from a web browser; the configuration will then be automatically updated, and new settings added to <code>data/config.php</code> (see <ahref="../Shaarli configuration">Shaarli configuration</a> for more details).</p>
<h2id="troubleshooting">Troubleshooting</h2>
<p>If the solutions provided here doesn't work, please open an issue specifying which version you're upgrading from and to.</p>
<h3id="you-must-specify-an-integer-as-a-key">You must specify an integer as a key</h3>
<p>In <code>v0.8.1</code> we changed how link keys are handled (from timestamps to incremental integers).
Take a look at <code>data/updates.txt</code> content.</p>
<ahref="../Download-and-Installation/"class="btn btn-neutral"title="Download and Installation"><spanclass="icon icon-circle-arrow-left"></span> Previous</a>
</div>
<hr/>
<divrole="contentinfo">
<!-- Copyright etc -->
</div>
Built with <ahref="http://www.mkdocs.org">MkDocs</a> using a <ahref="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <ahref="https://readthedocs.org">Read the Docs</a>.
