1. Download latest API reference as JSON file from desired platform
2. Convert it to yaml for easier modificatoin and convert it back to json file
3. Download Swagger UI https://github.com/swagger-api/swagger-ui/releases
4. Copy the contents of the /dist folder to your server and modify index and js file

The post Generate API Reference documentation appeared first on ubuntu|dog.

• A registered domain name with working HTTPS (TLS/SSL). HTTP/2 only works alongside HTTPS because most browsers, including Firefox and Chrome, don’t support HTTP/2 in cleartext (non-TLS) mode.

• Also you need at least Apache version 2.4.24

• If you run PHP in Apache via mod_php, you need to switch to FPM. That is not a bad thing. FPM is newer and faster.

Now lets do the configuratoin for HTTP/2

Switching Apache’s PHP Module from MPM Prefork to Event
Run the following commands:

sudo apt-get install php7.2-fpm
sudo a2enmod proxy_fcgi
sudo a2enconf php7.2-fpm
sudo a2dismod php7.2
sudo a2dismod mpm_prefork
sudo a2enmod mpm_event
sudo service apache2 restart

Installing and Enabling HTTP/2 in Apache

Enable the module mod_http2:

sudo a2enmod http2
sudo service apache2 restart

Enable the HTTP/2 protocol by adding the following to /etc/apache2/apache2.conf:

Protocols h2 http/1.1

Verify that HTTP/2 is Working

Cloudflare put together a comprehensive list of ways you can check a website for HTTP/2 support. The easiest to use are probably Chrome Dev Tools (network view, add the Protocol column) or the online test from KeyCDN.

The post Enable HTTP/2 in Apache on Ubuntu appeared first on ubuntu|dog.

 sudo mv /etc/vsftpd.conf /etc/vsftpd.conf_orig 
 sudo nano /etc/vsftpd.conf

Now paste below code in vsftpd.conf file:

listen_port=4021

listen=NO

listen_ipv6=YES

anonymous_enable=NO

local_enable=YES

write_enable=YES

local_umask=022

dirmessage_enable=YES

use_localtime=YES

xferlog_enable=YES

connect_from_port_20=YES 

connect_from_port_20=NO

chroot_local_user=YES

secure_chroot_dir=/var/run/vsftpd/empty

pam_service_name=vsftpd

rsa_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem

rsa_private_key_file=/etc/ssl/private/ssl-cert-snakeoil.key

ssl_enable=NO

pasv_enable=Yes

pasv_min_port=10000

pasv_max_port=10100

allow_writeable_chroot=YES

Restart VSFTPD service and it will start to listen on port 4021

service vsftpd restart

Now create sftp group:

groupadd sftp

Modify /etc/ssh/sshd_config file to disable users that are part of sftp group to login by a ssh client.

nano /etc/ssh/sshd_config

Add the following line in the end of the file

Match group sftp
ChrootDirectory /home
X11Forwarding no
AllowTcpForwarding no
ForceCommand internal-sftp

Restart the SSH server

service ssh restart

Now let’s create a user and give it a password

useradd myftpuser

passwd  myftpuser

Change a home folder of your “myftpuser” user:

usermod -d /var/www/myftpuser/www myftpuser

Root must be owner of the path /var/www/myftpuser/:

chown root:root /var/www/myftpuser/

Add user to sftp and www-data group:

usermod  myftpuser -G sftp, www-data

Check groups of your newly created user:

groups  myftpuser  

Groups www-data and sftp should be listed.

Make www-data owner of the web folder there all of your files will be stored:

chown www-data:www-data /var/www/myftpuser/www/ 

Last but not least try to ssh into your myftpuser account. You should not be able to login.

The next step is try login to your FTP but don’t forget to use port: 4021 that we specified above.

Also do not forget to allow port 4021 in your firewall. I use ufw firewall so the following command will allow port 4021:

 ufw allow 4021

