Moody Coder - My Daily Base Search | free online Reading portal

Yii2 advanced project template at shared hosting

Try this with .htaccess Method- Step 1 Create .htaccess file in root folder, i.e advanced/.htaccess and write below code. Note : if you are trying in local server then replace ^/ with ^/project_name/ where you see arrow sign. Remove those arrow sign <—— after setup is done. Step 2 Now create […]

Try this with .htaccess Method-

Step 1

Create .htaccess file in root folder, i.e advanced/.htaccess and write below code.

Options +FollowSymlinks
RewriteEngine On

# deal with admin first
RewriteCond %{REQUEST_URI} ^/(admin) <------
RewriteRule ^admin/assets/(.*)$ backend/web/assets/$1 [L]
RewriteRule ^admin/css/(.*)$ backend/web/css/$1 [L]

RewriteCond %{REQUEST_URI} !^/backend/web/(assets|css)/  <------
RewriteCond %{REQUEST_URI} ^/(admin)  <------
RewriteRule ^.*$ backend/web/index.php [L]


RewriteCond %{REQUEST_URI} ^/(assets|css)  <------
RewriteRule ^assets/(.*)$ frontend/web/assets/$1 [L]
RewriteRule ^css/(.*)$ frontend/web/css/$1 [L]
RewriteRule ^js/(.*)$ frontend/web/js/$1 [L] 
RewriteRule ^images/(.*)$ frontend/web/images/$1 [L]

RewriteCond %{REQUEST_URI} !^/(frontend|backend)/web/(assets|css)/  <------
RewriteCond %{REQUEST_URI} !index.php
RewriteCond %{REQUEST_FILENAME} !-f [OR]
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^.*$ frontend/web/index.php

Note : if you are trying in local server then replace ^/ with ^/project_name/ where you see arrow sign. Remove those arrow sign <------ after setup is done.

Step 2

Now create a components/Request.php file in common directory and write below code in this file.

namespace common\components;


class Request extends \yii\web\Request {
    public $web;
    public $adminUrl;

    public function getBaseUrl(){
        return str_replace($this->web, "", parent::getBaseUrl()) . $this->adminUrl;
    }


    /*
        If you don't have this function, the admin site will 404 if you leave off 
        the trailing slash.

        E.g.:

        Wouldn't work:
        site.com/admin

        Would work:
        site.com/admin/

        Using this function, both will work.
    */
    public function resolvePathInfo(){
        if($this->getUrl() === $this->adminUrl){
            return "";
        }else{
            return parent::resolvePathInfo();
        }
    }
}

Step 3

Installing component. Write below code in frontend/config/main.php and backend/config/main.php files respectively.

//frontend, under components array
'request'=>[
    'class' => 'common\components\Request',
    'web'=> '/frontend/web'
],
'urlManager' => [
        'enablePrettyUrl' => true,
        'showScriptName' => false,
],

// backend, under components array
'request'=>[
    'class' => 'common\components\Request',
    'web'=> '/backend/web',
    'adminUrl' => '/admin'
],
'urlManager' => [
        'enablePrettyUrl' => true,
        'showScriptName' => false,
],

Step 4 (Optional, if doesn’t work till step three)

create .htaccess file in web directory

RewriteEngine On 
RewriteCond %{REQUEST_FILENAME} !-f 
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteRule ^(.*)$ /index.php?/$1 [L]

Note: make sure you have enabled your mod rewrite in apache

Thats it! You can try your project with
www.project.com/admin, www.project.com

in local server
localhost/project_name/admin, localhost/project_name

Ref Link

Password Protect MongoDB

mongodb

At the very least you should set a password on your MongoDB deployment. This post will cover how to enable passwords for your MongoDB deployment, create an admin account, and add new accounts for a new database.mongodb Step 1. Create an Admin […]

April 24, 2020

How To Secure Apache Via Let’s Encrypt on Ubuntu 18.04

centos

SSL

vps

