phifa/typo3stack

There is no license information available for the latest version (v0.2.1) of this package.

TYPO3 CMS Base Distribution and Site Skeleton

v0.2.1 2019-01-24 14:18 UTC

Requires

• helhum/dotenv-connector: ^1.0.0
• helhum/typo3-console: ^5.6
• phifa/template: dev-master
• phifa/template_site1: dev-master
• typo3/cms-belog: ^9.5
• typo3/cms-beuser: ^9.5
• typo3/cms-fluid-styled-content: ^9.5
• typo3/cms-form: ^9.5
• typo3/cms-impexp: ^9.5
• typo3/cms-info: ^9.5
• typo3/cms-lowlevel: ^9.5
• typo3/cms-opendocs: ^9.5
• typo3/cms-recycler: ^9.5
• typo3/cms-reports: ^9.5
• typo3/cms-rte-ckeditor: ^9.5
• typo3/cms-scheduler: ^9.5
• typo3/cms-seo: ^9.5
• typo3/cms-setup: ^9.5
• typo3/cms-sys-note: ^9.5
• typo3/cms-tstemplate: ^9.5
• typo3/minimal: ^9.5

Unknown License

README

by phifa

TLDR:

composer create-project phifa/typo3stack=dev-master --prefer-dist .

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. 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

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

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