Jeśli jesteś właścicielem tej strony, możesz wyłączyć reklamę poniżej zmieniając pakiet na PRO lub VIP w panelu naszego hostingu już od 4zł!

Archive for Wrzesień, 2013

Community News: Packagist Latest Releases for 09.28.2013

Community News: Packagist Latest Releases for 09.28.2013Recent releases from the Packagist:

Source: http://www.phpdeveloper.org/news/20176

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Community News: Packagist Latest Releases for 09.28.2013

Community News: Packagist Latest Releases for 09.28.2013Recent releases from the Packagist:

Source: http://www.phpdeveloper.org/news/20176

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

David Adams: Zero to Jenkins – PHP Continuous Integration

David Adams: Zero to Jenkins – PHP Continuous Integration

David Adams has posted another screencast to YouTube, this time it’s about setting up Jenkins for continuous integration in a PHP-based application. (His previous one about using PHP on Digital Ocean is here).

The tutorial walks you through the entire process, including creating the Vagrant configuration:

  • Installing Jenkins via apt-get
  • Setting up the commands needed to run jobs
  • Configuring it to work with a Bitbucket project
  • Installing plugins/upgrades

  • Security configuration

He also shows some of the results of the job executions, both passing and failing. The video’s about 50 minutes long, so it’s not a quick installation but it is detailed.

Link: https://www.youtube.com/watch?v=PklYO2vYIfc
Source: http://www.phpdeveloper.org/news/20175

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

David Adams: Zero to Jenkins – PHP Continuous Integration

David Adams: Zero to Jenkins – PHP Continuous Integration

David Adams has posted another screencast to YouTube, this time it’s about setting up Jenkins for continuous integration in a PHP-based application. (His previous one about using PHP on Digital Ocean is here).

The tutorial walks you through the entire process, including creating the Vagrant configuration:

  • Installing Jenkins via apt-get
  • Setting up the commands needed to run jobs
  • Configuring it to work with a Bitbucket project
  • Installing plugins/upgrades

  • Security configuration

He also shows some of the results of the job executions, both passing and failing. The video’s about 50 minutes long, so it’s not a quick installation but it is detailed.

Link: https://www.youtube.com/watch?v=PklYO2vYIfc
Source: http://www.phpdeveloper.org/news/20175

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Kristo Vaher: What you should know about API-centric web development and design

Kristo Vaher: What you should know about API-centric web development and design

Kristo Vaher has an interesting post looking at a development technique that’s becoming more and more popular among web applications – API centric design. More development is being focused around reusable APIs than just making applications. Kristo fills you in on a few things you need to know about this technique and some things to watch out for along the way.

Modern web applications are often anything but stateless and consist of layers upon layers of session handling and asynchronous requests, where users can log in and their functionality is dependent upon dozens of checks before a page is returned to their web browser. In order to manage this problem a little better, we have to take discover – or rediscover – something that has existed in desktop software development for a dozen years: API-centric development and design.

For those new to the topic, he explains what an API is and how centering your development focus on it can help in the long run. He suggests that the API should be the software and everything else – clients, outside users, etc – just interacts with it. Some solutions are offered to help encourage this development including:

  • Using a MVC (Model/View/Controller) structure
  • Starting from day one to develop the API
  • Planning before writing any code
  • How teams should be working together, but on different elements

Link: http://waher.net/archives/1158
Source: http://www.phpdeveloper.org/news/20174

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Kristo Vaher: What you should know about API-centric web development and design

Kristo Vaher: What you should know about API-centric web development and design

Kristo Vaher has an interesting post looking at a development technique that’s becoming more and more popular among web applications – API centric design. More development is being focused around reusable APIs than just making applications. Kristo fills you in on a few things you need to know about this technique and some things to watch out for along the way.

Modern web applications are often anything but stateless and consist of layers upon layers of session handling and asynchronous requests, where users can log in and their functionality is dependent upon dozens of checks before a page is returned to their web browser. In order to manage this problem a little better, we have to take discover – or rediscover – something that has existed in desktop software development for a dozen years: API-centric development and design.

For those new to the topic, he explains what an API is and how centering your development focus on it can help in the long run. He suggests that the API should be the software and everything else – clients, outside users, etc – just interacts with it. Some solutions are offered to help encourage this development including:

  • Using a MVC (Model/View/Controller) structure
  • Starting from day one to develop the API
  • Planning before writing any code
  • How teams should be working together, but on different elements

