When I run Composer update in my project then I got this error.

[ErrorException]
  file_put_contents(./composer.lock): failed to open stream: Permission denied

Solution

It can be resolved with the following command:

sudo chown -R $USER ~/.composer/

That’s all.

I hope this article helps you to fix your issue.

Thanks for reading.

Keep Exploring.

I’m getting this error after migrating my laravel project to linux server, see error below

UnexpectedValueException: The stream or file "/opt/lampp/htdocs/testproject/storage/logs/laravel-2021-08-31.log" could not be opened in append mode: failed to open stream: Permission denied in file /opt/lampp/htdocs/testproject/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php on line 110
Stack trace:
  1. UnexpectedValueException->() /opt/lampp/htdocs/testproject/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:110
  2. Monolog\Handler\StreamHandler->write() /opt/lampp/htdocs/testproject/vendor/monolog/monolog/src/Monolog/Handler/RotatingFileHandler.php:120
  3. Monolog\Handler\RotatingFileHandler->write() /opt/lampp/htdocs/testproject/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php:39
  4. Monolog\Handler\AbstractProcessingHandler->handle() /opt/lampp/htdocs/testproject/vendor/monolog/monolog/src/Monolog/Logger.php:344
  5. Monolog\Logger->addRecord() /opt/lampp/htdocs/testproject/vendor/monolog/monolog/src/Monolog/Logger.php:712
  6. Monolog\Logger->error() /opt/lampp/htdocs/testproject/vendor/laravel/framework/src/Illuminate/Log/Logger.php:176
  7. Illuminate\Log\Logger->writeLog() /opt/lampp/htdocs/testproject/vendor/laravel/framework/src/Illuminate/Log/Logger.php:87
  8. Illuminate\Log\Logger->error() /opt/lampp/htdocs/testproject/vendor/laravel/framework/src/Illuminate/Log/LogManager.php:500
  9. Illuminate\Log\LogManager->error() /opt/lampp/htdocs/testproject/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php:118
 10. Illuminate\Foundation\Exceptions\Handler->report() /opt/lampp/htdocs/testproject/app/Exceptions/Handler.php:37
 11. App\Exceptions\Handler->report() /opt/lampp/htdocs/testproject/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:92
 12. Illuminate\Foundation\Bootstrap\HandleExceptions->handleException() [internal]:0

Solution

the error is that, Storage folder doesn’t have permission to write log files, you can run

 chmod -R o+w projectname/storage
 chmod -R o+w projectname/bootstrap

if you are using nginx then you need to use nginx user permission like below

sudo chown -R nginx:root storage
sudo chown -R nginx:root bootstrap

That’s All.

I hope this article helps you to solve the problem.

Thanks for reading.

Keep Exploring.

This simple task is made harder by the fact that Apache is cross-platform software that runs on nearly every server-based operating system.

While you might expect that Apache log files will be stored in different file system locations when running on a Mac or Windows PC, you should note that different Linux distros have their own ideas where to store log data.

Apache also stores data in a number of different logging formats.

The format your Apache installation uses is defined in the Apache configuration file.

• By default, Apache logs data uses the Common Log Format – the Common Log Format defines a label/nickname and associates it.
• Another popular format is the Combined Log Format – this format is based on the Common Log Format, and combines it with the header of the HTTP access request.
• Apache also lets you store log data in many common data formats, such as XML and JSON

2. EXTRACTING DATA FROM APACHE ERROR LOGS AND APACHE ACCESS LOGS

Before exploring how to use log files, we need to discuss the best way to extract data from them.

Apache access and error logs can give us valuable insights into the usage and functioning of an Apache-based website or application.

However, the sheer amount of data that is collected can be overwhelming, and finding important indicators can be a daunting process.

The obvious way to read log file data is using a basic text editor, but many editors may have a hard time dealing with large log files.

• A common approach to reading log files, especially on Linux/Unix based systems, is to take advantage of the operating system’s command line tools, such as GREP and AWK.
• Another approach is to use scripting languages, such as BASH or Powershell to parse log files.

3. Where is the Apache error log?

