Instalacja w systemie macOS

Wymagania sprzętowe

Weblate should run on any contemporary hardware without problems, the following is the minimal configuration required to run Weblate on a single host (Weblate, database and web server):

  • 3 GB of RAM

  • 2 rdzenie procesora

  • 1 GB miejsca


Rzeczywiste wymagania dotyczące instalacji Weblate różnią się znacznie w zależności od rozmiaru zarządzanych tłumaczeń.

Użycie pamięci

The more memory the better - it is used for caching on all levels (file system, database and Weblate). For hundreds of translation components, at least 4 GB of RAM is recommended.


For systems with less memory than recommended, Single-process Celery setup is recommended.

CPU usage

Many concurrent users increase the amount of needed CPU cores.

Storage usage

The typical database storage usage is around 300 MB per 1 million hosted words.

Storage space needed for cloned repositories varies, but Weblate tries to keep their size minimal by doing shallow clones.


For small and medium-sized sites (millions of hosted words), all Weblate components (see Architecture overview) can be run on a single node.

When you grow to hundreds of millions of hosted words, it is recommended to have a dedicated node for database (see Konfiguracja bazy danych dla Weblate).


Wymagania systemowe

Install the dependencies needed to build the Python modules (see Wymagania dotyczące oprogramowania):

brew install python pango cairo gobject-introspection glib libyaml pkg-config zstd xxhash libxmlsec1
pip install virtualenv

Optionally install software for running production server, see Uruchamianie serwera, Konfiguracja bazy danych dla Weblate, Zadania w tle korzystające z Celery. Depending on size of your installation you might want to run these components on dedicated servers.

Instrukcja instalacji lokalnej:

# Web server option 1: NGINX and uWSGI
brew install nginx uwsgi

# Web server option 2: Apache with ``mod_wsgi``
brew install httpd

# Caching backend: Redis
brew install redis

# Database server: PostgreSQL
brew install postgresql

# Gettext for the msgmerge add-on
brew install gettext

Moduły Pythona


We’re using virtualenv to install Weblate in a separate environment from your system. If you are not familiar with it, check virtualenv User Guide.

  1. Utwórz virtualenv dla Weblate:

    virtualenv ~/weblate-env
  2. Utwórz virtualenv dla Weblate:

    . ~/weblate-env/bin/activate
  3. Zainstaluj Weblate wraz ze wszystkimi opcjonalnymi zależnościami:

    # Install Weblate with all optional dependencies
    pip install "Weblate[all]"

    Please check Zależności ythona for fine-tuning of optional dependencies.


    On some Linux distributions running Weblate fails with libffi error:

    ffi_prep_closure(): bad user_data (it seems that the version of the libffi library seen at runtime is different from the 'ffi.h' file seen at compile-time)

    This is caused by incompatibility of binary packages distributed via PyPI with the distribution. To address this, you need to rebuild the package on your system:

    pip install --force-reinstall --no-binary :all: cffi

Konfigurowanie Weblate


The following assumes the virtualenv used by Weblate is activated (by executing . ~/weblate-env/bin/activate). If not, specify the full path to the weblate command as ~/weblate-env/bin/weblate.

  1. Copy the file ~/weblate-env/lib/python3.9/site-packages/weblate/ to ~/weblate-env/lib/python3.9/site-packages/weblate/

  2. Adjust the values in the new file to your liking. You will need to provide at least the database credentials and Django secret key, but you will want more changes for production setup, see Dostosowywanie konfiguracji.

  3. Create the database and its structure for Weblate (the example settings use PostgreSQL, check Konfiguracja bazy danych dla Weblate for a production-ready setup):

    weblate migrate

    Zobacz także


  4. Create an administrator user account admin, generate its password, and copy it to the clipboard; remember to save it for later use:

    weblate createadmin


    If you previously missed/lost the admin password, you can generate a new one with the following command:

    weblate createadmin --update

    Zobacz także


  5. Collect the static files for your web server (see Uruchamianie serwera and Obsługa plików statycznych):

    weblate collectstatic
  6. Compress the JavaScript and CSS files (optional, see Kompresowanie zasobów klienta):

    weblate compress
  7. Start the Celery workers. This is not necessary for development purposes, but strongly recommended otherwise. Zadania w tle korzystające z Celery has more info:

    ~/weblate-env/lib/python3.9/site-packages/weblate/examples/celery start
  8. Start the development server (Uruchamianie serwera details a production setup):

    weblate runserver

Po instalacji

Congratulations, your Weblate server is now running and you can start using it.

  • You can now access Weblate on http://localhost:8000/.

  • Sign in with admin credentials obtained during installation or register with new users.

  • You can now run Weblate commands using weblate command when Weblate virtualenv is active, see Polecenia zarządzania.

  • You can stop the test server with Ctrl+C.

  • Review potential issues with your installation either on /manage/performance/ URL (see Raport wydajności) or using weblate check --deploy, see Instalacja produkcyjna.

Dodawanie tłumaczenia

  1. Open the admin interface (http://localhost:8000/create/project/) and create the project you want to translate. See Konfiguracja projektu for more details.

    All you need to specify here is the project name and its website.

  2. Create a component which is the real object for translation - it points to the VCS repository, and selects which files to translate. See Konfiguracja komponentu for more details.

    The important fields here are: Nazwa komponentu, Repozytorium kodu źródłowego, and Maska pliku for finding translatable files. Weblate supports a wide range of formats including GNU gettext PO (Portable Object), Zasoby z ciągami Androida, Ciągi Apple iOS, Właściwości Java, Format stringsdict or Format Fluent, see Obsługiwane formaty plików for more details.

  3. Once the above is completed (it can be lengthy process depending on the size of your VCS repository, and number of messages to translate), you can start translating.