mirror of
https://github.com/haiwen/seafile-admin-docs.git
synced 2025-12-26 02:32:50 +00:00
improve upgrade nodes
This commit is contained in:
parent
83e3690ab0
commit
e27ac02ecc
|
|
@ -253,7 +253,7 @@ The test should cover these steps at least:
|
|||
### <a id="wiki-test-upgrading"></a> Test upgrading from a previous version
|
||||
|
||||
* Download the package of the previous version seafile server, and setup it.
|
||||
* Upgrading according to [the manual](http://manual.seafile.com/deploy/upgrade/)
|
||||
* Upgrading according to [the manual](http://manual.seafile.com/upgrade/upgrade/)
|
||||
* After the upgrade, check the functionality is ok:
|
||||
* Uploading/Downloading files through a web browser works correctly.
|
||||
* Seafile [WebDAV](http://manual.seafile.com/extension/webdav/) server works correctly
|
||||
|
|
|
|||
|
|
@ -1071,7 +1071,7 @@ The configuration of Apache is as following:
|
|||
|
||||
## 6.1
|
||||
|
||||
You can follow the document on minor [upgrade](../deploy/upgrade.md).
|
||||
You can follow the document on minor [upgrade](../upgrade/upgrade.md).
|
||||
|
||||
### 6.1.9 (2017.09.28)
|
||||
|
||||
|
|
@ -1166,7 +1166,7 @@ System changes:
|
|||
|
||||
## 6.0
|
||||
|
||||
You can follow the document on minor [upgrade](../deploy/upgrade.md).
|
||||
You can follow the document on minor [upgrade](../upgrade/upgrade.md).
|
||||
|
||||
Special note for upgrading a cluster:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,165 +0,0 @@
|
|||
# Upgrade manual
|
||||
|
||||
This page is for users who use the pre-compiled seafile server package.
|
||||
- If you [build seafile server from source](../build_seafile/server.md), please read the **Upgrading Seafile Server** section on that page, instead of this one.
|
||||
- After upgrading, you may need to clean [seahub cache](add_memcached.md) if it doesn't behave as expect.
|
||||
- If you are running a **cluster**, please read [upgrade a Seafile cluster](../deploy_pro/upgrade_a_cluster.md).
|
||||
|
||||
## Upgrade notes
|
||||
Please check the [upgrade notes](upgrade_notes.md) for any special configuration or changes before/while upgrading.
|
||||
|
||||
---
|
||||
|
||||
## Major version upgrade (e.g. from 4.x.x to 5.y.y)
|
||||
|
||||
|
||||
Suppose you are using version 4.3.0 and like to upgrade to version 5.0.0. First download and extract the new version. You should have a directory layout similar to this:
|
||||
|
||||
```
|
||||
haiwen
|
||||
-- seafile-server-4.3.0
|
||||
-- seafile-server-5.0.0
|
||||
-- ccnet
|
||||
-- seafile-data
|
||||
```
|
||||
|
||||
|
||||
Now upgrade to version 5.0.0.
|
||||
|
||||
1. Shutdown Seafile server if it's running
|
||||
|
||||
```sh
|
||||
cd haiwen/seafile-server-4.3.0
|
||||
./seahub.sh stop
|
||||
./seafile.sh stop
|
||||
# or via service
|
||||
/etc/init.d/seafile-server stop
|
||||
```
|
||||
2. Check the upgrade scripts in seafile-server-5.0.0 directory.
|
||||
|
||||
```sh
|
||||
cd haiwen/seafile-server-5.0.0
|
||||
ls upgrade/upgrade_*
|
||||
```
|
||||
|
||||
You will get a list of upgrade files:
|
||||
|
||||
```
|
||||
...
|
||||
upgrade/upgrade_4.0_4.1.sh
|
||||
upgrade/upgrade_4.1_4.2.sh
|
||||
upgrade/upgrade_4.2_4.3.sh
|
||||
upgrade/upgrade_4.3_4.4.sh
|
||||
upgrade/upgrade_4.4_5.0.sh
|
||||
```
|
||||
|
||||
3. Start from your current version, run the script(s one by one)
|
||||
|
||||
```
|
||||
upgrade/upgrade_4.3_4.4.sh
|
||||
upgrade/upgrade_4.4_5.0.sh
|
||||
```
|
||||
|
||||
4. Start Seafile server
|
||||
|
||||
```sh
|
||||
cd haiwen/seafile-server-5.0.0/
|
||||
./seafile.sh start
|
||||
./seahub.sh start # or "./seahub.sh start-fastcgi" if you're using fastcgi
|
||||
# or via service
|
||||
/etc/init.d/seafile-server start
|
||||
```
|
||||
|
||||
5. If the new version works fine, the old version can be removed
|
||||
|
||||
```sh
|
||||
rm -rf seafile-server-4.3.0/
|
||||
```
|
||||
|
||||
## Minor version upgrade (e.g. from 5.0.x to 5.1.y)
|
||||
|
||||
Suppose you are using version 5.0.0 and like to upgrade to version 5.1.0. First download and extract the new version. You should have a directory layout similar to this:
|
||||
|
||||
```
|
||||
haiwen
|
||||
-- seafile-server-5.0.0
|
||||
-- seafile-server-5.1.0
|
||||
-- ccnet
|
||||
-- seafile-data
|
||||
```
|
||||
|
||||
|
||||
Now upgrade to version 5.1.0.
|
||||
|
||||
1. Shutdown Seafile server if it's running
|
||||
|
||||
```sh
|
||||
cd haiwen/seafile-server-5.0.0
|
||||
./seahub.sh stop
|
||||
./seafile.sh stop
|
||||
# or via service
|
||||
/etc/init.d/seafile-server stop
|
||||
```
|
||||
|
||||
2. Check the upgrade scripts in seafile-server-5.1.0 directory.
|
||||
|
||||
```sh
|
||||
cd haiwen/seafile-server-5.1.0
|
||||
ls upgrade/upgrade_*
|
||||
```
|
||||
|
||||
You will get a list of upgrade files:
|
||||
|
||||
```
|
||||
...
|
||||
upgrade/upgrade_4.0_4.1.sh
|
||||
upgrade/upgrade_4.1_4.2.sh
|
||||
upgrade/upgrade_4.2_4.3.sh
|
||||
upgrade/upgrade_4.3_4.4.sh
|
||||
upgrade/upgrade_4.4_5.0.sh
|
||||
upgrade/upgrade_5.0_5.1.sh
|
||||
```
|
||||
|
||||
3. Start from your current version, run the script(s one by one)
|
||||
|
||||
```
|
||||
upgrade/upgrade_5.0_5.1.sh
|
||||
```
|
||||
|
||||
4. Start Seafile server
|
||||
|
||||
```sh
|
||||
cd haiwen/seafile-server-5.1.0/
|
||||
./seafile.sh start
|
||||
./seahub.sh start # or "./seahub.sh start-fastcgi" if you're using fastcgi
|
||||
# or via service
|
||||
/etc/init.d/seafile-server start
|
||||
```
|
||||
|
||||
5. If the new version works, the old version can be removed
|
||||
|
||||
```sh
|
||||
rm -rf seafile-server-5.0.0/
|
||||
```
|
||||
|
||||
## Maintenance version upgrade (e.g. from 5.1.2 to 5.1.3)
|
||||
|
||||
A maintenance upgrade is for example an upgrade from 5.1.2 to 5.1.3.
|
||||
|
||||
1. Shutdown Seafile server if it's running
|
||||
|
||||
2. For this type of upgrade, you only need to update the symbolic links (for avatar and a few other folders).
|
||||
A script to perform a minor upgrade is provided with Seafile server (for history reasons, the script is called `minor-upgrade.sh`):
|
||||
|
||||
```sh
|
||||
cd seafile-server-5.1.3
|
||||
upgrade/minor-upgrade.sh
|
||||
```
|
||||
|
||||
3. Start Seafile
|
||||
|
||||
4. If the new version works, the old version can be removed
|
||||
|
||||
```sh
|
||||
rm -rf seafile-server-5.1.2/
|
||||
```
|
||||
|
|
@ -1,153 +0,0 @@
|
|||
# Upgrade notes
|
||||
|
||||
These notes give additional information about changes.
|
||||
Please always follow the [main upgrade guide](./upgrade.md).
|
||||
|
||||
## Summary
|
||||
|
||||
* [Upgrade notes for V6.x.x](#upgrade-notes-v6.x.x)
|
||||
* [Upgrade notes for V5.x.x](#upgrade-notes-v5.x.x)
|
||||
* [Upgrade notes for V4.x.x](#upgrade-notes-v4.x.x)
|
||||
|
||||
*This documentation is just done from V4 + !*
|
||||
|
||||
------
|
||||
|
||||
# Upgrade Notes V6.x.x
|
||||
|
||||
## Important release changes
|
||||
|
||||
From this version, the Wiki module is hidden by default. Users will not be able to turn it on. For compatibility with older versions, it can be turned on by adding the following line to `seahub_settings.py`:
|
||||
|
||||
```python
|
||||
ENABLE_WIKI = True
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## V6.1.0
|
||||
|
||||
### Video Thumbnails
|
||||
|
||||
Enable or disable thumbnail for video. ffmpeg and moviepy should be installed first.
|
||||
For details, please refer to the [manual](./video_thumbnails.md).
|
||||
|
||||
### OnlyOffice
|
||||
The system requires some minor changes to support the OnlyOffice document server.
|
||||
Please follow the instructions [here](./only_office.md).
|
||||
|
||||
### Pip Pillow upgrade
|
||||
|
||||
```
|
||||
# for Ubuntu 16.04
|
||||
sudo apt-get install libjpeg-dev
|
||||
pip install --upgrade Pillow
|
||||
# If the pillow installation fails you may install
|
||||
# "build-dep python-imaging" instead of just "libjpeg-dev"
|
||||
|
||||
# for Debian 8
|
||||
apt-get install libjpeg-dev
|
||||
pip install --upgrade Pillow
|
||||
|
||||
# If the pillow installation fails you may install
|
||||
# "build-dep python-imaging" instead of just "libjpeg-dev"
|
||||
|
||||
# for Centos 7
|
||||
sudo yum install libjpeg-dev
|
||||
pip install --upgrade Pillow
|
||||
```
|
||||
|
||||
### Seahub does not start
|
||||
|
||||
In case Seahub does not start after the upgrade, install python-requests.
|
||||
|
||||
```bash
|
||||
sudo apt-get install python-requests
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## V6.0.0 - V6.0.9
|
||||
|
||||
There are no other special instructions.
|
||||
|
||||
---
|
||||
|
||||
# Upgrade Notes V5.x.x
|
||||
|
||||
## Important release changes
|
||||
|
||||
__In Seafile 5.0, we moved all config files to the folder ```/seafile-root/conf```, including:__
|
||||
|
||||
- seahub_settings.py -> conf/seahub_settings.py
|
||||
- ccnet/ccnet.conf -> conf/ccnet.conf
|
||||
- seafile-data/seafile.conf -> conf/seafile.conf
|
||||
- [pro only] pro-data/seafevents.conf -> conf/seafevents.conf
|
||||
|
||||
------
|
||||
|
||||
## V5.1.4
|
||||
|
||||
**Python upgrade**
|
||||
If you upgrade to 5.1.4+, you need to install the python 3 libs:
|
||||
|
||||
```
|
||||
# for Ubuntu 16.04
|
||||
sudo apt-get install python-urllib3
|
||||
|
||||
# for Debian 8
|
||||
apt-get install python-urllib3
|
||||
|
||||
# for Centos 7
|
||||
sudo yum install python-urllib3
|
||||
|
||||
# for Arch Linux
|
||||
pacman -Sy python2-urllib3
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## V5.0.0 - V5.1.3
|
||||
|
||||
Nothing to be installed/changed.
|
||||
|
||||
------
|
||||
|
||||
# Upgrade Notes V4.x.x
|
||||
These notes just give additional information about changes within each major version.
|
||||
Please always follow the [main installation guide](./upgrade.md).
|
||||
|
||||
## Important release changes
|
||||
|
||||
- [Thumbnail string to number](##V4.3.0)
|
||||
|
||||
---
|
||||
|
||||
## V4.3.1 - V4.4.6
|
||||
|
||||
There are no other special instructions.
|
||||
|
||||
---
|
||||
|
||||
## V4.3.0
|
||||
|
||||
Change the setting of THUMBNAIL_DEFAULT_SIZE from string to number in ```seahub_settings.py```:
|
||||
|
||||
Use ```THUMBNAIL_DEFAULT_SIZE = 24```, instead of ```THUMBNAIL_DEFAULT_SIZE = '24'```.
|
||||
|
||||
---
|
||||
|
||||
## V4.2.0 - V4.2.3
|
||||
|
||||
**Note when upgrading to 4.2:**
|
||||
If you deploy Seafile in a non-root domain, you need to add the following extra settings in ```seahub_settings.py```:
|
||||
```
|
||||
COMPRESS_URL = MEDIA_URL
|
||||
STATIC_URL = MEDIA_URL + '/assets/'
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## V4.0.0 - V4.1.2
|
||||
|
||||
There are no other special instructions.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
# Upgrading Seafile Professional Server
|
||||
|
||||
Upgrading Seafile Professional Server works like [upgrading a Seafile Community Server](../deploy/upgrade.md)
|
||||
Upgrading Seafile Professional Server works like [upgrading a Seafile Community Server](../upgrade/upgrade.md)
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ If the problem is not fixed, check whether seafile-server-latest point to the co
|
|||
|
||||
### Avatar pictures vanished after upgrading the server, what can I do?
|
||||
|
||||
* You need to check whether the "avatars" symbolic link under seahub/media/ is linking to ../../../seahub-data/avatars. If not, you need to correct the link according to the "minor upgrade" section in [Upgrading-Seafile-Server](deploy/upgrade.md).
|
||||
* You need to check whether the "avatars" symbolic link under seahub/media/ is linking to ../../../seahub-data/avatars. If not, you need to correct the link according to the "minor upgrade" section in [Upgrading-Seafile-Server](upgrade/upgrade.md).
|
||||
* If your avatars link is correct, and avatars are still broken, you may need to refresh Seahub cache using `rm -rf /tmp/seahub_cache/*` or by restarting memcached if being used.
|
||||
|
||||
## Server can't start
|
||||
|
|
|
|||
|
|
@ -14,6 +14,7 @@ Please check the **upgrade notes** for any special configuration or changes befo
|
|||
* [Upgrade notes for 7.0.x](./upgrade_notes_for_7.0.x.md)
|
||||
* [Upgrade notes for 7.1.x](./upgrade_notes_for_7.1.x.md)
|
||||
* [Upgrade notes for 8.0.x](./upgrade_notes_for_8.0.x.md)
|
||||
* [Upgrade notes for 9.0.x](./upgrade_notes_for_9.0.x.md)
|
||||
|
||||
## Major version upgrade (e.g. from 5.x.x to 6.y.y)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue