TYPO3 Flow 2.0 in the field - webtech Conference 2013

Patrick Lobacher | typovision GmbH | 29.10.2013

TYPO3 Flow 2.0 in the Field

Agenda
• What is TYPO3 Flow?
• Installation
• Base paradigms
• In the ﬁeld
• What else is inside TYPO3 Flow?
• What‘s new in TYPO3 Flow?
Patrick Lobacher | typovision GmbH | 29.10.2013 | TYPO3 Flow in the ﬁeld

What is TYPO3 Flow?


TYPO3 Flow is a PHP web
application platform enabling
developers creating excellent
web solutions.

History
•

•

Versions

•
•
•
•

FLOW3 1.0.0 alpha1 / 02.06.2009 (started in 2005)
FLOW3 1.0.0 / 20.10.2011
FLOW3 1.1.0 / 24.08.2012 (Rebranding in October 2012)
TYPO3 Flow 2.0 / 12.07.2013

Background

•
•
•

Written by the TYPO3 community from scratch
to have a solid code base for the next generation CMS TYPO3 Neos
Inﬂuenced by viFramework, Spring Framework, AspectJ,
NanoContainer, Ruby on Rails, Symfony, QT, Doctrine and surely
more


Features
•
•
•
•
•
•

Domain Driven Design

•
•
•

HTTP-Support

Aspect-Oriented Programming
Dependency Injection
Model-View-Controller
Property Mapping & Validation
Convention over
Conﬁguration
Resource Management

•
•
•
•
•

Security

•
•
•

Error & Exception Handling

Session Handling
Command Line
Cloud ready
Internationalization &
Localization
TDD & Debugging
Speed & Performance

Templating


Requirements
•

•

•
•

Supported operation systems

•
•
•

Linux
Mac OS X
Windows (Vista or later)

Supported HTTP server plattforms

•
•
•

Apache 2
NGINX
IIS

PHP 5.3.2 or higher
All systems supported by Doctrine 2 ORM can be used

Installation


Installation
Download of Composer (Dependency Manager for PHP)
curl -s https://getcomposer.org/installer | php


Installation
Download of TYPO3 Flow via Composer:
composer create-project --dev --keep-vcs typo3/flow-basedistribution flow 2.0.0

Link to Document Root (which is ﬂow/Web)
rm htdocs
ln -s flow/Web htdocs

(Use composer update to update installation)

Directory structure
Directory

Description

Configuration/

Application specific configuration, grouped by contexts

Data/

Persistent and temporary data, including caches, logs, resources

Web/

Public web root

flow

Flow command line tool

Build/

Build files (e.g. Surf)

Packages/

Contains sub directories which in turn contain package directories

Packages/Framework/

Packages which are part of the official TYPO3 Flow distribution

Packages/Application/ Application specific packages
Packages/Libraries/

3rd party libraries

bin/

Helper functions


File permissions
Most of the directories and ﬁles must be readable and writable for the user you're
running TYPO3 Flow with. This user will usually be the same one running your web
server (httpd, www-data, www or _www on most Unix based systems).
Set permissions
• 1. Parameter: Shell-User
• 2. Parameter: Webserver-User
• 3. Parameter: Webserver-Group
sudo ./flow core:setfilepermissions patricklobacher _www _www


Groups
Now that the ﬁle permissions are set, all users who plan using TYPO3 Flow from the
command line need to join the web server's group.
On a Linux machine this can be done (for user patricklobacher and group _www) by
typing:
sudo usermod -a -G _www patricklobacher
On a Mac type
sudo dscl . -append /Groups/_www GroupMembership patricklobacher


Web server conﬁguration
Assuming that you chose Apache 2 as your web server, simply create a new virtual host by
adding the following directions to your Apache conﬁguration (conf/extra/httpdvhosts.conf on many systems; make sure it is actually loaded with Include in
httpd.conf):
httpd.conf:
<VirtualHost *:80>
DocumentRoot /var/apache2/htdocs/flow/Web/
ServerName flow.dev
SetEnv FLOW_CONTEXT Development
</VirtualHost>
<VirtualHost *:80>
DocumentRoot /var/apache2/htdocs/flow/Web/
ServerName flow.live
SetEnv FLOW_CONTEXT Production
</VirtualHost>
<Directory /var/apache2/htdocs/flow/>
AllowOverride FileInfo Options=MultiViews
</Directory>