Link: http://waher.net/archives/1158
Source: http://www.phpdeveloper.org/news/20174

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Engine Yard Blog: Deploying PHP Applications on Engine Yard: A How-To

Engine Yard Blog: Deploying PHP Applications on Engine Yard: A How-To

Matthew Weier O’Phinney has written up an article for the Engine Yard blog walking you through the full process of getting a PHP site set up and working with their platform-as-a-service hosting.

I’ve been experimenting with a variety of cloud Platform as a Service (PaaS) offerings lately, and naturally was interested in seeing what Engine Yard brought to the table for PHP developers with its Engine Yard Cloud offering. Deployment of my application includes several non-trivial aspects, and I wanted to see how easy, or difficult, it was to accomplish each.

He lists some of his criteria (including deployment from a git repo, usage of Composer and cronjobs) and notes that the EY service matches all of his needs. The rest of the post goes into the details of the deployment, breaking it up into sections:

  • Initial deployment: Git and Composer
  • Private Configuration setup
  • Deployment Tasks
  • Cronjobs
  • DNS

Link: https://blog.engineyard.com/2013/deploying-php-applications-on-engine-yard-a-how-to
Source: http://www.phpdeveloper.org/news/20173

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Engine Yard Blog: Deploying PHP Applications on Engine Yard: A How-To

Engine Yard Blog: Deploying PHP Applications on Engine Yard: A How-To

Matthew Weier O’Phinney has written up an article for the Engine Yard blog walking you through the full process of getting a PHP site set up and working with their platform-as-a-service hosting.

I’ve been experimenting with a variety of cloud Platform as a Service (PaaS) offerings lately, and naturally was interested in seeing what Engine Yard brought to the table for PHP developers with its Engine Yard Cloud offering. Deployment of my application includes several non-trivial aspects, and I wanted to see how easy, or difficult, it was to accomplish each.

He lists some of his criteria (including deployment from a git repo, usage of Composer and cronjobs) and notes that the EY service matches all of his needs. The rest of the post goes into the details of the deployment, breaking it up into sections:

  • Initial deployment: Git and Composer
  • Private Configuration setup
  • Deployment Tasks
  • Cronjobs
  • DNS

Link: https://blog.engineyard.com/2013/deploying-php-applications-on-engine-yard-a-how-to
Source: http://www.phpdeveloper.org/news/20173

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Engine Yard Blog: Deploying PHP Applications on Engine Yard: A How-To

Engine Yard Blog: Deploying PHP Applications on Engine Yard: A How-To

Matthew Weier O’Phinney has written up an article for the Engine Yard blog walking you through the full process of getting a PHP site set up and working with their platform-as-a-service hosting.

I’ve been experimenting with a variety of cloud Platform as a Service (PaaS) offerings lately, and naturally was interested in seeing what Engine Yard brought to the table for PHP developers with its Engine Yard Cloud offering. Deployment of my application includes several non-trivial aspects, and I wanted to see how easy, or difficult, it was to accomplish each.

He lists some of his criteria (including deployment from a git repo, usage of Composer and cronjobs) and notes that the EY service matches all of his needs. The rest of the post goes into the details of the deployment, breaking it up into sections:

  • Initial deployment: Git and Composer
  • Private Configuration setup
  • Deployment Tasks
  • Cronjobs
  • DNS

Link: https://blog.engineyard.com/2013/deploying-php-applications-on-engine-yard-a-how-to
Source: http://www.phpdeveloper.org/news/20173

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Engine Yard Blog: Deploying PHP Applications on Engine Yard: A How-To

Engine Yard Blog: Deploying PHP Applications on Engine Yard: A How-To

Matthew Weier O’Phinney has written up an article for the Engine Yard blog walking you through the full process of getting a PHP site set up and working with their platform-as-a-service hosting.

I’ve been experimenting with a variety of cloud Platform as a Service (PaaS) offerings lately, and naturally was interested in seeing what Engine Yard brought to the table for PHP developers with its Engine Yard Cloud offering. Deployment of my application includes several non-trivial aspects, and I wanted to see how easy, or difficult, it was to accomplish each.

He lists some of his criteria (including deployment from a git repo, usage of Composer and cronjobs) and notes that the EY service matches all of his needs. The rest of the post goes into the details of the deployment, breaking it up into sections:

  • Initial deployment: Git and Composer
  • Private Configuration setup
  • Deployment Tasks
  • Cronjobs
  • DNS

Link: https://blog.engineyard.com/2013/deploying-php-applications-on-engine-yard-a-how-to
Source: http://www.phpdeveloper.org/news/20173

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>