PHPackages garvinhicking/tdk-project - 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. [Framework](/categories/framework) 4. / 5. garvinhicking/tdk-project ActiveProject[Framework](/categories/framework) garvinhicking/tdk-project ========================= TYPO3 Composer Development Kit: Project-Template 03PHP Since Nov 24Pushed 2y ago1 watchersCompare [ Source](https://github.com/garvinhicking/tdk-project)[ Packagist](https://packagist.org/packages/garvinhicking/tdk-project)[ RSS](/packages/garvinhicking-tdk-project/feed)WikiDiscussions main Synced 1mo ago READMEChangelogDependenciesVersions (1)Used By (0) tdk-project =========== [](#tdk-project) Provides a template to be used for "composer create-project" to: - Create your own project - Utilize [tdk-core](https://github.com/garvinhicking/tdk-core) and [tdk-cli](https://github.com/garvinhicking/tdk-cli) - Deliver SQL dumps and custom packages - Have the normal ddev and composer experience - Enjoy life - Have some kids This work is based on the shoulders of giants: - [ochorocho/tdk](https://github.com/ochorocho/tdk) - [helhum/composer-mono](https://github.com/helhum/composer-mono) Thanks to Jochen Roth, Stefan Bürk, Andreas Wolf (and unbeknownst Helmut Hummel) for bearing with me, talking about this idea time and again. ;) How to ------ [](#how-to) ### Create from scratch [](#create-from-scratch) ``` ## Initialize a composer project by using a boilerplate composer create-project --stability dev garvinhicking/tdk-project my-tdk-demo ## Change to the new directory chdir my-tdk-demo ## Now you can install the actual TYPO3-cms packages as a ## dev-dependency (you are actually using a dev-setup, so ## in my world, you're good!) ## Using "composer install" at this point would install ## locked versions of the PACKAGIST, so we actually ## run "composer update" at this point to both update ## and install the local packages. Sounds confusing? Yes. It is. composer update ``` ### Create from existing repository [](#create-from-existing-repository) The project created via the method above can be committed to your own repository. You can then clone your directory and set it up with the TYPO3-core via: ``` ## Clone your repository (can be anything, must not be GitHub) git clone git@github.com:your-vendor/your-repo.git my-tdk-demo ## Change to directory cd my-tdk-demo ## Install the required modules WITHOUT DEV FIRST (see note) ## !!!VERY IMPORTANT!!! composer install --no-dev ## That will have then checked out your sources. Now you should ## be able to update composer and install the dev-dependencies ## properly. composer update ``` ### Follow-up: DDEV [](#follow-up-ddev) This project also provides a default DDEV configuration. You can use `ddev start` to start it. There is basic configuration provided with the tdk-project dummy, but you'll need to initialize the database. This is done easiest via `ddev ssh` and then: ``` TYPO3_DB_DRIVER=mysqli \ TYPO3_DB_USERNAME=db \ TYPO3_DB_PORT=3306 \ TYPO3_DB_HOST=db \ TYPO3_DB_DBNAME=db \ TYPO3_DB_PASSWORD=db \ TYPO3_SETUP_ADMIN_PASSWORD="SuperDuper0815." \ TYPO3_SETUP_ADMIN_EMAIL=admin@example.com \ TYPO3_SETUP_ADMIN_USERNAME=admin \ TYPO3_SETUP_CREATE_SITE="https://tdk-project.ddev.site/" \ TYPO3_PROJECT_NAME="TYPO3 Development Kit" \ TYPO3_SERVER_TYPE="apache" \ ./vendor/bin/typo3 setup --force ``` If you spin-off your own project, you should: - Edit `.ddev/config.yaml` and configure your own hostname - Provide your own `config/sites/tdk-project/` Site configuration - Provide your own `config/system/*.php` Core configuration Just do it ---------- [](#just-do-it) You should now have a working TYPO3 environment with backend and frontend. Your directory `typo3-core` is a distinct GIT working directory. You can go to that directory and perform usual `git` operations, like pulling, cherry-picking. You could theoretically also change branches, but you will have to adjust your composer.json then to reflect version numbers. This repository is aimed at `main` development (currently: TYPO3 v13). After using `git pull` to update to the most recent TYPO3 changes, you should maybe also run `composer update` in your root directory. This allows you to be sure that dependencies can be resolved. Within the `typo3-core` directory you can ALSO run a `composer install`so that all development packages are installed within that tree. This will allow you to run usual developer tasks, like the `Build/Scripts/runTests.sh`script together with `phpstan` etc. When you contribute to the TYPO3-core like that, you can use your working directory within this project. Just remember that you need to operate GIT within that `typo3-core` directory. If you operate GIT outside that directory, you are doing changes to the `tdk-project`-specific directory. This one never holds TYPO3-specific core information, it's only a wrapper so that you can utilize `TYPO3` in composer mode. The largest benefit is that you can put custom extensions into the `/packages/`subdirectory, and require those with `composer` (in your project root, not the `typo3-core` subdirectory). These extensions will then be available in your TYPO3-Installation. And it allows you to store these extension in the main project repository, so other people can easily check out aspects of the `TYPO3 Core` with your extension provided. You can also add custom `SQL dump` files to this repository and allow easy (re)import via `ddev import-db` (and `ddev export-db`). Notes ----- [](#notes) Currently a nasty workaround is employed that tries to solve a specific problem. We can only list and properly install `typo3/cms-*` packages in `composer.json`, once the `vendor/bin/tdk-cli clone` command has succeeded. Because without the local repository, these packages cannot be installed from the local GIT repository. And the local git repository cannot be created before the packages are listed, because people may check out a project without yet having the GIT working directory. We need to put `composer.json` inside this repository for people to be able to spin-off a custom project and make it run. Now the workaround is that we use "require-dev" on the actual TYPO3 packages, and first start a "composer install" by not requiring the packages (where we would not be able to find the local packages) Surely there's a better way for it. I just haven't found that yet. Help! :-) TODO ---- [](#todo) - CLI asking which extensions to be loaded - add githooks - add git commit template - ...? ### Health Score 13 — LowBetter than 1% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity3 Limited adoption so far Community7 Small or concentrated contributor base Maturity20 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure 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. ### Community Maintainers ![](https://avatars.githubusercontent.com/u/273326?v=4)[Garvin Hicking](/maintainers/garvinhicking)[@garvinhicking](https://github.com/garvinhicking) --- Top Contributors [![garvinhicking](https://avatars.githubusercontent.com/u/273326?v=4)](https://github.com/garvinhicking "garvinhicking (16 commits)") ### Embed Badge ![Health badge](/badges/garvinhicking-tdk-project/health.svg) ``` [![Health](https://phpackages.com/badges/garvinhicking-tdk-project/health.svg)](https://phpackages.com/packages/garvinhicking-tdk-project) ``` ### Alternatives [laravel/telescope An elegant debug assistant for the Laravel framework. 5.2k67.8M192](/packages/laravel-telescope)[spiral/roadrunner RoadRunner: High-performance PHP application server and process manager written in Go and powered with plugins 8.4k12.2M84](/packages/spiral-roadrunner)[nolimits4web/swiper Most modern mobile touch slider and framework with hardware accelerated transitions 41.8k177.2k1](/packages/nolimits4web-swiper)[laravel/dusk Laravel Dusk provides simple end-to-end testing and browser automation. 1.9k36.7M259](/packages/laravel-dusk)[laravel/prompts Add beautiful and user-friendly forms to your command-line applications. 708181.8M596](/packages/laravel-prompts)[cakephp/chronos A simple API extension for DateTime. 1.4k47.7M121](/packages/cakephp-chronos) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)