The Weblate Manual 3.0.1
Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar0 码力 | 376 页 | 1.51 MB | 1 年前3The Weblate Manual 3.0
Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar0 码力 | 376 页 | 1.51 MB | 1 年前3The Weblate Manual 3.1.1
Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Correctly configure HTTPS Enable indexing offloading Use powerful database engine Enable caching0 码力 | 376 页 | 1.56 MB | 1 年前3The Weblate Manual 3.1
Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Correctly configure HTTPS Enable indexing offloading Use powerful database engine Enable caching0 码力 | 376 页 | 1.56 MB | 1 年前3The Weblate Manual 3.4
Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control permissions Database setup for Weblate PostgreSQL Creating a database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating a database in Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct sitename Correctly configure HTTPS Use a powerful database engine Enable caching Avatar0 码力 | 415 页 | 1.73 MB | 1 年前3The Weblate Manual 3.3
Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Correctly configure HTTPS Use powerful database engine Enable caching Avatar0 码力 | 403 页 | 1.75 MB | 1 年前3Weblate 3.2.1 Documentation
Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Correctly configure HTTPS Use powerful database engine Enable caching Avatar0 码力 | 398 页 | 1.65 MB | 1 年前3The Weblate Manual 3.2
Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Correctly configure HTTPS Use powerful database engine Enable caching Avatar0 码力 | 398 页 | 1.65 MB | 1 年前3The Weblate Manual 3.2.2
Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Correctly configure HTTPS Use powerful database engine Enable caching Avatar0 码力 | 399 页 | 1.64 MB | 1 年前3The Weblate Manual 3.5
Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control permissions Database setup for Weblate PostgreSQL Creating a database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating a database in Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct sitename Correctly configure HTTPS Use a powerful database engine Enable caching Avatar0 码力 | 419 页 | 1.75 MB | 1 年前3
共 519 条
- 1
- 2
- 3
- 4
- 5
- 6
- 52