frommeandClaude Opus 5.5
863dd9de1a
The constants of the sites become editable in Site Management >
Settings (admins only in TYPO3 13.4). settings.definitions.yaml of the
set ep/theme defines all 116 constants plus googleTagManagerId, with the
labels and categories of their constant editor annotations and today's
constants.typoscript values as defaults. Every setting is a string,
yes/no ones with a select of exactly '0' and '1': a bool setting would
hand '' instead of '0' to TypoScript.
config/sites/*/settings.yaml become shared files on the server and leave
git, like settings.php: production is leading, so backend edits survive
deploys, and each environment keeps its own values. Nine settings nobody
reads (twitterUrl, vimeoUrl, cookiefirstKey, ...) were dropped locally;
on production they stay in the seeded files until removed there.
deploy:check:site-settings aborts before anything else touches the
server if one of the shared files is missing or empty: deploy:shared
would create it empty, silently resetting that site to the defaults.
Rollout, after the site set is live: seed the shared files from the
live release once, then deploy:
cd <deploy_path> && for f in current/config/sites/*/settings.yaml; do
mkdir -p "shared/${f#current/}" && rmdir "shared/${f#current/}" &&
cp -p "$f" "shared/${f#current/}"; done
Verified locally: the resolved setup of 43 pages is unchanged and only
the nine unused constants are gone (switched state); the root template
state is unchanged; all 1912 frontend URLs are identical.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
TYPO3 CMS Base Distribution
Get going quickly with TYPO3 CMS.
Prerequisites
- PHP 8.2
- Composer
Quickstart
composer create-project typo3/cms-base-distribution project-name ^13cd project-name
Note that this distribution installs most, but not all of the TYPO3 CMS core extensions. Depending on your need you might also want to install other TYPO3 extensions from packagist.org.
Setup
To start an interactive installation, you can do so by executing the following command and then follow the wizard:
composer exec typo3 setup
Setup unattended (optional)
If you're a more advanced user, you might want to leverage the unattended installation. To do this, you need to execute the following command and substitute the arguments with your own environment configuration.
export TYPO3_SETUP_ADMIN_PASSWORD=$(tr -dc "_A-Za-z0-9#=$()/" < /dev/urandom | head -c24)
composer exec -- typo3 setup \
--no-interaction \
--server-type=other \
--driver=sqlite \
--admin-username=admin \
--admin-email="[email protected]" \
--project-name="My TYPO3 Project" \
--create-site="http://localhost:8000/"
echo "Admin password: ${TYPO3_SETUP_ADMIN_PASSWORD}"
Development server
While it's advised to use a more sophisticated web server such as Apache 2 or Nginx, you can instantly run the project by using PHPs` built-in web server.
TYPO3_CONTEXT=Development php -S localhost:8000 -t public- open your browser at "http://localhost:8000"
Please be aware that the built-in web server is single threaded and only meant to be used for development.
Next steps
License
GPL-2.0 or later