Depending on your Linux distribution, Apache log file locations may be available in different folders. One point that influences the location of the logs is the type of installation done from Apache. If you did a default installation, follow the log storage location(s).

RHEL / Red Hat / CentOS / Fedora
/var/log/httpd/error_log

Debian / Ubuntu
/var/log/apache2/error.log

FreeBSD
/var/log/httpd-error.log

To find the exact Apache error log file location(s), you can use the grep command:

$ grep ErrorLog /usr/local/etc/apache22/httpd.conf
$ grep ErrorLog /etc/apache2/apache2.conf
$ grep ErrorLog /etc/httpd/conf/httpd.conf

Sample output:

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a
ErrorLog “/var/log/httpd-error.log”

In order to succeed in log reading, you need to know the structure of the log, and where to find it. In the case of Apache running on Linux servers, there are default paths.

The default format of the Apache error log is defined by the ErrorLogFormat directive. It takes this form:

ErrorLogFormat “[%t] [%l] [client %a] %M”
%t is time relative to the server
%l is the level of the message (error, notice, fatal, etc.)
%a is the client IP making the request (if it exists)
%M is the actual error message

An example:

[Sun Jul 09 03:25:02 2017] [notice] Apache/2.2.32 (Unix) DAV/2 configured -- resuming normal operations
[Sun Jul 09 04:06:13 2017] [error] [client 1.2.3.4] File does not exist: /var/www/html/robots.txt
[Mon Jul 10 20:24:52 2017] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:8484 (localhost) failed

4. View Apache error logs

When you have a tool for displaying the data stored in a log, you can quickly find the answers you need. To monitor Apache logs, the easy-to-use Sumo Logic Apache App service is a great choice. You can quickly install the application and configure it to receive the data from your server, and display needed information.

The data that can be monitored are:

• Bytes Delivered
• HTTP Errors
• Page Hits
• Response Time
• Web Server

This data allows you to work safely, and analyze all traffic your application receives.

5. Apache Error Log Analysis

Apache logs contain valuable operational data. Apache error log analysis from Sumo Logic can provide insight and alerts to server errors, request processing, and other diagnostic issues. Analyzing Apache error logs has never been easier, and with Sumo Logic’s built-in error log parser, you can quickly visualize your logs without writing any regex.

SUSE Linux Enterprise ServerNovell Open Enterprise ServerNovell GroupWise

Situation

How to SSLize WebAccess on Linux
How to secure WebAccess using SSLGroupWise WebAccess shows untrusted certificate after pointing to 3rd party certificate using ConsoleOne for WebAccess Agent

Resolution

1. (conditional) If not yet configured, Enable the SSL module and set the Apache Server Flags to SSL:
   • From a terminal window: edit file /etc/sysconfig/apache2
   • Verify ssl is found in the list of APACHE_MODULES.
     Note: If it is not, please run the following command, which should enable the ssl module and add it to this list:
     sudo a2enmod ssl
   • From this same file, please find APACHE_SERVER_FLAGS=”” and add SSL in between the quotations.
   • Create a virtual host for ssl by copying from the template:
     cp /etc/apache2/vhosts.d/vhost-ssl.template /etc/apache2/vhosts.d/vhost-ssl.conf
     
2. Configure Apache to use new certificate files:
   • From a terminal window: cd /etc/apache2/vhosts.d/
   • Edit file vhost-ssl.conf
   • Update paths to the appropriate file(s) as needed:
     • SSLCertificateFile <directory to the cert (*.cert)>
     • SSLCertificateKeyFile <path to the private key (*.key)>
     • SSLCertificateChainFile <path to CA Chain file(s)>
     • SSLCACertificateFile <path to bundles>
   • Save and Close.
   • From a Terminal window: type rcapache2 restart and press Enter.

Additional Information

How to setup Apache using a single PEM file, if so desired.
Replace Step 2 above with the following:

1. See TID 7013103 – How to create a .pem file for SSL Certificate Installations
2. Point Apache to the New PEM:

1. From a terminal window: type cd /etc/apache2/vhosts.d/ and press Enter.
2. Edit file vhost-ssl.conf
3. Find and replace with the path to the same file:
   • SSLCertificateFile <path to the server.pem>
   • SSLCertificateChainFile <path to the server.pem>
4. Comment out any other Certificate configuration (pem created above includes them):
   • SSLCertificateKeyFile
   • SSLCACertificateFile
5. Save and Close.
6. From a Terminal window: type rcapache2 restart and press Enter.

 Access to parts of a site can be restricted
 Require authentication and authorization of the user

 User account information can be kept in several places
 Plain text files
 DBM files
 MySQL database

Here, we’ll restrict access to the “admin” section of our site to the
librarians Jim and Carla Since the number of users is small, we’ll store them in a plain text file

Managing the User Account File

1 Enable headers module

You need to enable headers module to enable CORS in Apache.

Ubuntu/Debian

In ubuntu/debian linux, open terminal & run the following command to enable headers module.

$ sudo a2emod headers

CentOS/Redhat/Fedora

In CentOS/Redhat/Fedora linux, open the Apache configuration file httpd.conf and uncomment the following line by removing # in front of them.

LoadModule headers_module modules/mod_headers.so

2 Enable CORS in Apache

Next, add the “Header add Access-Control-Allow-Origin *” directive to either your Apache config file, or .htaccess file, or Virtual Host configuration file, depending on your requirement. If you add it to your main configuration file, CORS will be enabled to all websites on your server. If you add it to .htaccess file or  virtual host configuration file, then it will be enabled for only that file’s website. Here are examples of how to add this directive in different files. You can use any one of them.

Directory Tag in Main Configuration File

<Directory /var/www/html>
   ...
   Header set Access-Control-Allow-Origin "*"
   ...
</Directory>

Anywhere in .htaccess file

   ...
   Header add Access-Control-Allow-Origin "*"
   ...

VirtualHost Tag in Virtual Host Configuration File

<VirtualHost *:443>
   ...
   Header add Access-Control-Allow-Origin "*"
   ...
</VirtualHost>

Enable CORS from all websites

If you want to enable CORS for all websites, that is, accept cross domain requests from all websites, add the following

Header add Access-Control-Allow-Origin *;

In the above statement, we use wildcard (*) for Apache Access-Control-Allow-Origin directive

Enable  CORS from one domain

If you want to enable CORS for one website domain (e.g example.com), specify that domain in place of wildcard character *.

Header add Access-Control-Allow-Origin "example.com";

Enable CORS from multiple domains

If you want to enable CORS for multiple domains (e.g example1.com, example2.com,example3.com), specify them separately one after another

Header add Access-Control-Allow-Origin "example1.com";
Header add Access-Control-Allow-Origin "example2.com";
Header add Access-Control-Allow-Origin "example3.com";

Enable CORS from localhost

If you want to enable CORS from localhost, add 127.0.0.1 or localhost in place of domain name

Header add Access-Control-Allow-Origin "localhost";

3. Restart Apache Server

Restart Apache web server to apply changes

-------------- On Debian/Ubuntu -------------- 
# apache2 -t
# systemctl restart apache2.service

-------------- On RHEL/CentOS/Fedora --------------
# httpd -t
# systemctl restart httpd.service

“Virtual hosting is a method for hosting multiple domain names (with separate handling of each name) on a single server (or pool of servers).”

How Does Apache Know Which Site to Serve?

The short answer to your specific case: apache will serve the FIRST overlapping virtual host. Since 000-default is before fc.localhost in the alphabet the first virtualhost is loaded and served.

To answer what i assume is the follow up question: You can host many sites on the same IP:PORT using named VirtualHosts

The host field in the http request header identifies which site (virtual
host) to serve:

Matched against the containers in the configuration file

A More Complete Virtual Host Definition

You can put (almost) any directive inside a virtual host container For example, it’s common to write separate logs for each site

Name Resolution

1. In the “real world” our East and West sites would each have an entry in DNS (Domain Name Service)
2. Our demonstration system uses only /etc/hosts for name resolution:

The directory Apache