The post Chroot VSFTPD user on a webserver and change port of VSFTPD appeared first on ubuntu|dog.

On an Apache server, it’s possible to password protect a directory using .htaccess and .htpasswd files. However, .htaccess files are not supported on Nginx.

You can still password protect your directories, but you need to use a basic_auth.conf file instead.

Creating the file

1. Log into your server via SSH.
2. Navigate to your user’s directory.
3. Make sure you have a /home/username/nginx/example.com directory.This doesn’t exist by default; you must create it by running the following:

   sudo mkdir -p nginx/example.com

4. In this /home/username/nginx/example.com directory, add a file named ‘basic_auth.conf‘ with the following:

   location / {
           auth_basic "Restricted";
           auth_basic_user_file /home/username/nginx/example.com/.htpasswd;
   }

   * The auth_basic parameter is just the title of the prompt the user sees when visiting this directory.
   * The auth_basic_user_file parameter specifies where the password file is. Note how its path is set to the /nginx directory.

   In this example, the ‘location’ directive password protects the entire domain since it’s pointing to ‘/’.
   If you want a subdirectory to be password protected, change the ‘location’ directive as follows:

   location /subdirectory/

5. Run the following to create the .htpasswd file:

   sudo htpasswd -c /home/username/nginx/example.com/.htpasswd LOGIN

   * LOGIN is the username you want to be used to authenticate in the login prompt.

6. After typing that command, enter a password and confirm it when prompted:

   New password: 
   
   Re-type new password:

   Adding password for user LOGIN

7. Reload the nginx config file.

   sudo service nginx reload

8. In your browser, load the directory your /home/username/nginx/example.com/basic_auth.conf points to. *In the example above, this would be your domain’s root directory since the ‘location’ directive points to /.
9. Enter a user/password when prompted to log in.
   * In this example, your username is LOGIN and the password is the one you created above.

See also:

• How to update timezone in Ubuntu
• How to install opcache in Ubuntu

The post Password protect directories / folders with nginx appeared first on ubuntu|dog.

CMS frameworks such as WordPress, Joomla and Drupal, use a complex code and consume many processes. Several website speed enhancement plugins are available, heavily featured within the yield of a typical search engine recommendation. Most of them do not explain how to enable opcode caching server-side – thankfully, it’s simple to implement.

A cursory search for ways to speed up websites will yield plugins and bolt on that only address part of the requirement. The Power Users amongst us need to know how to enable functionality server-side. This short guide will cover off the basics to get you started with OPcache on Ubuntu 18.04 with PHP 7.3 but approach is more or less the same for all Ubuntu versions.

For more detailed runtime options, take a look at the php.net site which has a page of all the runtime options available.

To get OPcache set up requires some changes in the php.ini file on your server.

Open php.ini in your favourite text editor
To get started open your php.ini file. Depending on your configuration, this will be in one of two locations:

APACHE 
sudo nano /etc/php/7.3/apache2/php.ini

Or

NGINX 
sudo nano /etc/php/7.3/fpm/php.ini

Enable OPcache
To enable the OPcache, change to the following lines of your php.ini file:

;opcache.enable=0

Change to:

opcache.enable=1

Note: Remember to uncomment this line and other configuration lines (remove the “;”) as well as change the “0″ to “1″ Otherwise your change won’t take effect.

Modify the amount of RAM the OPcache will use
With OPcache, there is a trade-off between speed and the amount of RAM used. The more RAM you are willing to dedicate to storing opcode, the more opcode that can be stored. There is a diminishing return at some point, because some code will execute rarely, or your code base might not be that big. It is worth playing with this setting to see where you get the best performance-versus-RAM trade-off. This setting is in megabytes.

;opcache.memory_consumption=64

Change to:

opcache.memory_consumption=128

Boost the number of scripts that can be cached
OPcache has a strange setting that requires you to not only adjust the amount of RAM but also define the number of scripts that can be cached. You have the option of tuning this parameter for your own application too, especially if you find that your hit rate is not close to 100 percent.

;opcache.max_accelerated_files=2000

Change to:

opcache.max_accelerated_files=4000

Change the revalidate frequency
To make sure that the OPcache notices when you change your PHP code, you can set the revalidate frequency. Basically, this will tell the cache how often to check the timestamp on the files. This is measured in seconds.

;opcache_revalidate_freq = 2

Change to:

opcache_revalidate_freq = 240

Verify that the PHP OPcache mod is enabled
Believe it or not, that converts most of the settings you will need to get started. PHP7 has its own module system (since 5.4), so make sure that OPcache is enabled.

sudo phpenmod opcache

Restart PHP
You should now be all set to start using PHP 7’s OPcache. You just need to restart the appropriate service to get it going.

APACHE WEB SERVERS

sudo service apache2 restart

NGINX WEB SERVERS

sudo service nginx restart

The post How to install PHP opcache appeared first on ubuntu|dog.

date

Fri Jan 25 02:12:14 UTC 2020
Above we can see the timezone is UTC (Coordinated Universal Time).

UTC is the default time zone. To avoid timezone confusion and the complexities of adjusting clocks for daylight saving time in accordance with regional custom, it is often recommended that all servers use UTC.

If your site or application requires a different system timezone, start by listing the available options:

timedatectl list-timezones
Africa/Abidjan
Africa/Accra
Africa/Addis_Ababa

Now its time to set your time zone. Mine timezone is Europe/Stockholm

sudo timedatectl set-timezone Europe/Stockholm

Now check if the timezone has been set correctly.

date

We can see the timezone has changed to CET, which correct for Stockholm.

The post Update timezone in Ubuntu appeared first on ubuntu|dog.

There is a program that makes those services simple to enable or disable from the start up.

If you need to disable apache2 from start up, type:
sudo update-rc.d apache2 disable

To enable apache2 at start up, type:
sudo update-rc.d apache2 enable

The post Howto disable or enable apache2 autostart on Ubuntu appeared first on ubuntu|dog.

1. Back up phpMyAdmin

You should back up your current phpMyAdmin folder by renaming it.

sudo mv /usr/share/phpmyadmin/ /usr/share/phpmyadmin.bak

Create a new phpMyAdmin folder

sudo mkdir /usr/share/phpmyadmin/

Change to directory

cd /usr/share/phpmyadmin/

2. Download and Extract phpMyAdmin

Visit the phpMyAdmin download page and look for the .tar.gz URL and download it using wget. In this guide we are using version 4.9.1, released Sept 2019. If a later version is now available, make sure to change the commands below to match (and let me know in the comments so I can update the guide 😉).

sudo wget https://files.phpmyadmin.net/phpMyAdmin/4.9.1/phpMyAdmin-4.9.1-all-languages.tar.gz

Now extract

sudo tar xzf phpMyAdmin-4.9.1-all-languages.tar.gz

Once extracted, list folder

ls

You should see a new folder phpMyAdmin-4.9.1-all-languages

We want to move the contents of this folder to /usr/share/phpmyadmin

