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.

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.

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.

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.

1. go into /api/ and copy cron.php to some random filename like xfgjkdscron.php

2. now edit xfgjkdscron.php and comment lines:
//if (!osTicket::is_cli())
//die(__(‘cron.php only supports local cron calls – use http -> api/tasks/cron’));

3. Create a cronjob on an external server like this:

A) Issue crontab -e at command line and add below command to it

*/1 * * * * wget -qO- –user-agent=<API KEY FROM osticket here> https://www.example.com/api/xfgjkdscron.php &> /dev/null

The post osTicket – Solve problem with cron.php appeared first on ubuntu|dog.

1. First we need to create a system user

# useradd test
# passwd test

2. Disable SSH access for FTP users
The default user creation script will give a user the /bin/bash shell, which can be a little too powerful. If you don’t want your users logging into your server via SSH, we need to know how to block this access. If you change the shell to /bin/false, the users will only be able to login via ftp or mail if you have that setup. Here is how to modify your users:

usermod -s /sbin/nologin test

3. Now add group www-data to your test user by issuing:

usermod -a -G www-data,test test

Where test is the user you want to modify and www-data and test are the new groups you want that user to join. Running the command without the -a argument will remove that user from all groups except group1 and group2.

You can check /etc/groups file to see the result.

4. Configure vsftpd to be chrooted.

5. Root directory for example /var/www/test/ needs to be owned by root user and group. The rest of the folders and files inside this directory should have www-data:test permissions.

6. Change root directory of your user by modifying /etc/passwd

test:x:1001:1001::/var/www/test:/bin/ftponly

Important: number 1001 above could be different in your case.

Read more: https://www.digitalocean.com/community/tutorials/how-to-set-up-vsftpd-for-a-user-s-directory-on-ubuntu-16-04

The post Chrooted user for VSFTP and Webserver purpose appeared first on ubuntu|dog.

1. Restart network interfaces

$ sudo /etc/init.d/networking restart

2. Restart dhcp

$ sudo /etc/init.d/dhclient

Now your network configuration is applied without restarting the computer.

The post Restart network in Ubuntu from command line appeared first on ubuntu|dog.

1. Boot the linux box using live-cd (any bootable installer for server computers).
2. Choose “rescue a broken system”.
3. Get to the shell and issue the following command:
4. fsck.ext3 /dev/sda1 (or other, depending on your partition)
5. The list of partitions can be displayed using:
6. fdisk -l

The post ext3-fs: error loading journal appeared first on ubuntu|dog.

cd /var/mail/
ls -l

Make sure that file www-data is listed.

Now you can safely remove that file by typing:

rm www-data

The post How to remove all of the mails for a user account on your system appeared first on ubuntu|dog.