daugaard47's questions

The non-profit I work for is planning to host an online virtual tel-a-thon later this month.

At MAX, we plan to have 1200 people access our landing page at the same time to watch the livestream event.

I'm currently running our website on an AWS Lightsail VPS with the following specs: (See below for detailed specs)

16 GB RAM, 4 vCPUs, 320 GB SSD
Ubuntu | NGINX

Would this be able to handle 1200 users for 3 hours?

The requests users would be making are the following:

1. Accessing the landing page

2. Making online donations

3. Making online sponsorship donations

4. Possibly browsing our site

5. Sitting Idle watching the livestream

I imagine most people will be sitting idle watching the livestream.

The livestream is hosted via YouTube and will be embedded into the landing page.

I used blazemeter.com and ran Two, 50 virtual user tests simultaneously. (100 virtual-users) During the 20 minute test my server CPU reached 77.65% and was in the burstable zone. The test had the users making many requests, not just sitting ideal.

Curious if I should upgrade my server, or if I'm just being paranoid.

Are there any commands I can run in my servers terminal to simulate this situation. I'm clueless when it comes to servers other than how to spin one up and launch a website on it.

Any advice would be appreciated.

Site Specs:

• Laravel - PHP
• Vue - JS
• MySql

Detailed Specs:

Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               79
Model name:          Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
Stepping:            1
CPU MHz:             2300.105
BogoMIPS:            4600.10
Hypervisor vendor:   Xen
Virtualization type: full
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            46080K
NUMA node0 CPU(s):   0-3
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx
fxsr sse sse2 ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single pti fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt

I'm setting up a new server on AWS Lightsail and all is good, but in my LEMP stack, I installed MySql and created my DB. For some reason though I cannot remote into that DB via my DB client (using TablePlus).

In the past using Vultr or Digital Ocean servers I had to add the IP address to the etc/mysql/mysql.conf.d/mysqld.cnf file, like this:

# bind-address = 127.0.0.1
  bind-address = 34.xxx.xxx.xxx

This would allow me to login with my DB username and pass that I created.

Does AWS Lightsail not allow for this? They have a Create DB Instance service that they want you to buy, but trying to stay cheap on this and only need the DB I built in my server.

Any help on how to connect remotely with a DB client would be extremely appreciative.

Using Ubuntu 18.04 LTS

I have my production site set up and now I'm trying to setup a dev/staging site to run live tests in.

I'm having issues pointing my subdomain to the correct root path on my Laravel app.

I need the following:

• dev.example.com to point to root /var/www/dev/public;
• example.com and www.example.com to point to root /var/www/laravel/public;
• currently everything is going to /var/www/laravel/public

Server:

• Ubuntu 18.10 x64
• Nginx

I have a domain example.com and I made a subdomain called dev.example.com each reference to the domain is in my SSL Cert via certbot/LetsEncrypt. www.example.com, example.com and dev.example.com

DNS for Subdomain:

A (Record) | dev (Name) | 140.xx.xx.xx (Data)

I have 2 folders located here:

• /var/www/laravel/public (My Main Production site)
• /var/www/dev/public (My Development Site)

In sites-available /etc/nginx/sites-available I have the default file with the following configurations.

(I've tried multiple variation of this, but this is where I left off)

 server {

    root /var/www/laravel/public;

    index index.php index.html index.htm index.nginx-debian.html;

    server_name example.com www.example.com dev.example.com;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
        client_max_body_size 200M;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
    }

    location ~ /\.ht {
        deny all;
    }

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}

# Virtual Host configuration for example.com

server {

    if ($host = dev.example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80;
    listen [::]:80;
    server_name dev.example.com;
    root /var/www/dev/public;
    return 404; # managed by Certbot

}

server {

    if ($host = www.example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80;
    listen [::]:80;
    server_name www.example.com;
    return 404; # managed by Certbot

}

server {

    if ($host = example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80 default_server;
    listen [::]:80;
    server_name example.com;
    return 404; # managed by Certbot

}

Again...

• I need dev.example.com to point to root /var/www/dev/public;

• I need example.com and www.example.com to point to root /var/www/laravel/public;

Any help in figuring this out would be appreciated.