/usr/lib64/httpd/modules

The httpd package we installed includes the config file:

/etc/httpd/conf/httpd.conf

Listening on a Port

You can restrict apache to listen on a specific network interface

Listen 22.33.44.55:80

Setting the Document Root

The DocumentRoot defines the top-level directory of the web site

Setting an Identity

Apache needs a user identity to run as Used to perform access control checks to the file system

Defining Multi-Process Settings

To improve response times, apache manages a pool of “spare” server
processes
These numbers control the size of the pool:

Containers

Container directives use XML-style opening / closing tags

Restrict the scope of the directives they contain

Apache listens for requests on TCP/IP port 80. You need to uninstall or disable any program that uses that port. If you have a Professional or Server version of Windows, you may already have IIS installed. If you would prefer Apache, either remove IIS as a Windows component or disable its services.

Step 2: Download the files

We’re going to use the unofficial Windows binary from Apache Lounge. This version has performance and stability improvements over the official Apache distribution, although I’m yet to notice a significant difference. However, it’s provided as a manually installable ZIP file from www.apachelounge.com/download/.

You should also download and install the Windows C++ runtime from Microsoft.com. You may have this installed already, but there is no harm installing it again.

Step 3: Extract the Files

We’ll install Apache in C:/Apache24, so extract the ZIP file to the root of the C:/ drive. Apache can be installed anywhere on your system, but you’ll need to change SVROOT configuration to point to your unzipped location — suh as E:/Apache24.

Step 4: Configure Apache

Apache is configured with the text file conf/httpd.conf contained in the Apache folder. Open it with your favorite text editor.

Note that all file path settings use a forward slash (/) rather than the Windows backslash. If you installed Apache anywhere other than C:/Apache24, now is a good time to search and replace all references to C:/Apache24.

There are several lines you should change for your production environment:

Line 60, listen to all requests on port 80:Listen *:80

Line 162, enable mod-rewrite by removing the # (optional, but useful):LoadModule rewrite_module modules/mod_rewrite.so

Line 227, specify the server domain name:ServerName localhost:80

Line 224, allow .htaccess overrides:AllowOverride All

After this test your installation…

Step 5: Test your Installation

Your Apache configuration can now be tested. Open a command box (Start > Run > cmd) and enter:

# navigate to Apache bin directory
cd /Apache24/bin
# Test httpd.conf validity
httpd -t

It should say “Syntax OK”. If not, correct any httpd.conf configuration errors and retest until none appear.

composer create-project --prefer-dist laravel/laravel testingcronjob "5.8.*"

Step 2 :- Now, we need to create a custom command. Custom command will execute with task scheduling cron job. Run the below command to create new custom command

php artisan make:command DemoCron --command=demo:cron

Now we make some changes on Command file.

app/Console/Commands/DemoCron.php

<?php
   
namespace App\Console\Commands;
   
use Illuminate\Console\Command;
   
class DemoCron extends Command
{
    /**
     * The name and signature of the console command.
     *
     * @var string
     */
    protected $signature = 'demo:cron';
    
    /**
     * The console command description.
     *
     * @var string
     */
    protected $description = 'Command description';
    
    /**
     * Create a new command instance.
     *
     * @return void
     */
    public function __construct()
    {
        parent::__construct();
    }
    
    /**
     * Execute the console command.
     *
     * @return mixed
     */
    public function handle()
    {
        \Log::info("Cron is working fine!");
     
        /*
           Write your database logic we bellow:
           Item::create(['name'=>'hello new']);
        */
      
        $this->info('Demo:Cron Cummand Run successfully!');
    }
}

Step 3 :- Now, we need to define our commands on Kernel.php file with time when you want to run your command like as bellow functions:

app/Console/Kernel.php

<?php
   
namespace App\Console;
    
use Illuminate\Console\Scheduling\Schedule;
use Illuminate\Foundation\Console\Kernel as ConsoleKernel;
    
class Kernel extends ConsoleKernel
{
    /**
     * The Artisan commands provided by your application.
     *
     * @var array
     */
    protected $commands = [
        Commands\DemoCron::class,
    ];
     
