2014-09-02 19:57:10 +04:00
|
|
|
Upgrading to v0.2.0
|
|
|
|
===================
|
|
|
|
|
|
|
|
To upgrade the database schema, run::
|
|
|
|
|
|
|
|
./database-prepare-for-0.2.0.sh "<database>.db"
|
|
|
|
|
|
|
|
|
2014-09-02 20:01:04 +04:00
|
|
|
The home server now requires setting up of SSL config before it can run. To
|
2014-09-02 19:57:10 +04:00
|
|
|
automatically generate some default config that can be edited use::
|
|
|
|
|
|
|
|
$ python synapse/app/homeserver.py \
|
|
|
|
--server-name machine.my.domain.name \
|
|
|
|
--bind-port 8448 \
|
|
|
|
--config-path homeserver.config \
|
|
|
|
--generate-config
|
|
|
|
|
|
|
|
After editing the config, you can run the home server using::
|
|
|
|
|
|
|
|
$ python synapse/app/homeserver.py --config-path homeserver.config
|
|
|
|
|
|
|
|
See the README.rst for more information.
|
|
|
|
|
|
|
|
Also note that many config options have been renamed.
|
|
|
|
|
|
|
|
|
2014-08-22 16:52:38 +04:00
|
|
|
Upgrading to v0.0.1
|
2014-08-22 18:09:03 +04:00
|
|
|
===================
|
|
|
|
|
2014-08-22 16:52:38 +04:00
|
|
|
This release completely changes the database schema and so requires upgrading
|
|
|
|
it before starting the new version of the homeserver.
|
|
|
|
|
|
|
|
The script "database-prepare-for-0.0.1.sh" should be used to upgrade the
|
|
|
|
database. This will save all user information, such as logins and profiles,
|
|
|
|
but will otherwise purge the database. This includes messages, which
|
|
|
|
rooms the home server was a member of and room alias mappings.
|
|
|
|
|
|
|
|
Before running the command the homeserver should be first completely
|
|
|
|
shutdown. To run it, simply specify the location of the database, e.g.:
|
|
|
|
|
|
|
|
./database-prepare-for-0.0.1.sh "homeserver.db"
|
|
|
|
|
|
|
|
Once this has successfully completed it will be safe to restart the
|
|
|
|
homeserver. You may notice that the homeserver takes a few seconds longer to
|
|
|
|
restart than usual as it reinitializes the database.
|
|
|
|
|
|
|
|
On startup of the new version, users can either rejoin remote rooms using room
|
|
|
|
aliases or by being reinvited. Alternatively, if any other homeserver sends a
|
|
|
|
message to a room that the homeserver was previously in the local HS will
|
|
|
|
automatically rejoin the room.
|