PHPackages                             kuntaliitto/kuntafibase - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. kuntaliitto/kuntafibase

ActiveProject

kuntaliitto/kuntafibase
=======================

Project template for Thunder projects with composer

v0.1(7y ago)181[9 issues](https://github.com/Kuntaliitto/kuntafibase/issues)GPL-2.0+ShellCI failing

Since Oct 30Pushed 5y ago1 watchersCompare

[ Source](https://github.com/Kuntaliitto/kuntafibase)[ Packagist](https://packagist.org/packages/kuntaliitto/kuntafibase)[ RSS](/packages/kuntaliitto-kuntafibase/feed)WikiDiscussions 8.x-7.x Synced today

READMEChangelog (1)Dependencies (63)Versions (5)Used By (0)

Thunder based KuntaFi installation
==================================

[](#thunder-based-kuntafi-installation)

This project template should provide a kickstart for managing your site dependencies with [Composer](https://getcomposer.org/).

```
composer install
composer drupal:scaffold

```

Usage
-----

[](#usage)

See our [install documentation](https://thunder.github.io/thunder-documentation/quick-install) on how to use Thunder project. We also have documentation on [extending](https://thunder.github.io/thunder-documentation/quick-install#install-extend) and [updating](https://thunder.github.io/thunder-documentation/quick-install#install-update) Thunder sites.

What does the template do?
--------------------------

[](#what-does-the-template-do)

When installing the given `composer.json` some tasks are taken care of:

- Drupal will be installed in the `docroot`-directory.
- Autoloader is implemented to use the generated composer autoloader in `vendor/autoload.php`, instead of the one provided by Drupal (`docroot/vendor/autoload.php`).
- Modules (packages of type `drupal-module`) will be placed in `docroot/modules/contrib/`
- Theme (packages of type `drupal-theme`) will be placed in `docroot/themes/contrib/`
- Profiles (packages of type `drupal-profile`) will be placed in `docroot/profiles/contrib/`
- Downloads Drupal scaffold files such as `index.php`, or `.htaccess`
- Creates `sites/default/files`-directory.
- Latest version of drush is installed locally for use at `bin/drush`.
- Latest version of DrupalConsole is installed locally for use at `bin/drupal`.

### File update

[](#file-update)

This project will attempt to keep all of your Thunder and drupal core files up-to-date; the project [drupal-composer/drupal-scaffold](https://github.com/drupal-composer/drupal-scaffold)is used to ensure that your scaffold files are updated every time drupal/core is updated. If you customize any of the "scaffolding" files (commonly .htaccess), you may need to merge conflicts if any of your modfied files are updated in a new release of Drupal core.

Follow the steps below to update your thunder files.

1. Run `composer update`
2. Run `git diff` to determine if any of the scaffolding files have changed. Review the files for any changes and restore any customizations to `.htaccess` or `robots.txt`.
3. Commit everything all together in a single commit, so `docroot` will remain in sync with the `core` when checking out branches or running `git bisect`.
4. In the event that there are non-trivial conflicts in step 2, you may wish to perform these steps on a branch, and use `git merge` to combine the updated core files with your customized files. This facilitates the use of a [three-way merge tool such as kdiff3](http://www.gitshah.com/2010/12/how-to-setup-kdiff-as-diff-tool-for-git.html). This setup is not necessary if your changes are simple; keeping all of your modifications at the beginning or end of the file is a good strategy to keep merges easy.

FAQ
---

[](#faq)

### Should I commit the contrib modules I download

[](#should-i-commit-the-contrib-modules-i-download)

Composer recommends **no**. They provide [argumentation against but also workrounds if a project decides to do it anyway](https://getcomposer.org/doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md).

### How can I apply patches to downloaded modules?

[](#how-can-i-apply-patches-to-downloaded-modules)

If you need to apply patches (depending on the project being modified, a pull request is often a better solution), you can do so with the [composer-patches](https://github.com/cweagans/composer-patches) plugin.

To add a patch to drupal module foobar insert the patches section in the extra section of composer.json:

```
"extra": {
    "patches": {
        "drupal/foobar": {
            "Patch description": "URL or local path to patch"
        }
    }
}
```

### Should I commit the scaffolding files?

[](#should-i-commit-the-scaffolding-files)

The [drupal-scaffold](https://github.com/drupal-composer/drupal-scaffold) plugin can download the scaffold files (like index.php, update.php, …) to the web/ directory of your project. If you have not customized those files you could choose to not check them into your version control system (e.g. git). If that is the case for your project it might be convenient to automatically run the drupal-scaffold plugin after every install or update of your project. You can achieve that by registering `@drupal-scaffold` as post-install and post-update command in your composer.json:

```
"scripts": {
    "drupal-scaffold": "DrupalComposer\\DrupalScaffold\\Plugin::scaffold",
    "post-install-cmd": [
        "@drupal-scaffold",
        "..."
    ],
    "post-update-cmd": [
        "@drupal-scaffold",
        "..."
    ]
},
```

### How can I prevent downloading modules from Thunder, that I do not need?

[](#how-can-i-prevent-downloading-modules-from-thunder-that-i-do-not-need)

To prevent downloading a module, that Thunder provides but that you do not need, add a replace block to your composer.json:

```
"replace": {
    "drupal/features": "*"
}
```

This example prevents any version of the feature module to be downloaded.

### Extending

[](#extending)

Minimum requirements for KuntaFi base packages can be installed

```
composer require kuntaliitto/kuntafibase_core --prefer-source
composer require kuntaliitto/kuntafibase_basic_page --prefer-source
composer require kuntaliitto/kuntafibase_basic_article --prefer-source
composer require kuntaliitto/kuntafibase_blog --prefer-source
composer require kuntaliitto/kuntafibase_book --prefer-source
composer require kuntaliitto/kuntafibase_contacts --prefer-source
composer require kuntaliitto/kuntafibase_now --prefer-source
composer require kuntaliitto/kuntafibase_paragraphs --prefer-source
composer require "drupal/allowed_formats":"1.x-dev"
composer require "drupal/ajax_comments":"1.0-beta2"

```

### Export configuration

[](#export-configuration)

To make pull request the configuration needs to be written into modules optional configuration. We use drupal consoles help.

```
drupal cect basic_article --module="kuntafibase_basic_article" --optional-config --remove-uuid --remove-config
-hash
drupal config:export --directory="modules/custom/kuntafibase_core" --remove-uuid --remove-config-hash

```

The export will add some fields and taxonomies to the export and they are not needed because they are general and they are added by the `kuntafibase_core` module. Example taxonomy channel, municipalities, type are not needed anymore and therefore you need to clean before doing the PR.

### Import custom module configuration

[](#import-custom-module-configuration)

Module configuration is installed only once while installation. Updating the `kuntafibase_***`configuration can be done by drush:

```
drush cim --partial --source=modules/custom/kuntafibase_/config/optional/

```

where `***` is subtituted by the modulename

###  Health Score

20

—

LowBetter than 14% of packages

Maintenance0

Infrequent updates — may be unmaintained

Popularity11

Limited adoption so far

Community4

Small or concentrated contributor base

Maturity54

Maturing project, gaining track record

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~75 days

Total

2

Last Release

2639d ago

Major Versions

v0.1 → 8.x.6.x-dev2019-02-18

### Community

Maintainers

![](https://www.gravatar.com/avatar/756bbe901e5ea2c95e807c6230e5c652dcb422a983ca54e15a86716c3254d50e?d=identicon)[wroxbox](/maintainers/wroxbox)

### Embed Badge

![Health badge](/badges/kuntaliitto-kuntafibase/health.svg)

```
[![Health](https://phpackages.com/badges/kuntaliitto-kuntafibase/health.svg)](https://phpackages.com/packages/kuntaliitto-kuntafibase)
```

###  Alternatives

[voidagency/vactory_starter_kit

Vactory is a custom Drupal profile which is developed and released by VOID Agency.

1019.7k](/packages/voidagency-vactory-starter-kit)[drupalwxt/wxt

Project template for Drupal 10 sites built with the WxT distribution.

29159.8k8](/packages/drupalwxt-wxt)[govcms/govcms

GovCMS Drupal Distribution

18997.1k3](/packages/govcms-govcms)[az-digital/az_quickstart

Arizona Quickstart

50234.3k2](/packages/az-digital-az-quickstart)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)