PHPackages phijufa/typo3stack - 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. phijufa/typo3stack ActiveLibrary phijufa/typo3stack ================== TYPO3 CMS Base Distribution and Site Skeleton v0.2.1(7y ago)1173PHP Since Dec 12Pushed 7y ago1 watchersCompare [ Source](https://github.com/phifa/typo3stack)[ Packagist](https://packagist.org/packages/phijufa/typo3stack)[ RSS](/packages/phijufa-typo3stack/feed)WikiDiscussions master Synced 2mo ago READMEChangelogDependencies (21)Versions (7)Used By (0) Composer-based DDEV TYPO3 Multidomain Setup and Surf Deployment =============================================================== [](#composer-based-ddev-typo3-multidomain-setup-and-surf-deployment) *by phifa* TLDR: ----- [](#tldr) `composer create-project phifa/typo3stack=dev-master --prefer-dist .` Notes ----- [](#notes) - During the installation several external extensions are installed. Additionally two local extensions are installed `template` and `template_site1`. - The `template` extension is the Base and should not be changed at all. - Every root site in the pagetree can get its own child template `template_site1`, `template_site2`, ... - First perform installation below. Customization will be done afterwards during integration below. - For multi-domain setup, copy the child extension and repeat integration for each domain. - **Overwriting:** All overwriting is done in the child extension: You can hide the standard Backend Layouts, add your own or overwrite them, same is true for FLUID files, etc. In `page.typoscript` you can overwrite the `css` and the `js` files with your own files, etc. When overwriting, make sure to stick to naming conventions, as only the same name will overwrite. 1. Installation --------------- [](#1-installation) 1. Create your project folder and cd into it. Then: `composer create-project phifa/typo3stack=dev-master --prefer-dist .` 2. Copy configuration templates from `/presets/` to their place, customize and rename if neccessary. 3. Run `ddev start` or modify the ddev configuration first (e.g. change the name) 4. Modify `.env-example` in project root accordingly and rename to `.env`. File is in shipped `.gitignore` and should be created for each context. 5. Run `ddev ssh`, then `./post-create-project-cmd.sh`. 6. `exit` ssh session. 7. Log in to the Backend and add the admin user to the Admin Group (Page UIDs should become visible in the pagetree after page refresh). 8. Also double check under the module `Access`, that all pages point to the group: `[ACCESS] Default`, if not already the case. 9. Now template\_site1 template is up and running. For customization see below **Integration** If the the name of the DDEV container was not changed, these are the urls: ``` Frontend: http://template.ddev.local https://template.ddev.local http://127.0.0.1:32775 MailHog: http://template.ddev.local:8025 phpMyAdmin: http://template.ddev.local:8036 ``` 2. Integration -------------- [](#2-integration) 1. Run `./renameextension.sh` and double check in changelog which files got changed. 2. Now the child template needs to be added again in two places in the backend: Add the TypoScript Template and the TSconfig to the Root Page. You might have to set the Backend Layout (and Sublevels) to `Test` again on the Root Page. 3. Modify constants of the child template accordingly. `config.name`, etc. 4. Clear System Caches and open your dev site, e.g. `http://mydomain.localhost`. Voila! 5. Configure sites first, with sites module. 3. Deployment via Bitbucket Pipeline and Surf --------------------------------------------- [](#3-deployment-via-bitbucket-pipeline-and-surf) 1. Make sure Git is set up correctly for your project and origin is set to the Bitbucket Repository. 2. There should be a Master Branch that will deploy to the client's live site and a Staging Branch that will deploy to the client's stage subdomain 3. You only need to customize the configuration in `.surf/`. The files are called in `bitbucket-pipelines.yml` ### Health Score 26 — LowBetter than 43% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity12 Limited adoption so far Community4 Small or concentrated contributor base Maturity55 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 ~14 days Total 4 Last Release 2668d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/adee69abeaf5e0a8bbbe52e8948001fb0a0cbb3b47bafb006f98893d8c84c533?d=identicon)[phijufa](/maintainers/phijufa) --- Tags typo3 ### Embed Badge ![Health badge](/badges/phijufa-typo3stack/health.svg) ``` [![Health](https://phpackages.com/badges/phijufa-typo3stack/health.svg)](https://phpackages.com/packages/phijufa-typo3stack) ``` ### Alternatives [typo3/cms-base-distribution TYPO3 CMS Base Distribution 21570.2k47](/packages/typo3-cms-base-distribution)[typo3/cms-introduction The Official TYPO3 Introduction Package 1880.6k5](/packages/typo3-cms-introduction) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)