Introduction Let’s Encrypt is a Certificate Authority (CA) that provides an easy way to obtain and install free TLS/SSL certificates, thereby enabling encrypted HTTPS on web servers. It simplifies the process by providing a software client, Certbot, that attempts to automate most (if […]

Introduction

Let’s Encrypt is a Certificate Authority (CA) that provides an easy way to obtain and install free TLS/SSL certificates, thereby enabling encrypted HTTPS on web servers. It simplifies the process by providing a software client, Certbot, that attempts to automate most (if not all) of the required steps. Currently, the entire process of obtaining and installing a certificate is fully automated on both Apache and Nginx.

In this tutorial, you will use Certbot to obtain a free SSL certificate for Apache on Ubuntu 18.04 and set up your certificate to renew automatically.

This tutorial will use a separate Apache virtual host file instead of the default configuration file. We recommend creating new Apache virtual host files for each domain because it helps to avoid common mistakes and maintains the default files as a fallback configuration.

Prerequisites

To follow this tutorial, you will need:

One Ubuntu 18.04 server set up by following this initial server setup for Ubuntu 18.04 tutorial, including a sudo non-root user and a firewall.
A fully registered domain name. This tutorial will use your_domain as an example throughout. You can purchase a domain name on Namecheap, get one for free on Freenom, or use the domain registrar of your choice.
Both of the following DNS records set up for your server. You can follow this introduction to DigitalOcean DNS for details on how to add them.
- An A record with your_domain pointing to your server’s public IP address.
- An A record with www.your_domain pointing to your server’s public IP address.
Apache installed by following How To Install Apache on Ubuntu 18.04. Be sure that you have a virtual host file for your domain. This tutorial will use /etc/apache2/sites-available/your_domain.conf as an example.

Step 1 — Installing Certbot

The first step to using Let’s Encrypt to obtain an SSL certificate is to install the Certbot software on your server.

Certbot is in very active development, so the Certbot packages provided by Ubuntu tend to be outdated. However, the Certbot developers maintain a Ubuntu software repository with up-to-date versions, so we’ll use that repository instead.

First, add the repository:

sudo add-apt-repository ppa:certbot/certbot

You’ll need to press ENTER to accept.

Install Certbot’s Apache package with apt:

sudo apt install python-certbot-apache

Certbot is now ready to use, but in order for it to configure SSL for Apache, we need to verify some of Apache’s configuration.

Step 2 — Set Up the SSL Certificate

Certbot needs to be able to find the correct virtual host in your Apache configuration for it to automatically configure SSL. Specifically, it does this by looking for a ServerName directive that matches the domain you request a certificate for.

If you followed the virtual host set up a step in the Apache installation tutorial, you should have a VirtualHost block for your domain at /etc/apache2/sites-available/your_domain.com.conf with the ServerName directive already set appropriately.

To check, open the virtual host file for your domain using nano or your favorite text editor:

sudo nano /etc/apache2/sites-available/your_domain.conf

Find the existing ServerName line. It should look like this:/etc/apache2/sites-available/your_domain.conf

...
ServerName your_domain;
...

If it does, exit your editor and move on to the next step.

If it doesn’t, update it to match. Then save the file, quit your editor, and verify the syntax of your configuration edits:

sudo apache2ctl configtest

If you get an error, reopen the virtual host file and check for any typos or missing characters. Once your configuration file’s syntax is correct, reload Apache to load the new configuration:

sudo systemctl reload apache2

Certbot can now find the correct VirtualHost block and update it.

Next, let’s update the firewall to allow HTTPS traffic.

Step 3 — Allowing HTTPS Through the Firewall

If you have the ufw firewall enabled, as recommended by the prerequisite guides, you’ll need to adjust the settings to allow for HTTPS traffic. Luckily, Apache registers a few profiles with ufw upon installation.

You can see the current setting by typing:

sudo ufw status

It will probably look like this, meaning that only HTTP traffic is allowed to the web server:

OutputStatus: active

To                         Action      From
--                         ------      ----
OpenSSH                    ALLOW       Anywhere                  
Apache                     ALLOW       Anywhere                  
OpenSSH (v6)               ALLOW       Anywhere (v6)             
Apache (v6)                ALLOW       Anywhere (v6)

To additionally let in HTTPS traffic, allow the Apache Full profile and delete the redundant Apache profile allowance:

sudo ufw allow 'Apache Full'
sudo ufw delete allow 'Apache'

Your status should now look like this:

sudo ufw status

OutputStatus: active

To                         Action      From
--                         ------      ----
OpenSSH                    ALLOW       Anywhere                  
Apache Full                ALLOW       Anywhere                  
OpenSSH (v6)               ALLOW       Anywhere (v6)             
Apache Full (v6)           ALLOW       Anywhere (v6)

Next, let’s run Certbot and fetch our certificates.

Step 4 — Obtaining an SSL Certificate

Certbot provides a variety of ways to obtain SSL certificates through plugins. The Apache plugin will take care of reconfiguring Apache and reloading the config whenever necessary. To use this plugin, type the following:

sudo certbot --apache -d your_domain -d www.your_domain

This runs certbot with the --apache plugin, using -d to specify the names you’d like the certificate to be valid for.

If this is your first time running certbot, you will be prompted to enter an email address and agree to the terms of service. After doing so, certbot will communicate with the Let’s Encrypt server, then run a challenge to verify that you control the domain you’re requesting a certificate for.

If that’s successful, certbot will ask how you’d like to configure your HTTPS settings:

OutputPlease choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
-------------------------------------------------------------------------------
1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you're confident your site works on HTTPS. You can undo this
change by editing your web server's configuration.
-------------------------------------------------------------------------------
Select the appropriate number [1-2] then [enter] (press 'c' to cancel):

Select your choice then hit ENTER. The configuration will be updated, and Apache will reload to pick up the new settings. certbot will wrap up with a message telling you the process was successful and where your certificates are stored:

OutputIMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/your_domain/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/your_domain/privkey.pem
   Your cert will expire on 2018-07-23. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot again
   with the "certonly" option. To non-interactively renew *all* of
   your certificates, run "certbot renew"
 - Your account credentials have been saved in your Certbot
   configuration directory at /etc/letsencrypt. You should make a
   secure backup of this folder now. This configuration directory will
   also contain certificates and private keys obtained by Certbot so
   making regular backups of this folder is ideal.
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

Your certificates are downloaded, installed, and loaded. Try reloading your website using https:// and notice your browser’s security indicator. It should indicate that the site is properly secured, usually with a green lock icon. If you test your server using the SSL Labs Server Test, it will get an A grade.

Let’s finish by testing the renewal process.

Step 5 — Verifying Certbot Auto-Renewal

Let’s Encrypt’s certificates are only valid for ninety days. This is to encourage users to automate their certificate renewal process. The certbot package we installed takes care of this for us by adding a renew script to /etc/cron.d. This script runs twice a day and will automatically renew any certificate that’s within thirty days of expiration.

To test the renewal process, you can do a dry run with certbot:

sudo certbot renew --dry-run

If you see no errors, you’re all set. When necessary, Certbot will renew your certificates and reload Apache to pick up the changes. If the automated renewal process ever fails, Let’s Encrypt will send a message to the email you specified, warning you when your certificate is about to expire.

Conclusion

Apache virtual hosts on Ubuntu

Ubuntu

virtual host

Define custom virtual hosts Now you are ready to add your own virtual hosts so that you can start to serve your domains. Create the vhost file for domain1: The contents look as follows: Enable the site Enable the site as follows: […]

Define custom virtual hosts

Now you are ready to add your own virtual hosts so that you can start to serve your domains.

Create the vhost file for domain1:

sudo nano /etc/apache2/sites-available/domain1.com.conf

The contents look as follows:

# Place any notes or comments you have here
# It will make any customisation easier to understand in the weeks to come

# domain: domain1.com
# public: /home/demo/public_html/domain1.com/

<VirtualHost *:80>

  # Admin email, Server Name (domain name) and any aliases
  ServerAdmin [email protected]
  ServerName  domain1.com
  ServerAlias www.domain1.com


  # Index file and Document Root (where the public files are located)
  DirectoryIndex index.html
  DocumentRoot /home/demo/public_html/domain1.com/public


  # Custom log file locations
  LogLevel warn
  ErrorLog /var/log/apache2/error-mydomainname.com.log
  CustomLog /var/log/apache2/access-mydomainname.com.log combined

</VirtualHost>

Enable the site

Enable the site as follows:

sudo a2ensite domain1.com

The output of the command is as follows:

Site domain1.com installed; run /etc/init.d/apache2 reload to enable.

Run the recommended command:

sudo /etc/init.d/apache2 reload

Navigate to the site

To test the domain without creating a DNS zone and records on some Internet name servers, you can modify the ‘/etc/hosts’ file on your local computer to include some entries mapping ‘domain1.com’, ‘domain2.com’, and the rest to the demo Cloud Server’s public IP address:

127.0.0.1    localhost
...

# entries related to the demo Cloud Server
123.45.67.890   domain1.com
123.45.67.890   www.domain1.com
123.45.67.890   domain2.com
...

The location of the ‘hosts’ file varies depending on what OS is loaded on your local computer.

Note: Entries in the ‘hosts’ file must be removed prior to testing and using live DNS zones and records created on Internet name servers. Failure to remove them might lead to confusion on your part and inaccurate tests of new or modified public DNS records.

With such changes made for testing purposes, you can navigate to your site in a web browser on your local computer and the contents of the public/index.html file are shown.

Use the ServerAlias

Note that in the vhost file, you set a ServerAlias. If you have the DNS set up correctly, you can also use that address.

We’ll talk about forcing one address or the other in a later article about rewrite rules.

Repeat the process for the other domain

To create and enable domain2.com, repeat the process as follows:

Create the vhost file:sudo nano /etc/apache2/sites-available/domain2.com ... # Enter the details for domain2.com as per the example shown above
Enable the site and restart Apache:sudo a2ensite domain2.com ... sudo /etc/init.d/apache2 reload
Navigate to the second domain:http://domain2.com or http://www.domain2.com

You should see the ‘domain2.com’ index file.

View log files

As defined in the vhosts file, each domain has its own log files.

List the logs for your domains:

ls /var/log/apache2/error-mydomainname.com.log

The output is exactly as expected:

access.log  error.log

Default vhost file

Although you changed the default virtual host, you did leave it in place.

If someone enters the IP address of the cloud server, they are served the contents of that default vhosts file (if you did not set up a separate vhost for the IP address).

Why are they served from that vhost file?

Apache searches the enabled vhost files in alphabetical order and if it can’t find one for the requested IP address or domain name, it serves the first one (alphabetically).

If you had disabled or deleted the default vhost file, then the contents of domain1.com would be displayed (being before domain2.com alphabetically).

This is something to consider when planning your websites. Do you want a particular domain to be the default? Do you want the IP address to have completely different content?

Set the admin email address

Set the email address for the server administrator. This address is used if you set up the server to contact you when errors occur. It is also shown in the ServerSignature if its value is set to Email. (See the section Define Apache footers.

ServerAdmin [email protected]

Set the domain name

Set the domain name (ServerName) for the virtual host. You can have as many aliases (ServerAlias) as required. For example, you can have domain.com and domain.net point to the same content.

ServerName domain.com
ServerAlias www.domain.com

Note: This is not a rewrite rule, but the domains defined here will serve the same content (assuming you have set the DNS to point to your Cloud Server IP).

Define the index file

Define the index file (the home page that is shown when the domain address is entered). This is useful if you have wanted the user to be directed to an alternate page or to a nonstandard home page.

DirectoryIndex index.html

Note: This is not a good method for redirecting users because they might go directly to a nonspecified page, such as domain.com/index.php, while the DirectoryIndex value works only for those entering domain.com.

Define the path of a documents

Define the location of the domain’s public files. Use an absolute pathname.

DocumentRoot /home/demo/public_html/domain.com/public

Set the log files

Set the log levels and the location for the virtual hosts’ log files.

LogLevel warn
ErrorLog  /var/log/apache2/error-mydomainname.com.log
CustomLog /var/log/apache2/access-mydomainname.com.log combined

Define error documents

Set the ErrorDocument, which is used for all the standard error messages.

ErrorDocument 404 /errors/404.html
ErrorDocument 403 /errors/403.html

In this example, there is an ‘errors’ folder in the public directory. Each error document was created and placed in the errors folder. The paths shown are relative to the DocumentRoot folder defined previously.

If error messages are not defined, Apache generates its own error pages. Custom error pages are more user-friendly and can be customized as much, or as little, as you want.

Define Apache footers

Define ServerSignature to specify whether the server details are displayed in any server-generated error pages or index lists. Options are On, Off, and Email.

ServerSignature On

The level of detail in the signature is configured via ServerTokens, which cannot be set in the Virtual Hosts file. For Ubuntu’s Apache layout, this is properly set in ‘/etc/apache2/conf.d/security’. See the Apache configuration #2 NEED LINK article for more details.

If ServerSignature is set to Email, the ServerAdmin email will be displayed.

Enable CGI-bin

Enable the CGI-bin location as defined by the custom virtual hosts layout. You can leave CGI-bin in the DocumentRoot location if you so want.

ScriptAlias /cgi-bin/ /home/demo/public_html/domain.com/cgi-bin/
<Location /cgi-bin>
  Options +ExecCGI
</Location>

Set directory options

Set the options for the specified directory. The following example enables the FollowSymLinks option for the public directory of domain.com.

  Options FollowSymLinks

Following are other options that you can set:

Directory browsing option

To turn off directory browsing, use -Indexes. To turn on directory browsing, use +Indexes.

Options -Indexes

SSI option

Enable or disable Server Side Includes. The following example disables it.

Options -Includes

Symlinks option

Enable or disable the option to follow symlinks. Be careful with this option because it can lead to security risks (inadvertently linking to configuration folders).

Options -FollowSymLinks

You can consider using the SymLinksIfOwnerMatch directive instead of FollowSymLinks. The SymLinksIfOwnerMatch directive allows symbolic links to be followed only if the owner of the link is identical to the owner of the target file or directory (in terms of Linux file system ownership/permissions). This prevents many of the security risks that a simple FollowSymlinks directive can create.

.htaccess option

Set AllowOverride to None to disable .htaccess support. Set it to All to allow support.

AllowOverride None

You can also specify which .htaccess features to enable, such as:

AllowOverride AuthConfig Indexes

The Apache htaccess and AllowOverride docs have more information about the different features.

Remember to specifically protect your .htaccess file. You can do this by renaming it to something obscure and denying access to the file from external sources:

AccessFileName .myobscurefilename
<Files ~ "^\.my">
    <SatisfyAll>
    Require all denied
    </SatisfyAll>
</Files>

Note: The preceding example is formatted for Apache 2.4. If using 2.2, replace <SatisfyAll> Require all denied </SatisfyAll> ** with **Order Allow,Deny | Deny from all | Satisfy all.

No Options

Specify None to turn off all the available options.

Options None

Options hierarchy

The options directives can be set per-directory, as shown in the following example:

  AllowOverride None
  Options None

AllowOverride All

The first directory setting would turn off all options and disable .htaccess support for all directories.

However, the second directory setting would override the first and allow .htaccess support for the domain.com/public directory.

How to Secure Apache With Let’s Encrypt on Ubuntu 18.04 & Ubuntu 16.04 LTS

Linux

Ubuntu

Let’s Encrypt is a certificate authority (CA) providing free SSL/TLS certificates for enhanced security freely. You can generate CA-singed SSL certificate for any domain, subdomain without any cost and use on your server. It also provides an option to auto-renew SSL certificates […]

September 21, 2019

Tagged Apache2, lets encrypt, tls, Ubuntu

How to Setup Let’s Encrypt SSL on Ubuntu 18.04

Linux

Wordpress

Let’s Encrypt is a certificate authority (CA) providing free SSL/TLS certificates. You can get a valid SSL certificate for your domain at no cost. These certificates can be used for production use as well. The certificates can only be requested from there […]

Tagged lets encrypt, SecurityApache2, SSL, tls

Ionic cache service

Cache

Ionic 2

Ionic cache service Ionic cache service that can cache almost everything. It caches requests, observables, promises, and classic data. It uses Ionic Storage so we support IndexedDB, SQLite (Cordova), WebSQL in this order. It can be used separately in Angular 2 application.

June 18, 2019

Full List of Meta Tags for html

HTML

Basic HTML Meta Tags <meta name=”keywords” content=”your, tags”/> <meta name=”description” content=”150 words”/> <meta name=”subject” content=”your website’s subject”> <meta name=”copyright”content=”company name”> <meta name=”language” content=”ES”> <meta name=”robots” content=”index,follow” /> <meta name=”revised” content=”Sunday, July 18th, 2010, 5:15 pm” /> <meta name=”abstract” content=””> <meta name=”topic” content=””> […]

June 28, 2018

Tagged html, Meta tags, SEO

Promises and Observables in angular 2

Observables are grabbing the spotlight as one of the cool new things Angular 2 is doing, despite having been around for some time. They are positioned to fully eclipse promises as the goto abstraction for dealing with async, among other things. Letâ€™s […]

February 7, 2017

Tagged Observables, Promises

Ask About Required Token in Github

composer

github

Creating a token In the upper-right corner of any page, click your profile photo, then click Settings. In the user settings sidebar, click Personal access tokens. Click Generate new token. Give your token a descriptive name. Select the scopes you wish to […]

February 3, 2017

Tagged composer, github