    /**
     * Define the application's command schedule.
     *
     * @param  \Illuminate\Console\Scheduling\Schedule  $schedule
     * @return void
     */
    protected function schedule(Schedule $schedule)
    {
        $schedule->command('demo:cron')
                 ->everyMinute();
    }
     
    /**
     * Register the commands for the application.
     *
     * @return void
     */
    protected function commands()
    {
        $this->load(__DIR__.'/Commands');
     
        require base_path('routes/console.php');
    }
}

Step 4 :- Now We’re ready to run our cron. You can manually check using following command of your cron.Run bellow command:

php artisan schedule:run

After running above command, now you can check log file where we already print some text. So open your log file it looks like as bellow:

storage/logs/laravel-2021-08-16.php

Now our Cron is Working fine, But we want to run cron at every minute in our Linux Server, So for that folow the below Steps.

========================= NOTE START ==========================

Crontab Date / Time Format

 * * * * *  command to execute
 │ │ │ │ │
 │ │ │ │ │
 │ │ │ │ └───── day of week(0-6)(0 to 6 are Sunday to Saturday, or use names; 7 is Sunday, the same as 0)
 │ │ │ └────────── month (1 - 12)
 │ │ └─────────────── day of month (1 - 31)
 │ └──────────────────── hour (0 - 23)
 └───────────────────────── min (0 - 59)

========================= NOTE END ==========================

Step 5 :- Now login into your server and navigate to /etc and run below command

sudo crontab -e

After running command you’ll get output like below image, just select easiest

In my case it’s 2, so I typed 2 and hit enter.

now add single entry on crontab file

* * * * * php /path/to/artisan schedule:run 1>> /dev/null 2>&1


OR

* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1

I’m running on my linux server so i’ve added path to my artisan file of my laravel project, see below

my code

* * * * * php /opt/lampp/htdocs/testingcronjob/artisan schedule:run 1>> /dev/null 2>&1

It’s Done. I hope this article help you.

Keep Exploring.

Thanks for reading.

So i’m providing a complete list of each folder’s and sub-folder’s permissions.

1. storage – 755.
   
   
2. storage/app – 755.
   storage/app/public – 755.
   
   
3. storage/framework – 755.
   storage/framework/views – 777.
   storage/framework/testing – 755.
   storage/framework/sessions – 777.
   storage/framework/cache – 755.
   
4. storage/logs – 755.

That’s all. Hope this article will solved your problem.

Keep Exploring.

Thanks for reading.

To find public ip address in windows just visit the below website it will show you the ip.

https://www.whatismyip.com

For linux

If you are using terminal and want to find your public ip address, then you have to run the below command in your terminal

wget –O – –q https://checkip.amazonaws.com

curl –s https://icanhazip.com

Step 1 :- first Stop the server from running by below command

sudo /opt/lampp/lampp stop

Step 2 :- Now run below command to uninstall Xampp.

sudo /opt/lampp/uninstall

Step 3 :- Now run the below command to remove Xampp All leftover files.

sudo rm -r /opt/lampp

As you can see in the screenshot, after running the command all files are removed and when xampp is also not starting, it means xampp is successfully uninstalled from our linux machine.

That’s All. I hope this article helps you to uninstall xampp.

Keep Exploring.

Thanks for reading.

Step 1 :- Login to your (Ubuntu) Machine.

Step 2 :- run the below command to download Xampp.

wget https://downloadsapachefriends.global.ssl.fastly.net/7.4.22/xampp-linux-x64-7.4.22-0-installer.run

Step 3 :- Go to root user by entering below command

sudo -s

Step 4 :- Now we give permission to execute to the downloaded xampp file. For that run,

chmod 755 xampp-linux-x64-7.4.22-0-installer.run

Step 5 :- Now, we run the downloaded file for installation, for that run

sudo ./xampp-linux-x64-7.4.22-0-installer.run

Output

root@sushant-VirtualBox:/home/sushant# sudo ./xampp-linux-x64-7.4.22-0-installer.run
----------------------------------------------------------------------------
Welcome to the XAMPP Setup Wizard.

