Estensioni
Flarum è minimalista, ma è anche altamente estensibile. In effetti, la maggior parte delle funzionalità fornite con Flarum sono in realtà estensioni!
Questo approccio rende Flarum estremamente personalizzabile: Puoi disabilitare tutte le funzionalità che non ti servono e installare altre estensioni per rendere il tuo forum perfetto per la tua comunità.
Per ulteriori informazioni sulla filosofia di Flarum su quali funzionalità includiamo nel core o se stai cercando di creare la tua estensione, consulta la documentazione estensioni. Questo articolo si concentrerà sulla gestione delle estensioni dal punto di vista dell'amministratore del forum.
Extension Manager
The extension manager is an extension that comes bundled with Flarum when installed via an archive. It provides a graphical interface for installing and updating both extensions and Flarum itself.
If you do not have the extension manager installed and you wish to install it, you can do so by running the following command in your Flarum directory:
composer require flarum/extension-manager:"*"
The extension manager allows an admin user to install any composer package. Only install the extension manager if you trust all of your forum admins with such permissions.
Trovare le estensioni
Flarum ha un vasto ecosistema di estensioni, molte delle quali sono open source è grautie. Per trovare nuove e fantastiche estensioni, visita il tag Estensioni sul forum ufficiale di Flarum. Il non ufficiale Database estensioni Extiverse è anch'esso una valida alternativa.
Installare le estensioni
Through the interface
Using the extension manager extension, you can install extensions directly from the admin dashboard. Once you have browsed the list of available extensions from the links above, and found one you want to install, you can install it by entering the extension's composer package name into the extension manager's installation input.
Through the command line
Proprio come Flarum, le estensioni vengono installate tramite Composer, usando SSH. Per installare un estensione:
cd
nella tua directory Flarum.cd
fino alla cartella che contienecomposer.json
. Puoi controllare i contenuti della directory tramitels -la
.- Lancia
composer require COMPOSER_PACKAGE_NAME:*
. Questo solitamente compare nel post o nella documentazione dell'estensione.
Gestire le estensioni
Through the interface
Using the extension manager extension, you can update extensions directly from the admin dashboard. You can run a check for updates by clicking the "Check for updates" button in the extension manager. If there are updates available, you can update all extensions by clicking the "Global update" button. Or, you can update individual extensions by clicking the "Update" button next to the extension you want to update.
Through the command line
Seguire le istruzioni fornite dagli sviluppatori di estensioni. Se stai usando *
come stringa di versione per le estensioni (come raccomandato), eseguire i comandi elencati nella guida di aggiornamento di Flarum dovrebbe aggiornare tutte le estensioni.
Disinstallazione Delle Estensioni
Through the interface
Using the extension manager extension, you can uninstall extensions directly from the admin dashboard. You can uninstall an extension by clicking the "Uninstall" button next to the extension you want to uninstall inside the extension's page.
Through the command line
Analogamente all'installazione, per rimuovere un'estensione:
- If you want to remove all database tables created by the extension, click the "Purge" button in the admin dashboard. Per maggiori informazioni, vedere qui sotto.
cd
nella tua directory Flarum.- Lancia
composer require COMPOSER_PACKAGE_NAME
. Questo solitamente compare nel post o nella documentazione dell'estensione.
Gestire le estensioni
Each individual extension page of the admin dashboard provides a convenient way to manage the extension. Potrai:
- Enable or disable the extension.
- See the settings provided by the extension, and change them.
- Revert an extension's migrations to remove any database modifications it made (this can be done with the Purge button). Ciò rimuoverà TUTTI i dati associati all'estensione ed è irreversibile. Dovrebbe essere fatto solo quando rimuovi un'estensione e non prevedi di installarla di nuovo. È anche del tutto facoltativo.
- See the extension's README, if it has one.
- See the extension's version.
- Uninstall the extension if the extension manager is installed.
Configuring additional extension repository sources
The extension manager uses composer
under the hood, and as such, it looks for extension packages in the same places as composer
. By default, this is Packagist. However, you can configure additional sources for the extension manager to look for extensions in. This is useful if you want to install an extension that is not available on Packagist.
In the admin page of the extension manager, clicking the Add Repository button will open a modal where you can enter the name and URL of the repository you want to add. The name is just a label for the repository, and can be anything you want. The URL should be the URL of the repository which depends on the type of repository you want to add.
Adding a repository from a VCS
If you want to add a repository from a VCS (e.g. GitHub, GitLab, BitBucket, etc), the URL should be the URL of the repository's VCS. For example, if you had a private GitHub repository at https://github.com/acme/flarum-extension
, you would enter that URL into the URL field. If it is a private source, you will need to enter an authentication method through the New authentication method button. The token can be generated from your VCS provider's website, and the host should be the domain of the VCS provider (e.g. github.com
).
Adding a composer repository
Extiverse provides access to premium extensions. It is a good example of a composer repository. You would specify the URL as https://flarum.org/composer/
and the name as premium
. You would also need to enter an authentication method through the New authentication method button. The token can be generated from your Flarum account's subscriptions page with the Instructions button.
- Type:
HTTP Bearer
- Host:
flarum.org
The configured repositories and auth methods will be active for both the command line and the admin dashboard. If you configure them from the command line however, you must not include the flag --global
.
Installing Non-stable extensions
If for whatever reason you want to install a non-stable extension (e.g. a beta, alpha or RC version) you must first update the Minimum stability setting to the wanted stability.
- If you set it to Alpha, you will be able to install alpha, beta, RC (Release Candidate) and stable versions.
- If you set it to Beta, you will be able to install beta, RC and stable versions.
- If you set it to RC, you will be able to install RC and stable versions.
- If you set it to Stable, you will only be able to install stable versions.