Verified Commit 8ff89a9d authored by Gael Yvert's avatar Gael Yvert
Browse files

add short ToC in upgrading doc

parent 6503b79b
...@@ -2,7 +2,11 @@ ...@@ -2,7 +2,11 @@
# Upgrading instructions # Upgrading instructions
## From v2.0.1 or later to latest-release [From v2.0.1 or later]("Fromv2.0.1orlater)
[From v1.0.0 to v2.0.1]("Fromv1.0.0tov2.0.1)
## From v2.0.1 or later to latest-release <a name="Fromv2.0.1orlater"></a>
All the steps below should be run at the root of your installation. Unless you installed your instance at a specific location, type: All the steps below should be run at the root of your installation. Unless you installed your instance at a specific location, type:
...@@ -126,11 +130,12 @@ You also need now to re-initialize the BLAST database of `dna_features`, so that ...@@ -126,11 +130,12 @@ You also need now to re-initialize the BLAST database of `dna_features`, so that
This step is only needed once. However, all your past entries of dnafeatures will appear black on your maps. To customize the colors you want, simply edit the `color` field of each dnafeature and then click on the button 'Update Plasmid Maps with these Features'. This step is only needed once. However, all your past entries of dnafeatures will appear black on your maps. To customize the colors you want, simply edit the `color` field of each dnafeature and then click on the button 'Update Plasmid Maps with these Features'.
## From v1.0.0 to v2.0.1 ## From v1.0.0 to v2.0.1 <a name="Fromv1.0.0tov2.0.1"></a>
Version v2 is **not** an upgrade of version v1 but was fully rewritten. Upgrading a v1 instance is therefore not straightfoward. However, it is totally do-able and we provide tools to help you achieve this process. Version v2 is **not** an upgrade of version v1 but was fully rewritten. Upgrading a v1 instance is therefore not straightfoward. However, it is totally do-able and we provide tools to help you achieve this process.
The first thing to do is to install a fresh instance of MyLabStocks that runs v2.0.1. Please see the steps above for the general guidelines. What is critical here in roder to have v2.0.1 installed is to change: The first thing to do is to install a fresh instance of MyLabStocks that runs v2.0.1. Please see the steps above for the general guidelines. What is critical here in order to have v2.0.1 installed is to change:
```sh ```sh
git clone https://gitbio.ens-lyon.fr/LBMC/gylab/mylabstocks.git git clone https://gitbio.ens-lyon.fr/LBMC/gylab/mylabstocks.git
git checkout latest-release git checkout latest-release
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment