Не могу найти правильный способ использовать разрешения, чтобы позволить Apache+PHP изменять файлы, которые я загрузил и размонтировал

У меня есть VPS, работающий на Amazon AWS EC2 благодаря этой замечательной статье.

Все идеально, за исключением того, что Apache+PHP не могут изменять файлы (создавать журналы и т.д.).

Поэтому я последовал инструкциям, приведенным в Чтобы исправить разрешения на файлы для веб-сервера Apache здесь. .

Все исправлено, теперь приложение PHP, которое я установил, могло создавать файлы.

Однако, если я войду и распакую резервную копию сайта в новую папку виртуального хоста (т.е. в /var/www/html/myNewSite), то, если я не выполню вышеуказанное "исправление", PHP снова не сможет редактировать файлы.

Я проверил, от имени какого пользователя запущен Apache (apache) и сделал его членом группы под названием www.

Папка www выглядит так:

drwxrwsr-x 2 root www 4096 Jan 19 16:56 cgi-bin drwxrwsr-x 3 root www 4096 May 3 16:14 error drwxrwsr-x 6 root www 4096 May 7 14:07 html drwxrwsr-x 3 root www 4096 May 3 16:14 icons drwxrwsr-x 2 root www 4096 May 3 16:14 noindex

Под html папка сайта:

drwxrwsr-x 2 root www 4.0K May 6 11:14 myNewSite

Под myNewSite если я разархивирую файл с помощью:

tar -zxvf mytar.tar.gz -C .

то в итоге я получу файлы следующего вида:

-rwxr-xr-x 1 myUserName www 537 Apr 21 12:27 composer.json -rwxr-xr-x 1 myUserName www 3.5K Apr 21 12:27 CONTRIBUTING.md -rwxr-xr-x 1 myUserName www 12K Apr 21 12:27 htaccess.txt -rwxr-xr-x 1 myUserName www 2.4K Apr 21 12:27 index.php etc Несмотря на то, что я (myUserName) являюсь членом www, тот факт, что я теперь владелец, похоже, убивает способность Apache писать в файлы.

Я пробовал эти причудливые g+w атрибуты и другие вещи, но безрезультатно :/

Морщась, я отправляю это, поскольку я уверен, что плохо объяснил и/или упустил что-то (на самом деле я откладывал вопрос, поскольку не смог придумать, как спросить это кратко, и я бы не винил мода за убийство моего Q; извините заранее, если это слишком слабо, чтобы быть допущенным).

httpd.conf файл:

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See  for detailed information.
# In particular, see 
# 
# for a discussion of each configuration directive.
#
# 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.  
#
# 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 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.    

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"    

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the 
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80    

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
Include conf.modules.d/*.conf    

#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User apache
Group apache    

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
#  definition.  These values also provide defaults for
# any  containers you may define later in the file.
#
# All of these directives may appear inside  containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#    

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin root@localhost    

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80    

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other 
#  blocks below.
#

    AllowOverride none
    Require all denied
    

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#    

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html"    

#
# Relax access to content within /var/www.
#

    AllowOverride None
    # Allow open access:
    Require all granted
    

# Further relax access to the default document root:

    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks    

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride All    

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
    

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#

    DirectoryIndex index.html
    

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#

    Require all denied
    

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a 
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a 
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/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    


    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common    

    
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
        

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a 
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per- access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    #CustomLog "logs/access_log" common    

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    CustomLog "logs/access_log" combined
    


    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar    

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a  section to allow access to
    # the filesystem path.    

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"    

    

#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#

    AllowOverride None
    Options None
    Require all granted
    


    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig /etc/mime.types    

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz    

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi    

    # For type maps (negotiated resources):
    #AddHandler type-map var    

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml
    

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default.  To use the 
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8    


    #
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #
    MIMEMagicFile conf/magic
    

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#    

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on    

# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf    

# Added by AcB 2017-05-03 per https://www.taniarascia.com/ etc AWS
NameVirtualHost *:80    


    ServerName localhost
    DocumentRoot /var/www/html/000
    


  ServerName www.example.com
  ServerAlias example.com *.example.com
  DocumentRoot /var/www/html/example 

Addendum 2017-05-12-12:10 PM EST

Я не понял, как это решить, но я заметил следующее.

На традиционном VPS, управляемом хостинговой компанией (не Amazon VPS), я вхожу под именем theDomainName (т.е. каждый домен/виртуальный хост. т.е. каждый домен/виртуальный хост имеет свое собственное имя входа) и если я ls -l, я вижу, что папка для веб-сайта:

drwxr-xr-x  8 theDomainName theDomainName     4096 May  2 11:25 public_html/

и файлы в ней имеют одинаковые права собственности и группы:

drwxr-xr-x  8 theDomainName theDomainName  4096 May  2 11:25 ./
drwx--x--x 15 theDomainName theDomainName  4096 May 12 12:20 ../
-rwxr-xr-x  1 theDomainName theDomainName   537 Apr 21 08:27 composer.json*
-rwxr-xr-x  1 theDomainName theDomainName  3571 Apr 21 08:27 CONTRIBUTING.md*
-rwxr-xr-x  1 theDomainName theDomainName 12225 Apr 21 08:27 htaccess.txt*
-rwxr-xr-x  1 theDomainName theDomainName  2421 Apr 21 08:27 index.php*
-rwxr-xr-x  1 theDomainName theDomainName 47540 Apr 21 08:27 install.php*
etc

Однако в настройках Amazon VPS папка для веб-сайта имеет вид:

drwxrwsr-x 6 root www 4096 May  7 14:07 html

и как только я tar распаковал, я получил

-rwxr-xr-x 1 myUserName www  537 Apr 21 12:27 composer.json
-rwxr-xr-x 1 myUserName www 3.5K Apr 21 12:27 CONTRIBUTING.md
-rwxr-xr-x 1 myUserName www  12K Apr 21 12:27 htaccess.txt
-rwxr-xr-x 1 myUserName www 2.4K Apr 21 12:27 index.php
etc

Итак, основная разница здесь в том, что в версии trad VPS владелец и группа И имя пользователя, под которым я вхожу в систему, одинаковы, в то время как в моем Amazon VPS это не так.

Поэтому, возможно, более краткий вопрос заключается в том, как мне эмулировать то, что делает традиционный VPS...?

Является ли это случаем создания, для каждого виртуального хоста, пользователя и группы и входа под этим пользователем...?

Пошел и попробовал это, хотя я не совсем уверен, если/почему это может сработать....