Purpose: check cert expiry and cert chain issues
Note: domains.txt needs emptyline at end of file
Example output:
059 days of validity left for https://www.google.com, chain fine (issued by GTS CA 1C3)
046 days of validity left for https://www.typo3.org, chain fine (issued by R3)
Next expiry in 46 days
everything fine
Docker provides download links in release note. They promised that
(we) will also include download links in release notes for future releases.
Note:
This little gist is an attempt to describe my vision for a nested content / grid feature for TYPO3. It contains a description of the vision I have and relates this vision to the current blueprint and WIP which are available at https://wiki.typo3.org/Blueprints/StructuredContentContainers and https://review.typo3.org/#/c/41936/.
| composer create-project typo3/cms-base-distribution='^7.6.0' my-test-typo3 --no-interaction | |
| cd my-test-typo3/ | |
| composer require helhum/typo3-console | |
| # This will only work with PHP < 7 as realurl need PHP 5.x | |
| composer require typo3-ter/introduction | |
| cp web/typo3conf/ext/typo3_console/Scripts/typo3cms . | |
| cp web/typo3conf/ext/bootstrap_package/Configuration/Apache/.htaccess web/ | |
| chmod +x typo3cms | |
| ./typo3cms install:setup --non-interactive --database-user-name="root" --database-user-password="root" --database-host-name="localhost" --database-port="3306" --database-name="t3_my_test" --admin-user-name="admin" --admin-password="password" --site-name="Auto Install" | |
| ./typo3cms database:updateschema '*.*' |
Stick to Semantic Versioning.
The official way of releasing TYPO3 extensions is to the TER, extensions existing solely as Git repositories are NOT properly made available to the community.
Dear members of the development team, CU a few days ago I commented the announcement, that Neos and Flow get rid of "TYPO3" as part of their names, as follows:
Removing "TYPO3" from Neos and Flow makes it easier to quietly abandon these products. \o/
Additionally to this tweet I had a small twitter conversation resulting in this tweet: