Joomla! Documentation™

Tutorial
Ni vipi kutayarisha mazingira ya kienyeji kwa Joomla 4

Joomla! 

4.x

Kuanzia Joomla 4, tumebadilisha maendesho ya maendeleo. Haitawezekana tena kudupliketi yaliohifadhiwa na kuwa na usakinishaji wa Joomla iliyo tayari kwa kutmia. Tunafuata mfano mzuri na tumefahamisha maendesho ya kujenga CMS.

Mwongozo wa kuanzisha haraka

Inategemea na mfumo wako wa mwendesho ni vipi utafanya ili uweze kurekebisha mazingira yako ya maendeleo. Hatuwezi kuandika mwongozo kwa kila aina ya mfumo. Kwa hivyo unapaswa kuuliza mashini ya kutafuta kwa kupata maelezo unayohitaji.

Zana unazohitaji

1. PHP - kwa kimsingi hii ni sawa na ya kuendesha tovuti ya Joomla, lakni unahitaji toleo la PHP CLI (command line interface) - angalia kurasa ya Kusanidi seva ya LAMPP kwa maendeleo ya PHP
2. Composer - kwa kusimamia mategemezi ya PHP ya Joomla - kwa usaidizi wa kusakinisha Composer, soma mwongozo katika https://getcomposer.org/doc/00-intro.md
3. Node.js - kwa kukusanya mafaili ya Joomla ya JavaScript na SASS - kwa usaidizi wa kusakinisha Node.js, tafadhali fuata maelezo yanayopatikana kwa https://nodejs.org/en/
4. Git - kwa kusimamia matoleo

Hatua za kurekebisha mazingira ya kienyeji

1. Dupliketi yaliohifadhiwa
2. Anzisha composer install kutoka kwa enzi ya hifadhi ya Git (unaweza kuongeza --ignore-platform-reqs ikiwa hauna PHP-LDAP iliyosakinishwa kwa kienyeji na hauihitaji)
3. Anzisha npm install kutoka kwa enzi ya hifadhi ya Git

Mwongozo mrefu kidogo wa kuanzisha

Joomla is not different to many other web tools these days. It has a large PHP part and it has more and more JavaScript code. While PHP coding doesn't need so much preparation, JavaScript needs a lot tooling around. The main reason is that nobody writes code in a way that every browser understands, so the code needs transpiling from e.g. ES6 to a compatible version of JavaScript. The same is true for CSS, for Joomla we are using SASS and this will be converted to native CSS so that any browser understands it. As downside setting up a dev environment is a bit more complicated but the tooling make coding also more convenient. Thanks to watchers and browser auto reload you can see your change in real time.

PHP

It should be enough to run composer install as this will install PHP dependencies saved in the composer.lock file. You can do this as many times as you like, it will only install new packages when the composer.lock file is changed. Don't run composer update as this will update all packages to newer versions and update the composer.lock file.

Note: You may need to run composer install with the --ignore-platform-reqs option to ignore platform requirements specified in Composer, i.e. if you do not have PHP's LDAP extension installed.

Node/npm scripts

Node.js comes with a package manager called NPM (in some way the same as Composer). NPM has a run command and we have prepared some scripts to make your life easier. You have to run the commands for the root of the repository.

npm run build:css

It will compile SASS files to CSS and also create the minified files.

npm run build:js

It will compile and transpile the JavaScript files to the correct format and create minified files

npm run watch:css

This is the same as the build:css command but will watch for changes and automatically build updated files.

npm run watch:js

This is the same as the build:js command but will watch for changes and automatically build updated files.

npm run lint:js

This will make a syntax check on JavaScript files.

npm run test

This will run other JavaScript testing suite.