mirror of
https://github.com/spl0k/supysonic.git
synced 2024-12-22 17:06:17 +00:00
Database setup doc
This commit is contained in:
parent
f92c7110ae
commit
15e5114cd9
39
docs/setup/database.rst
Normal file
39
docs/setup/database.rst
Normal file
@ -0,0 +1,39 @@
|
|||||||
|
Database setup
|
||||||
|
==============
|
||||||
|
|
||||||
|
Supysonic needs a database to run. It can either be a SQLite, MySQL-compatible
|
||||||
|
or PostgreSQL database.
|
||||||
|
|
||||||
|
If you absolutely have no clue about databases, you can go with SQLite as it
|
||||||
|
doesn't need any setup other than specifying a path for the database in the
|
||||||
|
:doc:`configuration <../configuration>`.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
SQLite, while being a viable option, isn't recommended for large
|
||||||
|
installations. First of all its performance *might* start to decrease as the
|
||||||
|
size of your library grows. But most importantly if you have a lot of users
|
||||||
|
reaching the instance at the same time you will start to see the performance
|
||||||
|
drop, or even errors.
|
||||||
|
|
||||||
|
Please refer to the documentation of the DBMS you've chosen on how to create a
|
||||||
|
database. Once it has a database, Supysonic will automatically create the
|
||||||
|
tables it needs and keep the schema up-to-date.
|
||||||
|
|
||||||
|
The PostgreSQL case
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
If you want to use PostgreSQL you'll have to add the ``citext`` extension to the
|
||||||
|
database once created. This can be done when connected to the database as the
|
||||||
|
superuser. How to connect as a superuser might change depending on your
|
||||||
|
PostgreSQL installation (this is **not** the same thing as the OS superuser
|
||||||
|
known as *root* on Linux systems).
|
||||||
|
|
||||||
|
On a Debian-based system you can connect as a superuser by invoking
|
||||||
|
:command:`psql` while being logged in as the *postgres* user. The following
|
||||||
|
commands will install the ``citext`` extension on the database named *supysonic*
|
||||||
|
assuming you are currently logged as *root*. ::
|
||||||
|
|
||||||
|
# su - postgres
|
||||||
|
$ psql supysonic
|
||||||
|
supysonic=# CREATE EXTENSION citext;
|
@ -8,3 +8,4 @@ start serving your music.
|
|||||||
:maxdepth: 2
|
:maxdepth: 2
|
||||||
|
|
||||||
install
|
install
|
||||||
|
database
|
||||||
|
@ -21,7 +21,7 @@ run.
|
|||||||
you're using the *stable* release it might not be available in the packages
|
you're using the *stable* release it might not be available in the packages
|
||||||
yet.
|
yet.
|
||||||
|
|
||||||
If you plan on using it with a MySQL or PostgreSQL you also need the
|
If you plan on using it with a MySQL or PostgreSQL database you also need the
|
||||||
corresponding Python package, ``python-pymysql`` for MySQL or
|
corresponding Python package, ``python-pymysql`` for MySQL or
|
||||||
``python-psycopg2`` for PostgreSQL.
|
``python-psycopg2`` for PostgreSQL.
|
||||||
|
|
||||||
@ -95,7 +95,7 @@ simply installing directly via :command:`pip`.
|
|||||||
This will install Supysonic along with the minimal dependencies it needs to
|
This will install Supysonic along with the minimal dependencies it needs to
|
||||||
run.
|
run.
|
||||||
|
|
||||||
If you plan on using it with a MySQL or PostgreSQL you also need the
|
If you plan on using it with a MySQL or PostgreSQL database you also need the
|
||||||
corresponding package, ``pymysql`` for MySQL or ``psycopg2-binary`` for
|
corresponding package, ``pymysql`` for MySQL or ``psycopg2-binary`` for
|
||||||
PostgreSQL.
|
PostgreSQL.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user