{
    "version": "https:\/\/jsonfeed.org\/version\/1.1",
    "title": "Discover Docker, K8s and Hashicorp Nomad with Maksym Prokopov: posts tagged nginx",
    "_rss_description": "The blog about containerisation, virtual machines and useful shell snippets and findings",
    "_rss_language": "en",
    "_itunes_email": "",
    "_itunes_categories_xml": "",
    "_itunes_image": "",
    "_itunes_explicit": "",
    "home_page_url": "https:\/\/blog.it-premium.com.ua\/tags\/nginx\/",
    "feed_url": "https:\/\/blog.it-premium.com.ua\/tags\/nginx\/json\/",
    "icon": false,
    "authors": [
        {
            "name": "Maksym Prokopov",
            "url": "https:\/\/blog.it-premium.com.ua\/",
            "avatar": false
        }
    ],
    "items": [
        {
            "id": "190",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/docker-compose-nginx-proxy-container-and-networking\/",
            "title": "docker-compose, nginx-proxy container and networking",
            "content_html": "<p>Well, this issue was my pain in the ass until I fully understood what was going on with nginx-proxy container and docker-compose v2.<\/p>\n<p>When you have <b>docker-compose.yml<\/b> with separate frontend network you need to connect this network to nginx-proxy container in order to work. Obviously, there is <b>no frontend network<\/b> until you up your containers for the first time!<br \/>\nWhen you do<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">docker-compose up<\/code><\/pre><p>network will be created, but nginx-proxy will not be attached to it! So you need to shut down your app containers, do<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">docker network connect itservice_frontend-tier nginx-proxy<\/code><\/pre><p>and then to fire your containers up again! But wait, you need to restart nginx-proxy container to connect to this new network!<\/p>\n<p>As you can see this process can not be single step deployment solution on CoreOS, but now you know why and how to fix this.<\/p>\n",
            "date_published": "2017-12-04T11:54:50+01:00",
            "date_modified": "2017-12-04T11:56:31+01:00",
            "tags": [
                "docker",
                "docker-compose",
                "nginx",
                "ngix-proxy"
            ],
            "_date_published_rfc2822": "Mon, 04 Dec 2017 11:54:50 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "190",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "177",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/quick-oneliner-to-determine-nginx-proxy-is-working\/",
            "title": "Quick oneliner to determine nginx-proxy is working",
            "content_html": "<pre class=\"e2-text-code\"><code class=\"\">curl -H &#039;Host:stage.it-premium.com.ua&#039; https:\/\/192.168.150.62<\/code><\/pre><p>where Host is your host and 192.168.150.62 is your nginx server.<\/p>\n",
            "date_published": "2017-03-28T16:02:01+01:00",
            "date_modified": "2017-03-28T16:35:41+01:00",
            "tags": [
                "nginx"
            ],
            "_date_published_rfc2822": "Tue, 28 Mar 2017 16:02:01 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "177",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "176",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/lets-encrypt-certificate-for-nginx-proxy-docker\/",
            "title": "let’s encrypt certificate for nginx-proxy docker",
            "content_html": "<p>For coreos that’s enough to use something like this<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">docker run -d \\\n  -v \/home\/core\/certificates:\/etc\/nginx\/certs:rw \\\n  --volumes-from nginx-proxy \\\n  -v \/var\/run\/docker.sock:\/var\/run\/docker.sock:ro \\\n  jrcs\/letsencrypt-nginx-proxy-companion\n\ndocker run -d -p 80:80 -p 443:443 \\\n  --name nginx-proxy \\\n  -v \/home\/core\/certificates:\/etc\/nginx\/certs:ro \\\n  -v \/etc\/nginx\/vhost.d \\\n  -v \/usr\/share\/nginx\/html \\\n  -v \/var\/run\/docker.sock:\/tmp\/docker.sock:ro \\\n  -v \/home\/core\/conf.d\/external.conf:\/etc\/nginx\/conf.d\/external.conf  \\\n  --restart always \\\n  jwilder\/nginx-proxy<\/code><\/pre><p>and then not to forget to specify<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">LETSENCRYPT_HOST=mydomain.com\nLETSENCRYPT_EMAIL=my@email.com<\/code><\/pre><p>in your docker-compose section.<\/p>\n<p>More is here <a href=\"https:\/\/hub.docker.com\/r\/mickaelperrin\/docker-letsencrypt-nginx-proxy-companion\/\">https:\/\/hub.docker.com\/r\/mickaelperrin\/docker-letsencrypt-nginx-proxy-companion\/<\/a><\/p>\n",
            "date_published": "2017-03-28T15:52:33+01:00",
            "date_modified": "2017-03-28T16:35:53+01:00",
            "tags": [
                "coreos",
                "docker",
                "nginx"
            ],
            "_date_published_rfc2822": "Tue, 28 Mar 2017 15:52:33 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "176",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "172",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/jwilder-nginx-proxy-debug-in-docker\/",
            "title": "jwilder nginx-proxy debug in docker",
            "content_html": "<p>When your site did not work properly in docker do following:<\/p>\n<ol start=\"1\">\n<li>Check is nginx container running<\/li>\n<\/ol>\n<pre class=\"e2-text-code\"><code class=\"\">docker ps -a<\/code><\/pre><pre class=\"e2-text-code\"><code class=\"\">3fbec7a5431f        jwilder\/nginx-proxy                                &quot;\/app\/docker-entrypoi&quot;   20 hours ago        Up 7 minutes                0.0.0.0:80-&gt;80\/tcp, 0.0.0.0:443-&gt;443\/tcp   nginx-proxy<\/code><\/pre><ol start=\"2\">\n<li>Check if it has proper configuration<\/li>\n<\/ol>\n<pre class=\"e2-text-code\"><code class=\"\">docker exec nginx-proxy nginx -t<\/code><\/pre><p>You should receive<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">nginx: the configuration file \/etc\/nginx\/nginx.conf syntax is ok\nnginx: configuration file \/etc\/nginx\/nginx.conf test is successful<\/code><\/pre><pre class=\"e2-text-code\"><code class=\"\">docker exec nginx-proxy nginx -T<\/code><\/pre><p>this shows configuration of nginx. So, no need to bash into nginx container and do cat \/etc\/nginx\/conf.d\/default.conf. It’s much faster.<\/p>\n<ol start=\"3\">\n<li>Check if your container and nginx container has network connection.<br \/>\nIf not, connect them with<\/li>\n<\/ol>\n<pre class=\"e2-text-code\"><code class=\"\">docker network connect mycontainer_default nginx-proxy<\/code><\/pre><ol start=\"4\">\n<li>Check container logs<\/li>\n<\/ol>\n<pre class=\"e2-text-code\"><code class=\"\">docker logs nginx-proxy -f --tail 250<\/code><\/pre><p>That will show last 250 lines and continues to follow new data.<\/p>\n",
            "date_published": "2017-01-18T09:02:33+01:00",
            "date_modified": "2017-01-18T09:03:21+01:00",
            "tags": [
                "docker",
                "nginx"
            ],
            "_date_published_rfc2822": "Wed, 18 Jan 2017 09:02:33 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "172",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "171",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/how-to-debug-http-traffic-on-linux\/",
            "title": "How to debug HTTP traffic on Linux",
            "content_html": "<p>Short answer: *httpry* is excellent utility for HTTP debugging on Linux.<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">apt-get install -y httpry\nhttpry<\/code><\/pre><pre class=\"e2-text-code\"><code class=\"\">root@d9fbedf5d17d:\/app# httpry -i eth0\nhttpry version 0.1.7 -- HTTP logging and information retrieval tool\nCopyright (c) 2005-2012 Jason Bittel &lt;jason.bittel@gmail.com&gt;\n----------------------------\nHash buckets:       64\nNodes inserted:     10\nBuckets in use:     10\nHash collisions:    0\nLongest hash chain: 1\n----------------------------\nStarting capture on eth0 interface\n2017-01-17 07:44:48\t185.49.14.190\t172.17.0.4\t&gt;\tGET\ttestp3.pospr.waw.pl\thttp:\/\/testp3.pospr.waw.pl\/testproxy.php\tHTTP\/1.1\t-\t-\n2017-01-17 07:44:48\t172.17.0.4\t185.49.14.190\t&lt;\t-\t-\t-\tHTTP\/1.1\t503\tService Temporarily Unavailable\n2017-01-17 07:45:05\t95.67.19.75\t172.17.0.4\t&gt;\tHEAD\tphoto.kiev.ua\t\/\tHTTP\/1.1\t-\t-\n2017-01-17 07:45:06\t172.17.0.4\t95.67.19.75\t&lt;\t-\t-\t-\tHTTP\/1.1\t200\tOK\n2017-01-17 07:45:06\t95.67.19.75\t172.17.0.4\t&gt;\tHEAD\tblog.it-premium.com.ua\t\/\tHTTP\/1.1\t-\t-\n2017-01-17 07:45:06\t172.17.0.4\t172.17.0.6\t&gt;\tHEAD\tblog.it-premium.com.ua\t\/\tHTTP\/1.1\t-\t-\n2017-01-17 07:45:06\t172.17.0.6\t172.17.0.4\t&lt;\t-\t-\t-\tHTTP\/1.1\t200\tOK\n2017-01-17 07:45:06\t172.17.0.4\t95.67.19.75\t&lt;\t-\t-\t-\tHTTP\/1.1\t200\tOK\n2017-01-17 07:46:35\t172.17.0.4\t172.17.0.2\t&gt;\tGET\tneovo.kiev.ua\t\/\tHTTP\/1.1\t-\t-\n2017-01-17 07:46:35\t172.17.0.2\t172.17.0.4\t&lt;\t-\t-\t-\tHTTP\/1.1\t200\tOK\n2017-01-17 07:46:51\t62.80.171.198\t172.17.0.4\t&gt;\tGET\tcondom.org.ua\t\/\tHTTP\/1.1\t-\t-\n2017-01-17 07:46:51\t172.17.0.4\t62.80.171.198\t&lt;\t-\t-\t-\tHTTP\/1.1\t503\tService Temporarily Unavailable\n2017-01-17 07:47:19\t163.172.65.114\t172.17.0.4\t&gt;\tGET\tphoto.kiev.ua\t\/photo_files\/75\/original\/5050.jpg?1458503622\tHT<\/code><\/pre><p>Source <a href=\"http:\/\/xmodulo.com\/sniff-http-traffic-command-line-linux.html\">http:\/\/xmodulo.com\/sniff-http-traffic-command-line-linux.html<\/a><\/p>\n",
            "date_published": "2017-01-17T09:42:36+01:00",
            "date_modified": "2017-01-17T11:20:36+01:00",
            "tags": [
                "nginx"
            ],
            "_date_published_rfc2822": "Tue, 17 Jan 2017 09:42:36 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "171",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "170",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/how-to-expose-internal-website-via-nginx-proxy\/",
            "title": "How to expose internal website via nginx-proxy",
            "content_html": "<p>For instance you have several small-sized dockerized websited on different servers in your internal network with webserver’s IP like 192.168.0.2, 192.168.0.3, 192.168.0.4 and you would like to expose your site to public via single IP address like 95.67.123.18.<\/p>\n<p>Is that possible? Sure, and you can even use great jwilder\/nginx-proxy image for that.<\/p>\n<p>Just create on public webserver folder \/home\/user\/conf.d\/external.conf and put there config like this<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">log_format vhost &#039;$host $remote_addr - $remote_user [$time_local] &#039;\n                 &#039;&quot;$request&quot; $status $body_bytes_sent &#039;\n                 &#039;&quot;$http_referer&quot; &quot;$http_user_agent&quot;&#039;;\nupstream server.it-premium.com.ua {\n  server 192.168.0.2:80;\n}\nserver {\n  server_name server.it-premium.com.ua;\n  listen 80;\n  location \/ {\n    proxy_pass http:\/\/server.it-premium.com.ua;\n  }\n  access_log \/var\/log\/nginx\/access.log vhost;\n}<\/code><\/pre><p>also launch nginx-proxy container with extra arguments<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">-v \/home\/user\/conf.d\/external.conf:\/etc\/nginx\/conf.d\/external.conf<\/code><\/pre><p>that will connect single config file to nginx config folder and will read configuration from there.<br \/>\nBeware, in case you change manually external.conf you’ll need to restart your nginx container, because docker will treat your file as invalid.<\/p>\n",
            "date_published": "2017-01-13T10:55:54+01:00",
            "date_modified": "2017-01-13T10:55:39+01:00",
            "tags": [
                "docker",
                "nginx"
            ],
            "_date_published_rfc2822": "Fri, 13 Jan 2017 10:55:54 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "170",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "165",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/dockerized-gitlab-registry-nginx-proxy-container-with-ssl\/",
            "title": "Dockerized Gitlab + Registry + nginx-proxy container with SSL",
            "content_html": "<p>For me worked following configuration for jwilder\/nginx-proxy container.<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">web:\n  image: &#039;gitlab\/gitlab-ce:latest&#039;\n  hostname: &#039;gitlab.it-expert.com.ua&#039;\n  environment:\n    GITLAB_OMNIBUS_CONFIG: |\n      external_url &#039;https:\/\/gitlab.it-expert.com.ua&#039;\n      registry_external_url &#039;https:\/\/registry.it-expert.com.ua&#039;\n    VIRTUAL_HOST: gitlab.it-expert.com.ua,registry.it-expert.com.ua\n    VIRTUAL_PORT: 443\n    VIRTUAL_PROTO: https\n  volumes:\n    - &#039;.\/data\/config:\/etc\/gitlab&#039;\n    - &#039;.\/data\/logs:\/var\/log\/gitlab&#039;\n    - &#039;.\/data\/data:\/var\/opt\/gitlab&#039;<\/code><\/pre><p>Tricky part was to figure out how containers is connected and which and who should process SSL.<\/p>\n<p>For this configuration you should supply SSL certificates both for nginx-proxy and gitlab-ce containers, because communications between them is also using SSL. For gitlab-ce use .\/data\/config\/ssl folder.<\/p>\n",
            "date_published": "2016-11-08T13:27:38+01:00",
            "date_modified": "2016-11-08T13:27:35+01:00",
            "tags": [
                "docker",
                "gitlab",
                "nginx"
            ],
            "_date_published_rfc2822": "Tue, 08 Nov 2016 13:27:38 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "165",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "157",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/nginx-proxy-configuration-for-server-sent-events-and-ssl\/",
            "title": "nginx-proxy configuration for server sent events and SSL",
            "content_html": "<p>I’ve encountered issue with dropped SSE connection when deployed SSE based sinatra app with SSL certificates and nginx-proxy docker container.<\/p>\n<p>First, create vhost.d directory on host and connect it to \/etc\/nginx\/vhost.d in nginx-proxy container via volume. Create corresponding file to your VIRTUAL_HOST name, which will be included upon nginx startup. In my case that was SSE stream.it-premium.com.ua.<\/p>\n<p>My \/home\/nexus\/vhost.d\/stream.it-premium.com.ua file is following<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">proxy_set_header Connection &#039;&#039;;\nproxy_http_version 1.1;\nchunked_transfer_encoding off;\nproxy_buffering off;<\/code><\/pre><p>But it has still issues with dropped connection.<br \/>\nFinally I’ve updated app code with following headers:<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">response[&#039;Cache-control&#039;] = &#039;no-cache&#039;\nresponse[&#039;X-Accel-Buffering&#039;] = &#039;no&#039;<\/code><\/pre><p>And everything run smoothly after deploy.<\/p>\n",
            "date_published": "2016-10-18T10:07:28+01:00",
            "date_modified": "2016-10-18T10:07:25+01:00",
            "tags": [
                "docker",
                "nginx",
                "server sent events",
                "ssl"
            ],
            "_date_published_rfc2822": "Tue, 18 Oct 2016 10:07:28 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "157",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "149",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/how-to-debug-jwilder-nginx-proxy\/",
            "title": "How to debug jwilder\/nginx-proxy",
            "content_html": "<p>It’s common when you use nginx-proxy by jwilder. It supports SSL in clever way, handy configuration for containers via environment variables, but sometimes issues happened. How can I debug it?<\/p>\n<p>First, check container logs with<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">docker logs nginx-proxy<\/code><\/pre><p>then run nginx configuration test with<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">docker exec nginx-proxy nginx -t<\/code><\/pre><p><small>nginx-proxy container should be up and running<\/small><\/p>\n<p>In case no issues you should receive output something like this:<br \/>\nnginx: the configuration file \/etc\/nginx\/nginx.conf syntax is ok<br \/>\nnginx: configuration file \/etc\/nginx\/nginx.conf test is successful.<\/p>\n<p>Otherwise number of line with issue will be reported.<\/p>\n<p>Then you should verify configuration, the simplest way is to exec following command:<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">docker exec nginx-proxy cat \/etc\/nginx\/conf.d\/default.conf<\/code><\/pre><p>I tackled some weird issues when:<\/p>\n<ol start=\"1\">\n<li>I use docker-compose version 2, and nginx-proxy does not have access to frontend network. In this case you should list<\/li>\n<\/ol>\n<pre class=\"e2-text-code\"><code class=\"\">docker network ls<\/code><\/pre><p>to find out yout frontend network name.<br \/>\nNETWORK ID          NAME                   DRIVER<br \/>\n7fcacd901d8b        bridge                 bridge<br \/>\n4c795ffb838a        itservice_front-tier   bridge<br \/>\nac4c6aeaf804        itservice_back-tier    bridge<br \/>\n55d3d40d2390        none                   null<br \/>\nd0c498886500        host                   host<\/p>\n<p>then<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">docker connect itservice_front-tier nginx-proxy<\/code><\/pre><p>and container become accessible.<\/p>\n<ol start=\"2\">\n<li>In case container expose several ports, like odoo container, and none of them is 80 or 443, you should point with VIRTUAL_PORT proper port for proxying. In my case default.conf configuration of nginx pointed that docker container<\/li>\n<\/ol>\n<pre class=\"e2-text-code\"><code class=\"\">server 172.17.0.5 down;<\/code><\/pre><p>is visible, but down. After specifying VIRTUAL_PORT all things has been resolved.<\/p>\n",
            "date_published": "2016-09-16T10:00:40+01:00",
            "date_modified": "2016-09-16T12:25:09+01:00",
            "tags": [
                "docker",
                "nginx"
            ],
            "_date_published_rfc2822": "Fri, 16 Sep 2016 10:00:40 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "149",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "131",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/nginx-proxy-i-docker-compose-version-2\/",
            "title": "nginx-proxy и docker-compose version 2",
            "content_html": "<p>нужно просто добавить контейнер в сеть с nginx-proxy примерно так<\/p>\n<pre class=\"e2-text-code\"><code class=\"\">docker network add mynet_default nginx-proxy<\/code><\/pre><p>и все работает.<\/p>\n<p>Либо добавлять external: bridge через docker-compose.<\/p>\n",
            "date_published": "2016-07-21T12:30:34+01:00",
            "date_modified": "2016-07-21T12:30:31+01:00",
            "tags": [
                "docker",
                "docker-compose",
                "nginx"
            ],
            "_date_published_rfc2822": "Thu, 21 Jul 2016 12:30:34 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "131",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "74",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/opencart-nginx-rewrite-rules\/",
            "title": "Opencart nginx rewrite rules",
            "content_html": "<pre class=\"e2-text-code\"><code class=\"\">rewrite ^\/sitemap.xml$ \/index.php?route=feed\/google_sitemap last;\n    rewrite ^\/googlebase.xml$ \/index.php?route=feed\/google_base last;\n    rewrite ^\/download\/(.*) \/index.php?route=error\/not_found last;\n    if (!-f $request_filename) {\n        set $rule_3 1$rule_3;\n    }\n    if (!-d $request_filename) {\n        set $rule_3 2$rule_3;\n    }\n    if ($uri !~ &quot;.*.(ico|gif|jpg|jpeg|png|js|css)&quot;) {\n        set $rule_3 3$rule_3;\n    }\n    if ($rule_3 = &quot;321&quot;) {\n        rewrite ^\/([^?]*) \/index.php?_route_=$1 last;\n    }<\/code><\/pre>",
            "date_published": "2015-12-15T12:25:21+01:00",
            "date_modified": "2015-12-15T12:21:36+01:00",
            "tags": [
                "nginx",
                "opencart"
            ],
            "_date_published_rfc2822": "Tue, 15 Dec 2015 12:25:21 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "74",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": []
            }
        },
        {
            "id": "66",
            "url": "https:\/\/blog.it-premium.com.ua\/all\/ustanovka-centos-mysql-varnish-nginx-php-fpm\/",
            "title": "Установка CentOS + MySQL + Varnish + Nginx + PHP-FPM",
            "content_html": "<p><a href=\"https:\/\/stavrovski.net\/blog\/install-and-configure-nginx-mysql-php-fpm-in-centos-6#set-up-mysql\">https:\/\/stavrovski.net\/blog\/install-and-configure-nginx-mysql-php-fpm-in-centos-6#set-up-mysql<\/a><br \/>\n<a href=\"http:\/\/dev.mysql.com\/doc\/mysql-yum-repo-quick-guide\/en\/\">http:\/\/dev.mysql.com\/doc\/mysql-yum-repo-quick-guide\/en\/<\/a><br \/>\n<a href=\"http:\/\/www.sitepoint.com\/set-automatic-virtual-hosts-nginx-apache\/\">http:\/\/www.sitepoint.com\/set-automatic-virtual-hosts-nginx-apache\/<\/a><\/p>\n<p>Деплой по хуку в гитлабе<br \/>\n<a href=\"https:\/\/github.com\/mauricerenck\/code-samples\/blob\/master\/gitlab-deploy\/deploy.php\">https:\/\/github.com\/mauricerenck\/code-samples\/blob\/master\/gitlab-deploy\/deploy.php<\/a><br \/>\n<a href=\"http:\/\/habrahabr.ru\/post\/246699\/\">http:\/\/habrahabr.ru\/post\/246699\/<\/a><br \/>\n<a href=\"http:\/\/habrahabr.ru\/post\/269163\/\">http:\/\/habrahabr.ru\/post\/269163\/<\/a><\/p>\n",
            "date_published": "2015-11-05T14:18:11+01:00",
            "date_modified": "2015-11-05T14:18:09+01:00",
            "tags": [
                "centos",
                "mysql",
                "nginx",
                "varnish"
            ],
            "_date_published_rfc2822": "Thu, 05 Nov 2015 14:18:11 +0100",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "66",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [],
                "og_images": []
            }
        }
    ],
    "_e2_version": 4134,
    "_e2_ua_string": "Aegea 11.3 (v4134)"
}