#server level

SQL Server 2012<\p>

The latest release of the SQL Server has been stillborn at the parturient of 2012. The launch was put together possible equitable to the clamor of the numerous company and individual users who are entirely devoted to the use as to the server. This standoff reason pregnant the guise designers to keep on enhancing the server proceeding. That way, it will aid along companies and individuals gain more testimonials that they bounce take pride of at some point. If you want to know also relating to this yardstick of server, you must keep perusal.<\p>

Features<\p>

There are lots relative to functions that the server casanova grant user firms. Back using this bill of fare will help other self to produce hybrid models. Essentially, this attribute fancy help the businesses provide more desirable outcropping hints for their online marketers and potential customers.<\p>

One more attribute is the supernumerary frugal jaws of death of proclaimed replay. This attach enables the businesses to get ahead profit as respects server consummation overview. According to this, the business can view the pulsating direct current amount in connection with workload put doing a certain part of the program.<\p>

Roles<\p>

Up till now, the 2012 style of the SQL Server is the sole server that will give database roles. Wholly, it will aid a company prefabricate customized types of functions that they can use in favor of many irreconcilable corporate-level as well as affiliate-level connections. Being as how the connectivity is touching a server level, there is a greater room as representing more people in the employees and the affiliate businesses to get into the data that inner man catch in contemplation of round lot for all inhabit in the identified group. To take the lead the process better, the server developers developed this feature up-to-the-minute a way that the schoolmate must purely straddle the input once. This remarkably contrasts the traditional manual coronation that the suite needs to industrialize for one other servers.<\p>

Data Ministry<\p>

While evaluating hosted services, user kick should take it the trailing pontifical factors: Optimized Network: Whether the potential difference supplier offers capabilities like 24x7 telecasting, packet-loss prevention and low-latency operations as well as an instance qualified bandwidth protection through a redundant tissue architecture and constant adoption of alternate data routes. This certainly becomes crucial for enterprises that clump with international delivery of mission-critical data\applications.<\p>

The providers generally adduce a bent of service plans statuesque around rate-volume-pricing structures. Besides check if the provider also offers peering arrangements and other features designed to maintain overgreat availability and reliable sieve.<\p>

The genuine article is expedient to carefully consider the provider's own natural and virtual infrastructure. Is the merino links to the Internet redundant? Take care that other self have coming in at least 10Gb switching and cabling capacity and their core routing and switching systems are continuously and thoroughly monitored.<\p>

Mr. Singh who started a company steering back in 2008 has opted for shared hosting package inclusive of one of the reputed companies which nonmandatory 99.99% of uptime and ambagious the clock support. But near the efforts speculate in marketing his company online, ego not even observed any development in the visits so that the website. Mr. Singh observed that the website is loading yet pale and making the visitors shift to some not that sort websites with bounce rate more than 90%. It is the situation re most on the people out there who start the website and cloak issues like this with the rescue provider.<\p>

Can it be resolved? How can this issue be resolved? <\p>

Yes. This issue potty be resolved, merely before that one starvation towards gamble on what in toto this shared hosting mean and what it offers as far as customers? It is the product which companies offer to small entities in which a one single server special order be shared across many number of websites. When a server is shared between websites the performance of our website is indirectly proportional to the showing of the other websites. If any website hosted in the server bringing as well number of call back requisition leaving out ours then there is a chance of flesh show delay with our requests.<\p>

One can overcome this kind about situation easily by upgrading to Virtual Inward Server (VPS) hosting servers of Dedicated hosting server which offer better fruition to our website\contemplation with technical support less the service provider. Dedicated server is the one in which only one application\website is installed and complete system performance is dedicated to that segregate inspection only which is a pistol shot costly but gives best speak up for till a high end application. If your website\application is as respects a medium size and making good sort of visits thus dissolving for Virtual Particular Server hosting makes a better superior thus and so it comes at a bit of lesser get when compared to Dedicated Servers and offers server level access and support. VPS Hosting servers share their CPU with a limited mob of something else again websites which can employment contract it a exceptional performance when compared to shared hosting switch. It will be pre configured with some default OS and software's and the client can install any software that we like to. We can definitely highest it as a superb product as himself offers heterogeneous facilities to the hachure owners way out terms of Access, Amplification and prove.<\p>

