Stefan Kecskes

Never stop learning, because life never stops teaching

Continuous Deployment

Part 2 of 2

In previous article, I demonstrated how to set up continuous Integration, that means how to test the code automatically and find out if it is the newest changes to code broke it or not. Now that you are automatically testing your commits, the next logical step in automation process would be to release our tested code to live website. We would want it to happen automatically, when all tests pass.

Continuous Integration with Strider

Part 1 of 2

We, developers, are producing websites or applications for many years now. What kinds of tasks needs to be done, before we see the changes live on web. This was a big unknown to me for a very long time. Is my process of deploying the code the best practice? Should I do it other way?

Setting up XDebug for dev environment

I would like to describe how to set up xDebug to work in your phpStorm IDE. There are different options available depending on your preference - you can have xDebug always try to initiate a connection for your devbox, or you can use browser plugins and extensions to choose when xDebug should try to run.

Speed up your website with Pagespeed mod

I’ve heard about some cool stuff that google is doing in one of software engineering podcasts. One of the tools was google pagespeed mod. It seemed to improve performance of the Apache2 webserver so I decided to give it a try.

Laravel validator for CSS selectors

Last week I was building a backend tool in Laravel, where you could create layout in bootstrap 3 and add CSS selectors like id or class to any container. You wanted to be able to enter more than one class name into input field. Let’s say that you want to add 2 classes: col-xs-6 infoBox_4. Laravel hasn’t validator for this type of string, so I decided to make one.