0 / 0 / 0
Регистрация: 09.03.2013
Сообщений: 7
|
|
1 | |
Несколько доменов на одном хосте09.03.2013, 21:12. Показов 5834. Ответов 16
Метки нет (Все метки)
Вечер добрый.
Есть 2 домена - site_1 и site_2, есть Ubuntu 12.04.2 LTS и Apache2. Есть настроенные конфиги для этих сайтов: Для site_1 Код
<VirtualHost *:80> ServerName site_1 ServerAlias site_1.ru DocumentRoot /var/www/vhosts/site_1/public SetEnv APPLICATION_ENV "development" <Directory /var/www/vhosts/site_1/public> DirectoryIndex index.php AllowOverride All Order allow,deny Allow from all </Directory> </VirtualHost> Код
<VirtualHost *:80> ServerName site_2 ServerAlias site_2.ru DocumentRoot /var/www/vhosts/site_2 SetEnv APPLICATION_ENV "development" <Directory var/www/vhosts/site_2> DirectoryIndex index.php AllowOverride All Order allow,deny Allow from all </Directory> </VirtualHost> Код
127.0.0.1 localhost site_1 site_1.ru site_2 site_2.ru Код
ServerName site_2 PS Компьютер не мой, до меня его уже настраивали, если нужно - могу скинуть настройки еще какого либо конфига (я в этом очень плохо разбираюсь).
0
|
09.03.2013, 21:12 | |
Ответы с готовыми решениями:
16
Несколько доменов на одном IP Несколько доменов на одном сайте с RewriteRule Несколько доменов на одном внешнем и множество внутренних IP Запуск виртуальных хостов Apache с двумя разными портами на одном хосте. Freebsd |
10.03.2013, 00:40 | 2 |
ruby777, Весь httpd.conf покажите
0
|
0 / 0 / 0
Регистрация: 09.03.2013
Сообщений: 7
|
|
10.03.2013, 00:42 [ТС] | 3 |
Это и был весь httpd.conf
0
|
10.03.2013, 00:44 | 4 |
ruby777, Не может быть
apache2.conf есть?
0
|
0 / 0 / 0
Регистрация: 09.03.2013
Сообщений: 7
|
|
10.03.2013, 00:52 [ТС] | 5 |
Да, есть. Но я там ничего "интересного" так и не нашел.
0
|
10.03.2013, 00:59 | 6 |
ruby777, Покажите весь apache2.conf
0
|
0 / 0 / 0
Регистрация: 09.03.2013
Сообщений: 7
|
|
10.03.2013, 01:02 [ТС] | 7 |
Код
# # Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See http://httpd.apache.org/docs/2.2/ for detailed information about # the directives. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "foo.log" # with ServerRoot set to "/etc/apache2" will be interpreted by the # server as "/etc/apache2/foo.log". # ### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation (available # at <URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # #ServerRoot "/etc/apache2" # # The accept serialization lock file MUST BE STORED ON A LOCAL DISK. # LockFile ${APACHE_LOCK_DIR}/accept.lock # # PidFile: The file in which the server should record its process # identification number when it starts. # This needs to be set in /etc/apache2/envvars # PidFile ${APACHE_PID_FILE} # # Timeout: The number of seconds before receives and sends time out. # Timeout 300 # # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to "Off" to deactivate. # KeepAlive On # # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. # MaxKeepAliveRequests 100 # # KeepAliveTimeout: Number of seconds to wait for the next request from the # same client on the same connection. # KeepAliveTimeout 5 ## ## Server-Pool Size Regulation (MPM specific) ## # prefork MPM # StartServers: number of server processes to start # MinSpareServers: minimum number of server processes which are kept spare # MaxSpareServers: maximum number of server processes which are kept spare # MaxClients: maximum number of server processes allowed to start # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_prefork_module> StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0 </IfModule> # worker MPM # StartServers: initial number of server processes to start # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept spare # ThreadLimit: ThreadsPerChild can be changed to this maximum value during a # graceful restart. ThreadLimit can only be changed by stopping # and starting Apache. # ThreadsPerChild: constant number of worker threads in each server process # MaxClients: maximum number of simultaneous client connections # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_worker_module> StartServers 2 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxClients 150 MaxRequestsPerChild 0 </IfModule> # event MPM # StartServers: initial number of server processes to start # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept spare # ThreadsPerChild: constant number of worker threads in each server process # MaxClients: maximum number of simultaneous client connections # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_event_module> StartServers 2 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxClients 150 MaxRequestsPerChild 0 </IfModule> # These need to be set in /etc/apache2/envvars User ${APACHE_RUN_USER} Group ${APACHE_RUN_GROUP} # # AccessFileName: The name of the file to look for in each directory # for additional configuration directives. See also the AllowOverride # directive. # AccessFileName .htaccess # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <Files ~ "^\.ht"> Order allow,deny Deny from all Satisfy all </Files> # # DefaultType is the default MIME type the server will use for a document # if it cannot otherwise determine one, such as from filename extensions. # If your server contains mostly text or HTML documents, "text/plain" is # a good value. If most of your content is binary, such as applications # or images, you may want to use "application/octet-stream" instead to # keep browsers from trying to display binary files as though they are # text. # # It is also possible to omit any default MIME type and let the # client's browser guess an appropriate action instead. Typically the # browser will decide based on the file's extension then. In cases # where no good assumption can be made, letting the default MIME type # unset is suggested instead of forcing the browser to accept # incorrect metadata. # DefaultType None # # HostnameLookups: Log the names of clients or just their IP addresses # e.g., www.apache.org (on) or 204.62.129.132 (off). # The default is off because it'd be overall better for the net if people # had to knowingly turn this feature on, since enabling it means that # each client request will result in AT LEAST one lookup request to the # nameserver. # HostnameLookups Off # ErrorLog: The location of the error log file. # If you do not specify an ErrorLog directive within a <VirtualHost> # container, error messages relating to that virtual host will be # logged here. If you *do* define an error logfile for a <VirtualHost> # container, that host's errors will be logged there and not here. # ErrorLog ${APACHE_LOG_DIR}/error.log # # LogLevel: Control the number of messages logged to the error_log. # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. # LogLevel warn # Include module configuration: Include mods-enabled/*.load Include mods-enabled/*.conf # Include all the user configurations: Include httpd.conf # Include ports listing Include ports.conf # # The following directives define some format nicknames for use with # a CustomLog directive (see below). # If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i # LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" %>s %O" common LogFormat "%{Referer}i -> %U" referer LogFormat "%{User-agent}i" agent # Include of directories ignores editors' and dpkg's backup files, # see README.Debian for details. # Include generic snippets of statements Include conf.d/ # Include the virtual host configurations: Include sites-enabled/
0
|
10.03.2013, 01:44 | 8 |
0
|
0 / 0 / 0
Регистрация: 09.03.2013
Сообщений: 7
|
|
10.03.2013, 08:46 [ТС] | 9 |
Там только 2 файла (отображение скрытых файлов включил). Первый - site_1, второй - site_2. Содержимое обоих полностью совпадает с первым сообщением.
0
|
10.03.2013, 14:58 | 10 |
ruby777, Наверно хост по умолчанию выбирается тот который первый определён, а первый определён у вас site_1, вот он у вас по localhost и открывается!
1
|
336 / 319 / 18
Регистрация: 25.10.2012
Сообщений: 1,070
|
|
10.03.2013, 15:47 | 11 |
1
|
10.03.2013, 16:32 | 12 |
svsw, Там _default_ не было...
0
|
0 / 0 / 0
Регистрация: 09.03.2013
Сообщений: 7
|
|
10.03.2013, 16:49 [ТС] | 13 |
0
|
336 / 319 / 18
Регистрация: 25.10.2012
Сообщений: 1,070
|
|
10.03.2013, 17:07 | 14 |
ruby777, дефолтным будет считаться объявленный первым
0
|
10.03.2013, 18:36 | 15 |
0
|
336 / 319 / 18
Регистрация: 25.10.2012
Сообщений: 1,070
|
|
10.03.2013, 19:14 | 16 |
имхо виртуальные хосты объявляются в порядке чтения конф-файлов. первый считанный и будет первым
0
|
0 / 0 / 0
Регистрация: 31.08.2013
Сообщений: 6
|
|
12.03.2014, 22:13 | 17 |
0
|
12.03.2014, 22:13 | |
12.03.2014, 22:13 | |
Помогаю со студенческими работами здесь
17
504 ошибка на одном из 3 доменов Несколько доменов на одном IP Несколько доменов в одном сайте Сателлиты на одном хосте За 1000 сайтов на одном хосте - расстрел? Картинки на одном хосте, а mySql и скрипты на другом. Искать еще темы с ответами Или воспользуйтесь поиском по форуму: |