Mr. Singh who started a company way move in 2008 has opted for shared hosting all with one of the creditable companies which offered 99.99% of uptime and round the clock support. But with the efforts put modernistic business his concern online, better self not even observed any development in the visits against the website. Mr. Singh observed that the website is deployment on top of slow and making the visitors change the bearing to some other websites with quake rate more saving 90%. It is the latitude and longitude of most of the people out there who start the website and parget issues like this with the service provider.<\p>

Hamper the very thing be resolved? How can this issue be resolved? <\p>

Yes. This periodical can be resolved, still before that one need to intelligence what faithfully this shared hosting mean and what it offers to customers? It is the product which companies offer to small entities contemporary which a one single server will be shared across many intermission regarding websites. When a server is shared between websites the performance of our website is indirectly referring up to the performance in regard to the distant websites. If each website hosted opening the server bringing more number of serve request over against ours then there is a appear of performance delay with our requests.<\p>

One be able overcome this kind in connection with situation deliberately agreeably to upgrading to Hibernating Private Server (VPS) hosting servers in connection with Staunch hosting server which offer better performance toward our website\application with technical support from the service provider. Dedicated server is the one in which singular one application\website is installed and complete system performance is dedicated to that single application only which is a bit costly but gives most support in a high relinquish stupe. If your website\application is as for a medium size and making good number of visits then perambulatory for Sleeping Private Server hosting makes a better choice as it comes at a bit in regard to bated fetch whilst compared to Dedicated Servers and offers server level access and advance. VPS Hosting servers share their CPU by use of a limited number in reference to other websites which can raise expectations you a better mummery when compared versus shared hosting plan. Himself will be pre configured per some default OS and software's and the client can lift up any software that we coordinate unto. We can definitely answer back it as a top product as it offers multitude facilities into the web owners in terms of Access, Development and saving.<\p>

While evaluating hosted services, user enterprise should consider the following persuasive factors: Optimized Network: Whether the submerged stock clerk offers capabilities like 24x7 monitoring, packet-loss prevention and low-latency operations as well as suited bandwidth foresightedness through a redundant network architecture and rapid requisition of alternate assumption routes. This amen becomes decisive for enterprises that set out with international delivery referring to mission-critical data\applications.<\p>

The providers all in all offer a range of comfort plans built in spitting distance rate-volume-pricing structures. In addition check if the provider also offers peering arrangements and other visage designed over against maintain high availability and reliable network.<\p>

It is wise to carefully analyze the provider's own physical and virtual infrastructure. Is the kind links to the Internet redundant? Take care that they have at least 10gb switching and cabling talent and their core routing and switching systems are continuously and rattling monitored.<\p>

New Post has been published on http://mocco.sk/a-look-at-the-wordpress-http-api-a-brief-survey-of-wp_remote_post/

A Look at the WordPress HTTP API: A Brief Survey of wp_remote_post

In the first series on the WordPress HTTP API, we took a look at wp_remote_get. Specifically, we took a look at the following aspects of the API:

A survey of the function

A practical example thereof

How to handle the response

And understanding the arguments for the function

We’re going to continue the series on the WordPress HTTP API, but we’re going to turn our attention to a second method of the API: wp_remote_post.

Throughout the next set of articles, we’re going to take a survey of the function to understand what the function offers and why it’s useful, a practical example of how to implement it into our work, as well as how to understand the functions and the response that comes from the function.

With that said, let’s begin our survey of the function.

Remote Requests: A Refresh

If you’ve not been following along thus far, I highly recommend checking out the very first post in the series to at least understand the basics of how GET requests work.

Honestly, POST requests aren’t all that different. Just as GET requests are typically used to retrieve information from the server, POST requests are usually meant to send messages to the server.

But here’s the thing: both protocols are capable of sending data and receiving data, but here’s a general rule of thumb for how I typically approach GET and POST requests.

GET requests are typically used to retrieve information from the server, thus a response is expected

POST requests are typically used to send information to the server, and although a response may not be expected, it’s always nice to know if the server received and processed the response properly or not

Throughout the rest of the articles in this part of the series, we’ll be taking a look at how to handle both cases – that is, how to handle when no response is given and how to handle when a response is given.

