TYPO3 CMS自动化部署：静态模板管理、扩展启停及PackageStates追踪问题

Great questions—these are exactly the kind of manual pain points that can be eliminated with TYPO3's CLI tools and your existing DDEV/Git/Composer setup. Let's tackle each one step by step:

1. Automate Adding/Removing Static Template Includes in Main TS Templates #

TYPO3's built-in CLI commands make this straightforward. You don't need to click around the backend anymore—use these commands directly in your DDEV environment or deployment scripts:

• Add a static template:

  typo3cms template:add-static-template --template-id=YOUR_MAIN_TEMPLATE_UID --key=EXTENSION_KEY.STATIC_TEMPLATE_KEY
  

  Replace YOUR_MAIN_TEMPLATE_UID with the UID of your root TS template (find it in the backend, or run typo3cms template:list to get a full list of templates and their IDs). The EXTENSION_KEY.STATIC_TEMPLATE_KEY is the identifier of the static template you want to include—this is usually defined in the extension's configuration files (look for staticTemplateIdentifier in ext_tables.sql or TypoScript setup files).

• Remove a static template:

  typo3cms template:remove-static-template --template-id=YOUR_MAIN_TEMPLATE_UID --key=EXTENSION_KEY.STATIC_TEMPLATE_KEY
  

To integrate this into your automated flow, add these commands to:

• DDEV hooks (in .ddev/config.yaml under hooks.post-start or hooks.post-import-db)
• Composer scripts (in composer.json under scripts.post-install-cmd or scripts.post-update-cmd)
• Your CI/CD pipeline steps (e.g., GitHub Actions, GitLab CI)

2. Automate Extension Activation/Deactivation #

TYPO3's CLI simplifies this too. Pair these commands with Composer to manage your extension lifecycle end-to-end:

• Activate an extension:

  typo3cms extension:activate EXTENSION_KEY
  

  This works for both Composer-installed and manually added extensions. Since you're using Composer, run this right after composer require to activate the extension automatically.

• Deactivate an extension:

  typo3cms extension:deactivate EXTENSION_KEY
  

  Use this if you need to disable an extension without removing it via Composer—it will update the extension's state in PackageStates.php.

For full automation, add these commands to your deployment workflow. For example, in DDEV, set up a post-start hook to activate required extensions every time the environment starts:

hooks:
  post-start:
    - exec: typo3cms extension:activate site_package my_custom_extension

You can also use typo3cms extension:setup EXTENSION_KEY to run installation wizards or database updates for the extension in one go—perfect for new extensions that need initial configuration.

3. Should PackageStates.php Be Version Controlled? #

Short answer: No, you should not commit PackageStates.php to Git. Here's why:

• It's an auto-generated file that tracks the current state of extensions in your specific environment. Committing it can cause inconsistencies between development, staging, and production (e.g., a dev-only extension activated locally might get deployed to production if the file is committed).
• TYPO3's official best practice recommends excluding it from version control—add it to your .gitignore file:

  typo3conf/PackageStates.php
  

Instead of relying on PackageStates.php in Git, manage your extensions via Composer (so composer.json and composer.lock track which extensions are installed) and use the CLI activation commands above to set the correct state for each environment. If you need to generate a fresh PackageStates.php (e.g., after cloning the repo), run:

typo3cms install:generatepackagestates

This will scan your typo3conf/ext directory and vendor folder to create an up-to-date PackageStates.php file automatically.

内容的提问来源于stack exchange，提问作者god_is_love