----------------------------------------------------------------------------
Select the components you want to install; clear the components you do not want
to install. Click Next when you are ready to continue.

XAMPP Core Files : Y (Cannot be edited)

XAMPP Developer Files [Y/n] :y

Is the selection above correct? [Y/n]: y

----------------------------------------------------------------------------
Installation Directory

XAMPP will be installed to /opt/lampp
Press [Enter] to continue:

----------------------------------------------------------------------------
Setup is now ready to begin installing XAMPP on your computer.

Do you want to continue? [Y/n]: y

----------------------------------------------------------------------------
Please wait while Setup installs XAMPP on your computer.

 Installing
 0% ______________ 50% ______________ 100%
 #########################################

----------------------------------------------------------------------------
Setup has finished installing XAMPP on your computer.

root@sushant-VirtualBox:/home/sushant#

Step 6 :- Installation Done. Now we want to start server for that run,

sudo /opt/lampp/lampp start

List of commands to start, stop and restart server

To Start Server :- sudo /opt/lampp/lampp start

To Stop Server :- sudo /opt/lampp/lampp stop

To Restart Server :- sudo /opt/lampp/lampp restart

That’s all, I hope this article helps you to solve your problem.

Keep Exploring.

Thanks for reading.

Step 1 :- First locate httpd-xampp.conf file, for Ubuntu it’s located at /opt/lampp/etc/extra/

Step 2 :- open httpd-xampp.conf file for editing. you’ll find something live below code

# New XAMPP security concept
#
<LocationMatch "^/(?i:(?:xampp|security|licenses|phpmyadmin|webalizer|server-status|server-info))">
    Require local
    ErrorDocument 403 /error/XAMPP_FORBIDDEN.html.var
</LocationMatch>

Step 3 :- add Require ip your_ip_address below Require local .

# New XAMPP security concept
#
<LocationMatch "^/(?i:(?:xampp|security|licenses|phpmyadmin|webalizer|server-status|server-info))">
    Require local
    Require ip 10.0.0.1  // provide your static ip here.
    ErrorDocument 403 /error/XAMPP_FORBIDDEN.html.var
</LocationMatch>

Step 4 :- Add your static IP address after Require ip your_static_ip.

It’s Done.

Now Check to access your_ip_address/phpmyadmin

Apache Installation

Apache gives its functionality and the components to individual units which can be customized and configured independently. The basic unit that describes a site or a domain is called a virtual host.

This allows the administrator to use one server to host multiple domains or sites with a single interface or IP address by using a mechanism.

$ sudo apt-get update
$ sudo apt-get install apache2

Create the Directory Structure

A directory structure shall hold the site information and data which will be served to visitors. By default, the top-level directory for apache is /var/www and we will be setting them to the individual directories under the /var/www directory for each site/domain.

$ sudo mkdir -p /var/www/firstSite.com
$ sudo mkdir -p /var/www/secondSite.com

Grant Permissions

Our directory’s owned by our root user. If we want our normal user to be able to modify files in our web directories, then we have to change the ownership to others normal users.

$ sudo chown -R $USER:$USER /var/www/firstSite.com
$ sudo chown -R $USER:$USER /var/www/secondSite.com
$ sudo chmod -R 755 /var/www

Create Demo Pages for for both sites.

To create a file we use touch command, The touch command is a standard command used in UNIX/Linux operating system which is used to create, change and modify timestamps of a file.

$ touch /var/www/webserver1.com/index.html

Then put some lines of html.

<!DOCTYPE html>
<html>
<head>
<title>Site one</title>
</head>
<body>

<h1>Site one heading</h1>
<p>My first paragraph.</p>

</body>
</html>

We’ll copy and past the same page for second server and modify it accordingly

$ cp /var/www/firstSite.com/index.html /var/www/secondSite.com/index.html

$ nano /var/www/webserver2.com/index.html
<html>
   <head>
      <title>Welcome to secondSite.com!</title>
   </head>
   <body>
      <h1>Success!</h1>
   </body>
</html>