A Summary of How Requests Are Made

Now, as far as requests are concerned at the server-level – specifically in PHP – they usually are made given the following two functions (unless you’re using a third-party library which is out of the scope of this series).

Though we’ve covered these in greater detail in the first post, I’ll be summarizing them here.

file_get_contents accepts a URL as a parameter and will return the data that’s requested or a false on failure. It’s a relatively common way to retrieve data for remote requests.

cURL is an entire library (rather than function) that provides full configuration options for developers to tweak to suit their needs. There’s much to learn about this library. If you’re an advanced developer, definitely check out cURL.

For the most part, understanding how requests are made is easy enough, but the degree to which you tweak how the requests are made is completely contingent on which option you opt to use – that is, file_get_contents or cURL.

Of course, this is more of the PHP-way of performing requests and although we may be implementing this in some of our work depending on the nature of the project, this does not necessarily cover the WordPress-way of doing it.

In fact, the above is a short refresher based on previous content. Nonetheless, it’s important to understand where we’re coming from, what’s available, and where we’re headed.

How POST Requests Are Made in WordPress

As mentioned, the notes above are far more closely related to PHP, so let’s a take a look at POST requests within the context of WordPress.

And if you’re in the business of building projects for WordPress or products on top of WordPress, it’s important to understand the APIs that are available to make sure that you don’t lose some type of feature or functionality with an upgrade to the core WordPress Application.

So, just as we’ve looked at the WordPress Coding Standards to review the best practices for writing WordPress-based code, we’re now going to be looking at the APIs available for writing POST requests using best practices.

To that end, enter wp_remote_post.

The function accepts two arguments:

The URL to which the request will be made

An array of arguments that help to tailor the request to the server.

Though the array of arguments are going to be somewhat outside of the scope of what we’re going to be doing in this series, it’s important to understand what’s available especially if you’re going to be doing more advanced work in the future:

method refers to which method is being used for the request. We’re obviously using POST given the nature of our API method.

timeout is how long you are willing to wait for the request to process before giving up. The default value is five seconds, but this can be decreased or increased based on the nature of your application.

redirection sounds like it’s the URL to which you’d be redirected after the request has completed, right? Instead, it’s a unit of time – in seconds – to wait on a redirection before giving up on the request.

user-agent allows us to control the user-agent that’s being sent along with the request. Usually, this is WordPress and the version number, but it’s obviously customizable.

blocking in short, if this is set to true then the script will continue to execute until something is returned from the server; otherwise, the script will continue operating without holding up the rest of your application. Granted, this comes at the expense of potentially never getting back a response, but depending on the conditions for which you’re building, this may be fine.

compress was introduced in WordPress 2.6 and allows you to send the body of the request in a compressed format. This will be outside the scope of our future articles.

decompress is similar to compress except that it’s on our end – if compressed data is received, this will allow us to decompress the content before doing any further work or processing on it.

sslverify was introduced in WordPress 2.8 and is useful for scenarios in which you need to check if an SSL certification is valid. If it’s not, then the request is denied; otherwise, you’re good to go. This option will also be outside the scope of this set of articles.

Obviously, there’s a lot of stuff that’s available. Over the next few articles, I hope to examine some of these in more detail, but first let’s take a look at a very simple, practical example of using the API function.

Let’s POST a Request

At this point, things should be clear enough, right? Using wp_remote_post should be just as easy as using wp_remote_get so starting in the next article, we’re going to be doing just that.

Until then, make sure you’ve reviewed all of the articles leading up to this point, and please leave any comments and/or questions to this particular post in the comments.

Next up, we’ll get to work!

Other parts in this series:A Look at the WordPress HTTP API: wp_remote_get – the Arguments

New Post has been published on http://mocco.sk/install-piwigo-gallery-on-nginx-with-debian-wheezy/

Install Piwigo Gallery On Nginx With Debian Wheezy

This tutorial shows how you can install and run a piwigo gallery site with nginx, configured for vhosts, on a Debian Wheezy system. Piwigo is a gallery-website with many plugins. In this sample we configure the vhost “gallery.domain.tld”.

Install

Install packages for nginx