Web server conﬁguration
Add the following line to your /etc/hosts ﬁle (C:
windowssystem32driversetchosts on Windows):
127.0.0.1 flow.live flow.dev


Set up database
Copy Settings-File:
cp Configuration/Settings.yaml.example Configuration/Settings.yaml

Edit Configuration/Settings.yaml (2 blanks indent):
TYPO3:
Flow:
persistence:
backendOptions:
host: '127.0.0.1'
dbname: 'flow'
user: 'root'
password: 'password'

#
#
#
#

adjust
adjust
adjust
adjust

to
to
to
to

your
your
your
your

database
database
database
database


host
name
user
pass

Migration
If you conﬁgured everything correctly, the following command will create
the initial table structure needed by TYPO3 Flow:
./flow doctrine:migrate


Testing
Now call the following URL in your browser
http://flow.dev/


Base Paradigms


•

•

•

An approach which ...

•
•
•

results in rich domain models
provides a common language (ubiquacross the project team
simplify the design of complex applications

The premise of TYPO3 Flow is:

•

Placing the project's primary focus on the core domain and domain
logic

•
•

Basing complex designs on a model of the domain
Introducing an ubiquitous language which concerns all assets

TYPO3 Flow is the ﬁrst PHP framework tailored to Domain-Driven
Design

DDD Model (incl. ubiquitous language UL)
Domain Object (Entity,Value Object)
Aggregate (Aggregate Root)
Repository
Service
Relation
Strategic Pattern (Sub-/Domain, Bounded Context, Context Map)

MVC
Model View Controller Stack (DVC)
Domain/
Model/
Repository/
Validator/
Controller/
View/

In the ﬁeld a step-by-step example


Domain Model
We assume a pretty simple domain Model:
n

Blog
title

Post
title

description
posts

1


Kickstart the package
Let's create a new package Blog inside the vendor namespace IPC:
./flow kickstart:package IPC.Blog

If you want to have more information about the commands, you can use:
./flow help
./flow help kickstart:package


Now call the package:
http://flow.dev/IPC.Blog


Kickstart Controllers
If you compare with our domain model we need a controller for the
Domain Model „Post“.
We also need a SetupController which initially sets up the blog.
Create them with the kickstarter as well:
./flow kickstart:actioncontroller IPC.Blog Setup


Kickstart Controllers
Kickstart PostController (and all related ﬁles):
./flow kickstart:actioncontroller --generate-actions -generate-related IPC.Blog Post

Update database:
./flow doctrine:update

Test them with:
http://flow.dev/IPC.Blog/Setup
http://flow.dev/IPC.Blog/Post

Kickstart Blog Model
Kickstart Blog Model:
./flow kickstart:model IPC.Blog Blog title:string
description:string 'posts:DoctrineCommonCollections
Collection'


Kickstart
Blog Model


Edit Blog Model
Edit Blog Model to look like the following(Packages/Application/
IPC.Blog/Classes/IPC/Blog/Domain/Blog.php):


Add to Blog Model
Add to Blog Model to look like the following(Packages/Application/
IPC.Blog/Classes/IPC/Blog/Domain/Blog.php):


Kickstart Post Model
Kickstart Post Model:
./flow kickstart:model --force IPC.Blog Post 'blog:IPCBlog
DomainModelBlog' title:string linkTitle:string date:
DateTime author:string content:string


Edit Post Model
Edit Blog Model to look like the following(Packages/Application/
IPC.Blog/Classes/IPC/Blog/Domain/Post.php):


Kickstart Blog Repository
Kickstart Blog Repository:
./flow kickstart:repository IPC.Blog Blog


Repository
• There are „magic“ methods available
•
•
•
•
•
•
•
•

add
remove
update
findAll
findBy[PropertyName]
findOneBy[PropertyName]
count
countBy[PropertyName]


Repository - Examples


Setup - Controller - 1
Edit Setup Controller
to look like the following
(Packages/Application/IPC.Blog/
Classes/IPC/Blog/Controller/
SetupController.php):


Setup - Controller - 2
Edit Setup Controller
to look like the following
(Packages/Application/IPC.Blog/
Classes/IPC/Blog/Controller/
SetupController.php):


Index Action / Setup Controller


Edit Blog Repository
Edit Blog Repository:


Edit Post Controller
Edit Post Controller:


Index Action / Post Controller


What else is inside TYPO3 Flow?


Templating via Fluid
•
•

TYPO3 Flow has its own template engine called Fluid.
Focus on the following features:

•

Support of logical structures (such as conditions, widgets,
conditions, loops, iteration over array, ...)

•
•
•
•
•

No PHP code in the template ﬁle
Easy to expand through ViewHelper (reusable)
Simple but intuitve syntax
Provide an XML structure for automated template validation
Highly object oriented

Templating via Fluid


Persistence
•

Object Persistence in the Flow is

•
•
•
•
•
•
•

based on Doctrine 2
integrates seamless into Flow
provides all the great Doctrine 2 features
provides Doctrine 2 Migrations
uses UUIDs
provides a low level persistence API
allows for own, custom persistence backends (instead of Doctrine 2)

•

e.g. Solr or CouchDB


Aspect oriented programming
•

Loggin without AOP


•

Loggin with AOP


•
•

AOP is used for in TYPO3 Flow for

•
•
•
•

persistence magic
logging
debugging
security

•
•
•
•
•

@FlowBefore
@FlowAfterReturning
@FlowAfterThrowing
@FlowAfter
@FlowAround

Advices within TYPO3 Flow


Security
•
•
•
•
•
•
•
•
•
•

as many default build-in security mechanism as possible
CSRF protection
SQL-Injection protection
Cross Site Scripting (XSS) protectipn
centrally managed through AOP
modeled after TYPO3 CMS and Spring Security
supports authentication, authorization, validation, ﬁltering, security policies, ...
can intercept arbitrary method calls
transparently ﬁlters content through query-rewriting
highly extensible for new authmechanisms


And many more...


What is new in Flow 2.0?


Lazy Dependency Injection
•

Consider a controller which depends on 15 other services. Not all
of these are used in every action. And since most of these services
may in turn depend on other services which have even further
dependencies, you end up loading maybe hundreds of class files
which are not needed for the particular action to be executed.

•

In Flow 2.0 dependencies injected through Property Injection are
now "lazy" by default. Developers can uses these dependencies like
before, but the instance is created and thus the class file is only
loaded when the service is actually used the first time. Apart from
a few special cases this process is completely transparent to the
developer.

•

This will increase the speed of the application enormous


Safe Request Methods
•

The HTTP 1.1 speciﬁcation states that the GET and HEAD request
methods should be considered "safe", which means that they should
not do anything other than retrieve information.

•

In Flow 2.0 we now enforce this rule by disabling the automatic
persistence for "safe" request methods.

•

In practice this means, for example, that simple links pointing to a
"delete" action will still call that action, but the delete operation will
not be persisted to the database.

•

Since we know that there won't be data modiﬁcations in "safe"
requests, we also don't need to protect links to these actions with
CSRF tokens. Or, in other words, links to a “delete” action will not
really delete anything, so applications must use another non-safe
request method, like POST, if they want the change to be persisted.

Composer
•

Flow 2.0 comes with a whole new package management
layer based on Composer (https://getcomposer.org), the
de-facto standard for PHP dependency management.

•

Take a few minutes reading the Composer
documentation and getting familiar with its concepts.
While it takes a few days getting into the new
workﬂow, you will love how much easier it is to use
third party packages now. Just look at all the third-party
libraries listed on packagist.org and you’ll begin to see
some of the amazing possibilities with composer.

Session
•

While creating a Single-Sign On Client / Server solution based on Flow,
we wanted to be able to access and modify remote sessions in a multisite setup. While PHP's native session implementation does support
alternative storage backends, there is no official way to modify this data,
except for the currently active session.

•

Flow 2.0 now provides a clean session mechanism written in pure PHP.
Instead of creating a whole new API for the storage, we chose to just rely
on Flow's caching framework: that way you can store session data in the
file system, APC, Memcache, Redis, PDO compatible databases and more.

•

The Session Manager now provides additional functions to retrieve
arbitrary sessions by identifier or by tags. This way it is possible to tag a
session, for example, with a customer number and allow a support team
have a closer look at possible problems or even log out a user remotely.


REST Support
•

Various changes added even better support for
creating and consuming RESTful web services.

•

One important change introduces support for
HTTP Method Tunneling: in situations where it is
not possible to send a true DELETE or PUT
request (or any other request type), it is now
possible simulate the request method by sending
a POST request either with a "__method"
argument or with a special HTTP request header.

Links


Links
•
•
•
•
•

http://flow.typo3.org/
http://flow.typo3.org/documentation.html
http://jweiland.net/flow.html
http://www.typovision.de/de/
kompetenzen/typo3/
http://de.slideshare.net/plobacher/typo3neos-the-compendium


Patrick Lobacher
•
•
•
•
•
•
•
•
•

43 years, happily married, residing in Munich
Author of 9 books and > 40 articles on the subject of TYPO3
and web development
Active in the web deveopment area since 1994
Certiﬁed TYPO3 Integrator since 2009
Until 2012 member of the teams Extbase (Leader),
Certiﬁcation and Content editoral
Until 2012 member of the EAB (Expert Advisory Board)
Co-Organizer of the TYPO3camp Munich (2008-2013) and
TYPO3 Developer Days (T3DD12)
Speaker at national and internation conferences
Lecturer for leading training institutes and MVHS

Publications:


typovision GmbH
• Full service digital communications agency based in Munich & NRW
• >40 employees (+ 15 from freelancer pool)
• CEO: Sebastian Böttger (CTO), Patrick Lobacher (CMO)
• Highly specialized in TYPO3 since 10 years (Extbase/Fluid since 2009)
• Platinum TYPO3 Association Member since 3 Jahren
• Specialized in Enterprise Search (Solr, Elastic Search) since 3 years
• Focus: Premium Open Source Web Technlologies and CMS
• Agency proﬁl (german): www.typovision.de/dieagentur
• More than 600 projects of any size
• Vision:

We are the partner of our clients in all areas of its digital
communication - from the initial vision to the successful
implementation and far beyond.


Customers


Contact
Traditional:

Twitter:

www.twitter.com/typovision
www.twitter.com/PatrickLobacher
www.twitter.com/crosscontent
Facebook:

www.facebook.com/typovision

typovision GmbH
Elsenheimerstr. 7
80687 Munich
Phone:

+49 89 45 20 59 3 - 0
Fax:

+49 89 45 20 59 3 - 29
Email:

Web:

info@typovision.de
www.typovision.de

XING:

www.xing.com/companies/typovisiongmbh
www.xing.com/proﬁle/Patrick_Lobacher
www.xing.com/proﬁle/Sebastian_Boettger2
LinkedIn
www.linkedin.com/company/2038844

Blog:
typoblog.de

Slideshare:

www.slideshare.net/plobacher
www.slideshare.net/typovision

Trainings:
academy.typovision.de

Amazon:

www.amazon.de/Patrick-Lobacher/e/
B0045AQVEA


Thanks a lot!

TYPO3 Flow 2.0 in the field - webtech Conference 2013

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (12)

Similar to TYPO3 Flow 2.0 in the field - webtech Conference 2013

Similar to TYPO3 Flow 2.0 in the field - webtech Conference 2013 (20)

More from die.agilen GmbH

More from die.agilen GmbH (20)

Recently uploaded

Recently uploaded (20)

TYPO3 Flow 2.0 in the field - webtech Conference 2013