We use PHPStorm with PHP 7.2, apache installed, php-xdebug installed in Ubuntu.<\/p>\n
We read the setup guide<\/a>. A good source probably will be also Symfony 3 For Beginners<\/a>.<\/p>\n We are on a Ubuntu 18.10 x64 VM, with a Windows 10 professional host. After installing PHPStorm, it seemed everything was set up, but creating a new project with<\/p>\n would create empty, or almost empty, projects (obviously non-working).<\/p>\n did not solve the problem, which was solved installing missing packages:<\/p>\n Then everything worked. We start with<\/p>\n Another thing that will be useful is the command line interface.<\/p>\n We install it globally with the adviced command<\/p>\n We run also the secuity check with this, as adviced by https:\/\/github.com\/sensiolabs\/security-checker#integration, by running the following from the project base directory.<\/p>\n This will have to be executed periodically (or maybe as part of a final check before release).<\/p>\n Another useful read is the coding standard<\/a> document.<\/p>\n Just remember to do it in Settings \u2192 Language & Frameworks \u2192 PHP \u2192 Symfony. You’ll have to restart PHPStorm (manually).<\/p>\n This starts the server, listening on 127.0.0.1:8000. Navigation to the first page shows the Symfony web debug bar – it will be very useful. The “404” error is expected since there is no route.<\/p>\n We build also a first page for our self-training, following approximately the docs here<\/a>. The example shows how to route using the file routes.yaml, then it mentions that you can “also” route via annotations. The best practice, according to the Symfony docs (https:\/\/symfony.com\/doc\/master\/best_practices\/controllers.html), is to route via annotations<\/em>. So we do it.<\/p>\n The tutorial says we should execute<\/p>\n and we do it. Then we create the file src\/Controller\/TestController.php. We don’t need the lucky numbers example. It is enough to say “hello world” here.<\/p>\n This works, and also the Symfony web debug bar shows that we are authenticated as an anonymous user.<\/p>\n The name=”test” will be needed later, keep it.<\/p>\n The guide says a little about the installation of packages via composer and the usage of flex<\/em>, but it seems to be unnecessary to study this now. We instead try to make a template, which will be very useful later. We create a template:<\/p>\n and change the controller to:<\/p>\n Simply read the routing docs<\/a> (no need to implement anything, it is very straightforward). Then, the controller docs<\/a> show things we already know about, and says the important thing that extending AbstractController<\/em> provides you with the additional methods render<\/em> (already used to render the template), generateUrl(), redirectToRoute() and redirect(). Fetching Services<\/strong> could be useful. It is also mentioned that you can generate controllers<\/strong><\/p>\n and generate an entire CRUD<\/strong> from a Doctrine entity (which we’ll find is the ORM).<\/p>\n In the controller docs we learn also how to generate 404 errors via exceptions.<\/p>\n In the controller we can also access the request object information, by type-hinting an argument with the\u00a0Request <\/strong>type,\u00a0 the session by type-hinting an argument with the SessionInterface<\/strong> type:<\/p>\n Sessions can be used to store information about the user between requests. Session is enabled by default, but will only be started if you read or write from it. Session storage and other configuration can be controlled under the framework.session configuration in config\/packages\/framework.yaml. Stored attributes remain in the session for the remainder of that user’s session. There is a specific documentation.<\/p>\n You can also store special messages, called flash messages<\/strong>, on the user’s session. By design, flash messages are meant to be used exactly once: they vanish from the session automatically as soon as you retrieve them. This feature makes them useful for storing user notifications.<\/p>\n Also there are more tools for responses.\u00a0Like the Request, the Response object has also a public headers property. This is a ResponseHeaderBag<\/strong> that has some nice methods for getting and setting response headers. The header names are normalized so that using Content-Type is equivalent to content-type or even content_type.<\/p>\n The only requirement for a controller is to return a The file() helper provides some arguments to configure its behavior.<\/p>\n$ composer create-project symfony\/skeleton d1\r\n$ composer create-project symfony\/website-skeleton d2<\/pre>\n
$ composer require symfony\/requirements-checker<\/pre>\n
$ sudo apt install php libapache2-mod-php php-mbstring php-xmlrpc php-soap php-gd php-xml php-cli php-zip php-mysql php-curl<\/pre>\n
$ composer create-project symfony\/website-skeleton download_portal<\/pre>\n
$ wget https:\/\/get.symfony.com\/cli\/installer -O - | bash<\/span><\/pre>\n$ sudo mv \/home\/filippo\/.symfony\/bin\/symfony \/usr\/local\/bin\/symfony<\/pre>\n
$ symfony security:check<\/pre>\n
Enabling Symfony plugin in PHPStorm<\/h2>\n
Starting<\/h1>\n
$ composer bin\/console server:start<\/pre>\n
$ composer require annotations<\/pre>\n
<?php\r\n\/\/ src\/Controller\/TestController.php\r\nnamespace App\\Controller;\r\n\r\nuse Symfony\\Component\\HttpFoundation\\Response;\r\nuse Symfony\\Component\\Routing\\Annotation\\Route;\r\n\r\nclass TestController\r\n{\r\n \/**\r\n * @Route(\"\/test\/test\", name=\"test\")\r\n *\/\r\n public function test()\r\n {\r\n return new Response(\r\n '<html><body>Hello world!<\/body><\/html>'\r\n );\r\n }\r\n}<\/pre>\n{# templates\/test\/test.html.twig #}<\/span>\r\n<body><\/code> <h1>{{ salute }} world!<\/span><\/h1>\r\n<\/body><\/code><\/span><\/pre>\n<?php\r\n\/\/ src\/Controller\/TestController.php\r\nnamespace App\\Controller;\r\n\r\nuse Symfony\\Component\\HttpFoundation\\Response;\r\nuse Symfony\\Component\\Routing\\Annotation\\Route;\r\nuse Symfony\\Bundle\\FrameworkBundle\\Controller\\AbstractController;\r\n\r\nclass TestController extends AbstractController\r\n{\r\n \/**\r\n * @Route(\"\/test\/test\")\r\n *\/\r\n public function test()\r\n {\r\n return $this->render('test\/test.html.twig', [\r\n 'salute' => 'Greetings',\r\n ]);\r\n }\r\n}<\/pre>\nFurther reading<\/h2>\n
$ php bin\/console make:controller BrandNewController<\/pre>\n
$ php bin\/console make:crud Product<\/pre>\n
use<\/span> Symfony\\Component\\HttpKernel\\Exception\\NotFoundHttpException<\/span>;<\/span>\r\n\r\n\/\/ generate 404<\/span>\r\n throw<\/span> $this<\/span>-><\/span>createNotFoundException<\/span>(<\/span>'The item does not exist'<\/span>);\r\n<\/span>\/\/ this exception ultimately generates a 500 status error<\/span>\r\n throw<\/span> new<\/span> \\Exception<\/span>(<\/span>'Something went wrong!'<\/span>);<\/span><\/pre>\nuse<\/span> Symfony\\Component\\HttpFoundation\\Request<\/span>;<\/span>\r\nuse Symfony\\Component\\HttpFoundation\\Session\\SessionInterface;\r\n\r\n\/\/ ... in the controller\r\n public<\/span> function<\/span> index<\/span>(SessionInterface $session, <\/span>Request<\/span> $request<\/span>,<\/span> $firstName<\/span>,<\/span> $lastName<\/span>)<\/span>\r\n {\r\n \/\/ access a request parameter<\/span>\r\n $page<\/span> =<\/span> $request<\/span>-><\/span>query<\/span>-><\/span>get<\/span>(<\/span>'page'<\/span>,<\/span> 1<\/span>);<\/span>\r\n \/\/ stores an attribute for reuse during a later user request\r\n $session->set('foo', 'bar');\r\n \/\/ gets the attribute set by another controller in another request\r\n $foobar = $session->get('foobar');\r\n \/\/ uses a default value if the attribute doesn't exist\r\n $filters = $session->get('filters', []);\r\n }<\/span><\/pre>\nResponse<\/code> object.<\/p>\nuse<\/span> Symfony\\Component\\HttpFoundation\\Response<\/span>;<\/span>\r\n\r\n\/\/ creates a simple Response with a 200 status code (the default)<\/span>\r\n$response<\/span> =<\/span> new<\/span> Response<\/span>(<\/span>'Hello '<\/span>.<\/span>$name<\/span>,<\/span> Response<\/span>::<\/span>HTTP_OK<\/span>);<\/span>\r\n\r\n\/\/ creates a CSS-response with a 200 status code<\/span>\r\n$response<\/span> =<\/span> new<\/span> Response<\/span>(<\/span>'<style> ... <\/style>'<\/span>);<\/span>\r\n$response<\/span>-><\/span>headers<\/span>-><\/span>set<\/span>(<\/span>'Content-Type'<\/span>,<\/span> 'text\/css'<\/span>);\r\n\r\n<\/span>\/\/ JSON - returns '{\"username\":\"jane.doe\"}' and sets the proper Content-Type header<\/span>\r\nreturn<\/span> $this<\/span>-><\/span>json<\/span>([<\/span>'username'<\/span> =><\/span> 'jane.doe'<\/span>]);\r\n\r\n\/\/ using <\/span>the file() helper to serve a file from inside a controller:\r\n\/\/ send the file contents and force the browser to download it\r\nreturn $this->file('\/path\/to\/some_file.pdf');<\/pre>\nTemplates<\/h2>\n