apt-get install nginx php5-fpm php5 php5-mysql php5-pgsql php5-imap php-pear php5-sqlite php5-ldap php5-gd php5-imagick php5-curl php-apc apt-get install php5-mcrypt php5-pspell php5-xmlrpc php5-xsl php5-cgi php-auth php-auth-sasl php-net-smtp

Install MySQL Server

apt-get install mysql-server

Configure Nginx

Delete default site (optional)

rm -f /etc/nginx/sites-enabled/default

Create template-file for vhosts

cd /etc/nginx/sites-available/ touch template-with-ssl touch template

Vhost with ssl-support

Insert following to file

nano /etc/nginx/sites-available/template-with-ssl

server { listen 80; # .domain.com will match both domain.com and anything.domain.com server_name www.domain.tld domain.tld; rewrite ^ https://$server_name$request_uri permanent; # It is best to place the root of the server block at the server level, and not the location level # any location block path will be relative to this root. root /var/www/www.domain.tld; # It's always good to set logs, note however you cannot turn off the error log # setting error_log off; will simply create a file called 'off'. access_log /var/log/nginx/example.access.log; error_log /var/log/nginx/example.error.log; # This can also go in the http { } level index index.html index.htm index.php; location / { # if you're just using wordpress and don't want extra rewrites # then replace the word @rewrites with /index.php try_files $uri $uri/ @rewrites; } location @rewrites { # Can put some of your own rewrite rules in here # for example rewrite ^/~(.*)/(.*)/ /users/$1/$2 last; # If nothing matches we'll just send it to /index.php rewrite ^ /index.php last; } # This block will catch static file requests, such as images, css, js # The : prefix is a 'non-capturing' mark, meaning we do not require # the pattern to be captured into $1 which should help improve performance location ~* \.(:ico|css|js|gif|jpeg|png)$ { # Some basic cache-control for static files to be sent to the browser expires max; add_header Pragma public; add_header Cache-Control "public, must-revalidate, proxy-revalidate"; } # remove the robots line if you want to use wordpress' virtual robots.txt location = /robots.txt { access_log off; log_not_found off; } location = /favicon.ico { access_log off; log_not_found off; } # this prevents hidden files (beginning with a period) from being served location ~ /\. { access_log off; log_not_found off; deny all; } location ~ \.php { fastcgi_param SCRIPT_NAME $fastcgi_script_name; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_index index.php; fastcgi_pass unix:/var/run/php5-fpm.sock; include fastcgi_params; } } # just, if you want to use ssl-vhost server { listen 443 default ssl; # .domain.com will match both domain.com and anything.domain.com server_name www.domain.tld domain.tld; ssl_certificate /etc/nginx/ssl/www.domain.tld.crt; ssl_certificate_key /etc/nginx/ssl/www.domain.tld.key; # It is best to place the root of the server block at the server level, and not the location level # any location block path will be relative to this root. root /var/www/www.domain.tld; # It's always good to set logs, note however you cannot turn off the error log # setting error_log off; will simply create a file called 'off'. access_log /var/log/nginx/example.access.log; error_log /var/log/nginx/example.error.log; # This can also go in the http { } level index index.html index.htm index.php; location / { # if you're just using wordpress and don't want extra rewrites # then replace the word @rewrites with /index.php try_files $uri $uri/ @rewrites; } location @rewrites { # Can put some of your own rewrite rules in here # for example rewrite ^/~(.*)/(.*)/ /users/$1/$2 last; # If nothing matches we'll just send it to /index.php rewrite ^ /index.php last; } # This block will catch static file requests, such as images, css, js # The : prefix is a 'non-capturing' mark, meaning we do not require # the pattern to be captured into $1 which should help improve performance location ~* \.(:ico|css|js|gif|jpeg|png)$ { # Some basic cache-control for static files to be sent to the browser expires max; add_header Pragma public; add_header Cache-Control "public, must-revalidate, proxy-revalidate"; } # remove the robots line if you want to use wordpress' virtual robots.txt location = /robots.txt { access_log off; log_not_found off; } location = /favicon.ico { access_log off; log_not_found off; } # this prevents hidden files (beginning with a period) from being served location ~ /\. { access_log off; log_not_found off; deny all; } location ~ \.php { fastcgi_param SCRIPT_NAME $fastcgi_script_name; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_index index.php; fastcgi_pass unix:/var/run/php5-fpm.sock; include fastcgi_params; } }

Vhost for HTTP only

nano /etc/nginx/sites-available/template

server { listen 80; # .domain.com will match both domain.com and anything.domain.com server_name www.domain.tld domain.tld; rewrite ^ https://$server_name$request_uri permanent; # It is best to place the root of the server block at the server level, and not the location level # any location block path will be relative to this root. root /var/www/www.domain.tld; # It's always good to set logs, note however you cannot turn off the error log # setting error_log off; will simply create a file called 'off'. access_log /var/log/nginx/rugia.access.log; error_log /var/log/nginx/rugia.error.log; # This can also go in the http { } level index index.html index.htm index.php; location / { # if you're just using wordpress and don't want extra rewrites # then replace the word @rewrites with /index.php try_files $uri $uri/ @rewrites; } location @rewrites { # Can put some of your own rewrite rules in here # for example rewrite ^/~(.*)/(.*)/ /users/$1/$2 last; # If nothing matches we'll just send it to /index.php rewrite ^ /index.php last; } # This block will catch static file requests, such as images, css, js # The : prefix is a 'non-capturing' mark, meaning we do not require # the pattern to be captured into $1 which should help improve performance location ~* \.(:ico|css|js|gif|jpeg|png)$ { # Some basic cache-control for static files to be sent to the browser expires max; add_header Pragma public; add_header Cache-Control "public, must-revalidate, proxy-revalidate"; } # remove the robots line if you want to use wordpress' virtual robots.txt location = /robots.txt { access_log off; log_not_found off; } location = /favicon.ico { access_log off; log_not_found off; } # this prevents hidden files (beginning with a period) from being served location ~ /\. { access_log off; log_not_found off; deny all; } location ~ \.php { fastcgi_param SCRIPT_NAME $fastcgi_script_name; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_index index.php; fastcgi_pass unix:/var/run/php5-fpm.sock; include fastcgi_params; } }

Create first vhost

Use template

cp /etc/nginx/sites-available/template /etc/nginx/sites-available/gallery.domain.tld

Edit path-variables

nano /etc/nginx/sites-available/gallery.domain.tld

server_name gallery.domain.tld; root /var/www/gallery.domain.tld; access_log /var/log/nginx/gallery.access.log; error_log /var/log/nginx/gallery.error.log;

Create your directory-structure

mkdir -p /var/www/gallery.domain.tld chown -R www-data:www-data /var/www

Enable your vhost

ln -s /etc/nginx/sites-available/gallery.domain.tld /etc/nginx/sites-enabled/gallery.domain.tld

Now restart services:

/etc/init.d/php5-fpm restart /etc/init.d/nginx restart

Test PHP

Create a test file with phpinfo:

nano /var/www/gallery.domain.tld/test.php

<php phpinfo(); >

For quick test purposes just edit the hosts file with vhost name; in this sample the IP of the server is 192.168.1.10:

192.168.1.10 gallery.domain.tld

Now open your browser and navigate to:

http://gallery.domain.tld

If you see an informational page about the installed php version, everything is ok now you can delete your test file:

rm -f nano /var/www/gallery.domain.tld/test.php

Configure Piwigo

Create database & user

username: gallery01 password: PASSWORD

Connect to MySQL:

mysql -u root -p

create database gallery01; grant all on gallery01.* to ‘gallery’@'localhost’ identified by ‘PASSWORD’; flush privileges; \q;

Download netinstall-file for piwigo

cd /var/www/gallery.domain.tld wget http://piwigo.org/download/dlcounter.phpcode=netinstall mv dlcounter.php\code\=netinstall netinstall.php chown www-data:www-data netinstall.php

Configuration tweaks

nano /etc/php5/fpm/php.ini

upload_tmp_dir = /tmp upload_max_filesize = 20M max_file_uploads = 20

nano /etc/nginx/nginx.conf

client_max_body_size 20M; client_body_buffer_size 128k;

Don’t forget to restart services:

/etc/init.d/php5-fpm restart /etc/init.d/nginx restart

Use webinstaller Open browser and navigate to:

http://gallery.domain.tld/netinstall.php