Introducing the Symfony Maker Bundle

If you've been around the Symfony community for some time so I think you have used the SensioGeneratorBundle. It's a popular bundle that provides console commands to generate boilerplate code, like controllers and entities. It also includes a basic CRUD generator.

Given that SensioGeneratorBundle is starting to show its age and considering the massive simplifications introduced by Symfony 4, they decided to stop evolving that bundle and they've created a new bundle called SymfonyMakerBundle.

SymfonyMakerBundle helps you creating empty commands, controllers, form classes, tests and more so you can forget about the required boilerplate code. It's an alternative to SensioGeneratorBundle for modern Symfony applications and requires using Symfony 3.4 or newer and Symfony Flex.

Of course the end goal is to not have boilerplate code at all in Symfony applications. Symfony 4 made a lot of improvements towards that goal, but you will always have to bootstrap some code, so having a modern, simple and lightweight bundle to do that is nice.

Generating Code with Makers

The usage of the bundle is similar to SensioGeneratorBundle, but the commands now use the make: prefix instead of generate: In this bundle you can find few commands as below:

php bin/console list make

make:command

make:controller

make:entity

make:form

make:functional-test

make:subscriber

make:twig-extension

make:unit-test

make:validator

make:voter

Comments

As a symfony developer what you should take care when symfony standard edition is legacy:

Now symfony standard edition is legacy . So no need to worry much just go threw article and understand whats new in symfony 4 if standard edition is legacy now. This is the main difference in Symfony 4 from symfony 2 and symfony 3 . Older symfony versions provide by default doctrine, twig, form, validation, profiler, annotations and many other components. But some time user do not want to use it. Suppose what if user do not want to doctrine or twig? Still he has doctrine and twig in his dependency. That makes symfony heavy framework. When starting a new project developers do not like to assemble things manually. So symfony 2 and 3 provides standard edition for developers to start a big project. But was hard to scale down project and decrease dependency if user do not require some packages. Symfony 2 and 3 are big success and in years developers are now aware with composer and dependency injection. So adding/removing a new package is not a big deal. So symfony chose...

3 Node.js Alternatives To WordPress

3 Node.js Alternatives To WordPress As compare to WordPress there is alternative option like Node.js. There are many various latest challengers that have large communities, support themes, plugins and are easy to install on your own server. Here are 3 you might want to checkout. KeystoneJS KeystoneJS is a content management system and framework to build server applications that interact with a database. It is based on the Express framework for Node.js and uses MongoDB for data storage. It represents a CMS alternative for web developers who want to build a data-driven website but don’t want to get into the PHP platform or large systems like WordPress. EnduroJS Enduro.js offers a fast and easy way to build your project, beautiful and simple admin UI and integrated tools to build everything on the server. It works without a database, instead relying on a system of flat files that can be opened directly in a text editor. It is easy to install and can be deployed via Git. ...

Laravel: How to protect .env files?

.env files: If you develop your applications using Laravel, you probably use .env files every day in your development life. We use these files to store the most secret information of our application. Be it database credentials, the application key or any third-party service credentials. So simply put: We do not want anyone to get access to these files! But the truth is: quite a few .env files are accessible. And I don’t mean that they are accessible by some hackers, but by Google. To search for public .env files, all you need to do is google for one of these terms: DB_USERNAME filetype:env DB_PASSWORD filetype:env APP_DEBUG filetype:env Secure your .env files The reason that these .env files are accessible and also get scraped is because of two things: Misconfigured shared hosting The .env file has the wrong access rights Shared hosting If you use shared hosting, please make sure that the root folder of your Laravel application is not accessib...

Search This Blog