Home directory websites using vhost

Needs / Issues

  • Develop websites located inside home directory;
  • No need for special (root/web server) privileges to develop sites;
  • Websites are referenced with DNS, not aliases.

Audience

  • Administrator / Power user;
  • Developer user.

Initial Setting

  • Apache 2.2 (or newer).

Steps

  • In a shell session (as user):
    Apache logo
    1. Create your "root" directory
      mkdir ~/public_html
      This is where the site will be hosted.
       
    2. Make sure the Apache user can access that root directory:
      namei -l ~/public_html
      All directories in the output list should be at least executable by the Apache user.
  • In a shell session (as root):
    1. Enable VHosts in Apache's configuration:
      vi /etc/httpd/conf/httpd.conf
      Uncomment the following line:
      NameVirtualHost *:80
       
    2. Create an Apache configuration file for your website:
      vi /etc/httpd/conf.d/YOUR_WEBSITE.conf
      Have it contain:
      <VirtualHost *:80>   ServerName YOUR_WEBSITE.localhost
        DocumentRoot /home/YOUR_USERNAME/public_html
        <Directory "/home/YOUR_USERNAME/public_html">
          AllowOverride All
          Order Allow,Deny
          Allow from All
        </Directory>
        ErrorLog logs/YOUR_WEBSITE.localhost-error_log
        CustomLog logs/YOUR_WEBSITE.localhost-access_log common
      </VirtualHost>
    3. Restart the web server:
      service httpd restart
       
    4. Add a local DNS entry to your website:
      vi /etc/hosts
      Add the following line:
      127.0.0.1  YOUR_WEBSITE.localhost
  • In your web browser:
    1. Browse to the URL you created:
      http://YOUR_WEBSITE.localhost/
    2. You should be served your new website.

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

Connect to a different port with SQL Server Management Studio

Hình ảnh
Microsoft's SQL Server Management Studio will connect by default to port 1433 and there's nowhere in the connect dialog to specify a different port from the default. To connect using a different port specify the servername, a comma, and then the port number as shown in this post. Connect using a different port using a comma The connection dialog in the SQL Server Management Studio client is shown in the screenshot below. Normally you would just type the server name into field but to specify a different port use a comma then the port number. The example screenshot above shows " 192.168.50.166\SQLSERVER2012 " as the instance name and "port" where the port would be. 192.168.50.166\SQLSERVER2012,1343 Then specify the login credentials, click the connect button, and assuming everything is correct it should then connect to the SQL Server. Setup specific port for SQL Server: Link: http://msdn.microsoft.com/en-us/library/ms177440.aspx
Đọc thêm

Zabbix Agent Over an SSH Tunnel

Today I set up Zabbix monitoring of a bunch of boxes. A couple have public IP addresses – the load-balancers – so they were pretty standard. However, most of them are sitting behind a NAT, so are a little trickier. I played around with Zabbix proxy for a while – whose purpose is to solve this exact problem. In the end though, just to be different/awkward, I opted to set up ssh tunnels and just pass the Zabbix traffic through the load-balancer boxes. The Zabbix agent config was fiddly and took a lot of trial and error to get right, so, maybe this will help someone else. First of all, the ssh tunnels. This is the command I used, but you’ll probably want to set up ssh keys and use autossh or some such thing. This is run on the load-balancer box, as it’s acting as a bridge between the public network and the NAT’ed network. ssh -f user@10.0.0.25 -L0.0.0.0:14050:10.0.0.25:10050 -N Breaking this down: -f : Background the ssh process user@10.0.0.25 : these ...
Đọc thêm

CLEANING UP THE ZABBIX DATABASE

My Zabbix database size increased a lot in the last few months and since my disk was running out space, I decided to clean up the old events from the database. Looking at the database tables, the biggest one was  history_uint , which holds the items history data – over 400 millions of records and over 30 Gb of disk space before the clean up. Since deleting the old records from this table directly would be a very slow process, I decided to create a new table and insert the latest records from the  history_uint  table and then just replace the old table with a new one. Since this is not an offical procedure, use it at your own risk. Environment: Zabbix v2.2 MySql 5.1 – InnoDB with  innodb_file_per_table=ON Step 1 – Stop the Zabbix server Step 2 – Open your favourite MySQL client and create a new table CREATE TABLE  history_uint_new  LIKE  history_uint; Step 3 – Insert the latest records from the  history_uint  table to the...
Đọc thêm