Best Php Training Trivandrum

Deploy your Symfony application on AWS Elastic Beanstalk using CloudFormation The problem I was looking for a way to quickly create a Minimum Viable Stack on AWS with the following properties: Be setup in less than 10min Be able to run a Symfony application Using PostgreSQL on RDS Deployment is easy and fast Non AWS experts can create the MVS But I couldn’t find any out-of-the-box tools so I looked for a solution. Here I describe my journey which ended up with a ready-to-go CloudFormation configuration. Elastic Beanstalk I started working with  Elastic Beanstalk , the PAAS of AWS,  which seemed to be exactly what I needed . Thanks to  this article  on Elastic Beanstalk configuration files and  this one  on how to deploy a Symfony application, I was able to run my application  after some debugging cycles . My problem after that was that I couldn’t reuse my configuration to recreate the whole environment ...

churn-php What is it? churn-php  is a package that helps you identify php files in your project that could be good candidates for refactoring. It examines each PHP file in the path it is provided and: Checks how many commits it has. Calculates the cyclomatic complexity. Creates a score based on these two values. The results are displayed in a table: A file that changes a lot and has a high complexity might be a better candidate for refactoring than a file that doesn't change a lot and has a low complexity. churn-php  only assists the developer to identify files for refactoring. It's best to use the results in addition to your own judgment to decide which files you may want to refactor. Compatibility PHP 7+ Currently does not work on Windows command line. See  #71  for more details. Your project uses Git as version control system. If you want to install  churn-php  in Symfony project, your Symfony components version must be 3.3 o...

How do I deploy my Symfony API -  - Deploy This is the forth post from a series of posts that will describe the whole deploy process from development to production.  The first article is available  here , the second  here  and the third  here . After covering the steps 1-3 and having prepared our infrastructure, we can see how to  deploy  our application to production. Almost the same approach can be used to deploy not only to production but also to test environments. Workflow Different "git push" operation should trigger different actions. Just as example a push to  master  should trigger a deploy to production, while other branches may trigger a deploy to a test environment, or not trigger deploys at all. I've used  Circe CI Workflows  to manage this set of decisions. Workflows are just another section from the same  .circleci/config.yml  file and here they are: workflows: version: 2 build_and...