sudo mv phpMyAdmin-4.9.1-all-languages/* /usr/share/phpmyadmin

You can now log back into phpMyAdmin and check the current version. You may also see two errors:

3. Edit vendor_config.php

If you are seeing an error The $cfg[‘TempDir’] (./tmp/) is not accessible. phpMyAdmin is not able to cache templates and will be slow because of this.

Open vendor_config.php

sudo nano /usr/share/phpmyadmin/libraries/vendor_config.php

Press CTRL + W and search for TEMP_DIR

Change line  to

define('TEMP_DIR', '/var/lib/phpmyadmin/tmp/');

You may also see an error The configuration file now needs a secret passphrase (blowfish_secret). The blowfish secret is used by phpMyAdmin for cookie authentication. 

Press CTRL + W and search for CONFIG_DIR

Change line to

define('CONFIG_DIR', '/etc/phpmyadmin/');

phpMyAdmin will now generate its own blowfish secret based on the install directory.

Save file and exit. (Press CTRL + X, press Y and then press ENTER)

Now log back in to phpMyAdmin and ensure the errors are gone.

4. Cleanup

You can now delete the tar.gz file and the empty folder.

sudo rm /usr/share/phpmyadmin/phpMyAdmin-4.9.1-all-languages.tar.gz

sudo rm -rf /usr/share/phpmyadmin/phpMyAdmin-4.9.1-all-languages

And if you’re certain your new phpMyAdmin install is working correctly you can delete the backup folder.

sudo rm -rf /usr/share/phpmyadmin.bak

Hurrah!

The post How to Manually Upgrade phpMyAdmin appeared first on ubuntu|dog.

Let’s get started.

WARNING

Because PHP 7.3 is not yet officially released, there can be several bugs and other kind of issues since once again its not official yet. I highly recommend you not upgrade your production servers to PHP 7.3 yet.

1. Add ondrej/php PPA

We are going to use PHP PPA by Ondrej. He has published PHP 7.3 on all supported Ubuntu versions.

Commands

sudo add-apt-repository ppa:ondrej/php # Press enter to confirm.
sudo apt-get update

2. Write down current PHP packages

If you are upgrading PHP from an earlier version, it’s important to make sure you ensure you have the same PHP extensions installed. PHP 7.2 onwards no longer include mcrypt extension. Other than that, PHP 7.3 includes all extensions that were in PHP 7.1 and 7.2. dpkg -l | grep php | tee packages.txt Above command will list all packages installed in your system that has php in its name, and write them to a file called packages.txt in your current working directory. You can easily refer this file to install the same PHP 7.3 package counter parts.

3. Install PHP 7.3

Now to the juicy part!

PHP 7.3 core

sudo apt install php7.3 php7.3-common php7.3-cli

This will install PHP 7.3 core extensions and PHP 7.3 CLI.

PHP 7.3 extensions

You can now install the remaining packages as necessary. If you are setting up a new setup, or have no clear idea which packages to install, I highly recommend installing the following packages from the command below. If you are upgrading, look at the packages.txt file to see your current list.

sudo apt-get install php7.3-curl php7.3-gd php7.3-intl php7.3-bcmath php7.3-imap php7.3-json php7.3-mysql php7.3-oauth php7.3-readline php7.3-bz2 php7.3-mbstring php7.3-opcache php7.3-readline php7.3-xml php7.3-zip

PHP 7.3 for web server

With all these packages in place, you might also need to integrate PHP with your web server. If you are using Nginx, or Apache with mod_event, you will need to install php7.3-fpm package. If you are using PHP as an embedded Apache module, you will need libapache2-mod-php7.3 package. For Apache, you can run apachectl -V to see your current MPM, whether its prefork or event.

Nginx and Apache with event MPM

apt install php7.3-fpm

Apache with prefork MPM

apt install libapache2-mod-php7.3

Activate php7.3 Apache module

sudo a2enmod php7.3

Issue update and upgrade command

sudo apt-get update

sudo apt-get upgrade

The post How to upgrade to PHP 7.3 on Ubuntu appeared first on ubuntu|dog.

This is how to do it.

sudo apt-get -y purge ubuntu-desktop
sudo apt-get -y purge unity gnome-shell lightdm
sudo apt-get -y remove ubuntu-desktop
sudo apt purge ubuntu-desktop -y && sudo apt autoremove -y && sudo apt autoclean
sudo apt-get -y clean
sudo apt-get -y autoremove
sudo apt-get -f install

However if you need to install it again just run the following command:

sudo apt-get install ubuntu-desktop

The post How to remove GUI Desktop from Ubuntu 16.04 or 18.04 appeared first on ubuntu|dog.