Allgemein

16. February 2018

Angular Development Server behind Nginx with Go API

You’re here because you’d like to know the nginx.conf or rather the vhost conf for nginx in order to serve an Angular dev app on your local host.
Angular listens on port 4200 with ng serve.
In my case I have a keycloak-proxy listening on port 8080.
And my api is on /api/v1/ .
My project is called “dating”.
It’s located at ~/WebstormProjects/dating/ .

So let’s make this simple.

server {
    listen 80;
    listen [::]:80;
    server_name dating.dev.luketic;
    root /home/darko/WebstormProjects/dating/src/;
    index index.html;

    error_log /var/log/nginx/dating.error;

    location / {
        proxy_pass http://localhost:4200;
        proxy_read_timeout 30;
        proxy_connect_timeout 30;
        proxy_redirect off;
        proxy_set_header X-Real-IP          $remote_addr;
        proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto  $scheme;
    }

    location /sockjs-node/ {
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        rewrite ^/(.*)$  /$1  break;
        proxy_set_header Host localhost;
        proxy_pass http://localhost:4200/;
    }

    location ~ ^/api/v1/.* {
        proxy_pass http://localhost:8080;
        proxy_read_timeout 30;
        proxy_connect_timeout 30;
        proxy_redirect off;
        proxy_set_header Host               $host;
        proxy_set_header X-Real-IP          $remote_addr;
        proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto  $scheme;
    }
}

server {

listen 80;

listen [::]:80;

server_name dating.dev.luketic;

root /home/darko/WebstormProjects/dating/src/;

index index.html;

error_log /var/log/nginx/dating.error;

location / {

proxy_pass http://localhost:4200;

proxy_read_timeout 30;

proxy_connect_timeout 30;

proxy_redirect off;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_set_header X-Forwarded-Proto $scheme;

}

location /sockjs-node/ {

proxy_http_version 1.1;

proxy_set_header Upgrade $http_upgrade;

proxy_set_header Connection "upgrade";

rewrite ^/(.*)$ /$1 break;

proxy_set_header Host localhost;

proxy_pass http://localhost:4200/;

}

location ~ ^/api/v1/.* {

proxy_pass http://localhost:8080;

proxy_read_timeout 30;

proxy_connect_timeout 30;

proxy_redirect off;

proxy_set_header Host $host;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_set_header X-Forwarded-Proto $scheme;

}

So again this is for the DEVELOPMENT server. Production has different settings.

13. February 2018

keycloak: upstream sent too big header while reading response header from upstream

The relevant bits on how to solve this header too big error message

                proxy_buffer_size 64k;
                proxy_buffers 8 64k;
                proxy_busy_buffers_size 64k;

proxy_buffer_size 64k;

proxy_buffers 8 64k;

proxy_busy_buffers_size 64k;

For a whole keycloak listening on default port 8080 example with letsencrypt see below

server {
        listen 80;
        listen [::]:80;
        server_name my.serv.er.name;
        include /etc/nginx/acme.conf;
        location / {
                return 301 https://$host$request_uri;
        }
}


server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
        server_name my.serv.er.name;
        ssl_certificate /etc/letsencrypt/live/my.serv.er.name/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/my.serv.er.name/privkey.pem;
        access_log /var/log/nginx/my.serv.er.name.access.log;
        error_log /var/log/nginx/my.serv.er.name.error.log;

        location / {
                proxy_pass http://127.0.0.1:8080;
                proxy_set_header Host               $host;
                proxy_set_header X-Real-IP          $remote_addr;
                proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto  $scheme;
                proxy_buffer_size 64k;
                proxy_buffers 8 64k;
                proxy_busy_buffers_size 64k;
        }

}

server {

listen 80;

listen [::]:80;

server_name my.serv.er.name;

include /etc/nginx/acme.conf;

location / {

return 301 https://$host$request_uri;

}

server {

listen 443 ssl http2;

listen [::]:443 ssl http2;

server_name my.serv.er.name;

ssl_certificate /etc/letsencrypt/live/my.serv.er.name/fullchain.pem;

ssl_certificate_key /etc/letsencrypt/live/my.serv.er.name/privkey.pem;

access_log /var/log/nginx/my.serv.er.name.access.log;

error_log /var/log/nginx/my.serv.er.name.error.log;

location / {

proxy_pass http://127.0.0.1:8080;

proxy_set_header Host $host;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_set_header X-Forwarded-Proto $scheme;

proxy_buffer_size 64k;

proxy_buffers 8 64k;

proxy_busy_buffers_size 64k;

}

9. February 2018

Create MySQL Database and User – the proper way

I read so much bullshit about how to create a mysql user and database, in most cases it’s not just inefficient but also wrong.

So here is the best and most efficient way to create a MySQL database and user with password:

CREATE DATABASE mydatabase;
GRANT ALL ON mydatabase.* TO 'myuser'@'localhost' IDENTIFIED BY 'mypassword';

1 2	CREATE DATABASE mydatabase; GRANT ALL ON mydatabase.* TO 'myuser'@'localhost' IDENTIFIED BY 'mypassword';

Done.

No FLUSH PRIVILEGES.
No create user, then database then give user access then update password.
Just those 2 lines. Nothing more.

17. January 20181. February 2018

Youtube is going DOWN

Today I received an email from Youtube

[Channel Name],
Today we are announcing changes to the YouTube Partner Program (YPP). While our goal remains to keep the YPP open to as many channels as possible, we recognize we need more safeguards in place to protect creator revenue across the YouTube ecosystem.

What’s Changing
Under the new eligibility requirements announced today, your YouTube channel, [Channel Name], is no longer eligible for monetization because it doesn’t meet the new threshold of 4,000 hours of watchtime within the past 12 months and 1,000 subscribers. As a result, your channel will lose access to all monetization tools and features associated with the YouTube Partner Program on February 20, 2018 unless you surpass this threshold in the next 30 days. Accordingly, this email serves as 30 days notice that your YouTube Partner Program terms are terminated.
One of YouTube’s core values is to provide anyone the opportunity to earn money from a thriving channel. Creators who haven’t yet reached this new threshold can continue to benefit from our Creator Academy, our Help Center, and all the resources on the Creator Site to grow their channels. Once your channel reaches the new threshold, it will be reviewed to make sure it adheres to our policies and guidelines, and if so, monetization will be re-enabled.

The main reason to upload to Youtube was monetization. Google, or rather Alphabet is turning more evil each day.
So now you need 4000 hours over 12 months watched and 1000 subscribers.
Yeah “down with the little folk” Alphabet is now part of the mob the ruling elite.
They do whatever they want and fuck the little guy who made them what they are.
Disgusting evil bastards.

I vouch for “Don’t support Alphabet, don’t give them your material for free. Delete your videos if they’re not being monetized and show Alphabet/Youtube who’s boss. It’s not them, it’s you”

2 days later Google has removed any news about this incident from their news search. “If people believe that no one knows about it, nothing will happen, right?”

What happend to “being inclusive”? Don’t they have that lawsuit on their hand because some white guy got mobbed because he’s white? And now this?

5. January 2018

Hetzner Xeon 1245v2 MegaRAID Gentoo Kernel v4.14.11

This is a kernel config for Intel Xeon 1245v2 with LSI MegaRAID Controllers
The particular version of this Kernel config is for Linux kernel 4.14.11

kernel-4.14.11-config

It is certainly optimizable, but works for me TM.