Create New Virtual Host Files

$ sudo cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/firstSite.conf
$ sudo nano /etc/apache2/sites-available/firstSite.com.conf

<VirtualHost *:80>
   ServerAdmin admin@firstSite.com
   ServerName firstSite.com
   ServerAlias www.firstSite.com
   DocumentRoot /var/www/firstSite.com/
   ErrorLog ${APACHE_LOG_DIR}/error.log
   CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Copy First Virtual Host file and customize for Second Domain webserver2.com

$ sudo cp /etc/apache2/sites-available/firstSite.com.conf /etc/apache2/sites-available/secondSite.com.conf
$ sudo nano /etc/apache2/sites-available/secondSite.com.conf

Do the same thing for secondSite VH

<VirtualHost *:80>
   ServerAdmin admin@secondSite.com
   ServerName secondSite.com
   ServerAlias www.secondSite.com
   DocumentRoot /var/www/secondSite.com/
   ErrorLog ${APACHE_LOG_DIR}/error.log
   CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Enable the New Virtual Host Files

$ sudo a2ensite webserver1.com.conf
$ sudo a2ensite webserver2.com.conf

We needed to restart Apache server

$ sudo service apache2 restart

Testing the Websites

$ sudo /etc/hosts

192.168.1.84 website1.com
192.168.1.84 website1.com

If you are new to Linux/Unix, then the concept of permissions may be confusing. This guide provides you with an explanation of what permissions are, how they work, and how to manage them. A number of examples are provided to illustrate how to set and change permissions for both users and groups.

What are Linux User and Group Permissions?

Linux/Unix operating systems have the ability to multitask in a manner similar to other operating systems. However, Linux’s major difference from other operating systems is its ability to have multiple users. Linux was designed to allow more than one user to have access to the system at the same time. In order for this multiuser design to work properly, there needs to be a method to protect users from each other. This is where permissions come in to play.

Read, Write, & Execute Permissions

Permissions are the “rights” to act on a file or directory. The basic rights are read, write, and execute.

• Read: a readable permission allows the contents of the file to be viewed. A read permission on a directory allows you to list the contents of a directory.
• Write: a write permission on a file allows you to modify the contents of that file. For a directory, the write permission allows you to edit the contents of a directory (e.g. add/delete files).
• Execute: for a file, the executable permission allows you to run the file and execute a program or script. For a directory, the execute permission allows you to change to a different directory and make it your current working directory. Users usually have a default group, but they may belong to several additional groups.

Viewing File Permissions

To view the permissions on a file or directory, issue the command ls -l <directory/file>. Remember to replace the information in the <directory/file> with the actual file or directory name. Below is sample output for the ls command:

-rw-r--r-- 1 root root 1031 Nov 18 09:22 /etc/passwd

• The first ten characters show the access permissions.
• The first dash (-) indicates the type of file (d for directory, s for special file and - for a regular file).
• The next three characters (rw-) define the owner’s permission to the file.

In this example, the file owner has read and write permissions only. The next three characters (r--) are the permissions for the members of the same group as the file owner (which in this example is read only). The last three characters (r--) show the permissions for all other users and in this example it is read only.

Step :1 Create a folder anywhere in your local computer with any name (Mine is workspace)

Step:2 Make sure git and gitbash is installed in your local machine if not download it from here

Step:3 Login into your GitHub account and create a repository

Step 4: Clone the repository into your local machine

• get inside your repository

• Copy the URL under HTTPS area
• There are many more ways to clone a repo but for time being use this method
• Now get inside our workspace folder that we created before (local/workspace)
• right click and open git bash or command line inside the folder

• Run these git commands to get started

git init 

This is to initialize a new, empty repository 

git clone https://github.com/pradeeprjth/laravelTestingProject.git [HTTPS_URL_YOU_COPYED_FROM_GITHUB] 

This will clone everything stored in your remote repository into your local folder/repository
You will find a folder with the same name you created your repository 

Step :5 paste your project/code inside the folder you just clone from the repository

• Again run the below commands to push all the changes and codes back to the repository
• Right click and open your git bash or cmd inside the folder

git add .

The git add command adds a file to the Git staging area. This area contains a list of all the files you have recently changed.

git commit -m"first_commit"

git commit creates a commit, which is like a snapshot of your repository. These commits are snapshots of your entire repository at specific times. and you need to specify a commit message using -m flag including double quote

git push origin master    or    git push origin main 

git push -u origin master is used for pushing local content to GitHub

Step 6: Login to your remote machine or ubuntu machine and make sure xampp and composer is installed in that machine.

Follow this blog if xampp and composer are not installed in your remote/ubuntu machine

1. Installed Xampp

How to install and Configure XAMPP on Ubuntu?

This blog is written by Rajesh thanks to him.

2. Another thing which is required is Composer

Install composer using CLI in ubuntu (Globally)

Follow this to install composer in your machine using CLI

Stpe :7 Go to your htdocs folder or if you have lampp then www folder and run below commands

git init 

 This is to initialize a new, empty repository but this time inside your remote machine 

git clone https://github.com/pradeeprjth/laravelTestingProject.git [HTTPS_URL_YOU_COPYED_FROM_GITHUB]

Now as we already have pushed all our code into our repository so we'll get all the files folder into our htdocs folder or www folder 

Step 8: Now to run the project we need to do some configuration

• Copy the .env.example file to .env coz git ignore some files and folder including our vendor folder which contains all our Laravel project files . To do this run the below command.

cp .env.example .env

• Install composer, as git ignores our vendor folder in order to get it back we need to run

composer install

• You may get an error while composer install
• Class ‘Illuminate\Support\facades\Schema not found
• In order to solve this go to your project folder in local and inside C:\xampp\htdocs\WrokSpace\laravelTestproject\app\Providers\AppServiceProvider.php
• use this class in the top
  use Illuminate\Support\Facades\Schema;

• Next thing is to set the APP_KEY value in your .env file, run the command below

php artisan key:generate

Step 9: Now go to your browser and put your ip followed by the project name /public to visit the application

http://90.437.1965.252/laravelTestproject/public/

That’s it hope it help’s someone out there.

First permission:

As you know the first thing our browser needs to run a Laravel project is, the index file which is located in the public folder
so we need to make it read and writable so that our browser can access it and if required can modify it.

Run the below command to grant access to the public folder

cd /opt/lampp/htdocs/YOUR_PROJECT
sudo chmod -R +rw public

Second permission:

The next permission if for the storage folder, as you already know when our Laravel projects runs it create some logs files automatically if any error found in you code base,

Run the below command to grant access to the logs folder

cd /opt/lampp/htdocs/YOUR_PROJECT
sudo chmod -R +rw storage

Third permission:

At the end, the final permission we have to give to our session folder which is located inside our storage/framework folder,
and every time we hit our project URL a new random session key is generated, that get stored in our session folder
so all of them are necessary to run a Laravel project

Run the below command to grand access to the framework and session

sudo chmod -R 775 framework
sudo chmod -R 775 session

That’s it, these all works for me hope it for you too

1. Installed Xampp

2. Another thing which is required is Composer

3. Now the thing is when we try to install Laravel project inside our htdocs folder it through an error

4. To resolve this error first create a folder inside your htdocs.

mkdir Projects

5 grant read and write permissions to this folder by running this commands

sude chmod +rw Projects

6. You may get another error while installing is (“mbstring” extension is missing.)

Run the below commands to resolve these errors

sudo apt-get install php-mbstring

sudo su - root

7. That’s it now try installing your project again

composer create-project --prefer-dist laravel/laravel testProject "5.8.*"

That’s it, Hope it help someone out there.

I was trying to install Laravel in a Ubuntu virtual machine and got this error

And To enable extensions, verify that they are enabled in your .ini files:

But in your server you’re missing ext-dom. php-xml has all the related packages you need. So, you can simply install it by running:

sudo apt install php-xml

Most likely you are missing mbstring too. If you get the error, install this package as well with:

sudo apt-get install php-mbstring

Then run:

composer update
composer require cviebrock/eloquent-sluggable