4.7.x Installation Contao localhost

Installation Contao localhost

Hallo liebe Contao-Gemeinde!

Zu mir: Ich bin blutiger Anfänger, grün hinter den Ohren in Sachen php, MySQL und Co. und möchte mit Contao anfangen, mich in die Sache einzuarbeiten. Zur Zeit besitze ich null Erfahrungen und bitte daher um Unterstützung und haut mir bitte nicht zu viele Kürzel und Fachbegriffe um die Ohren! Danke! ,-)

Zum konkreten Problem: Ich benötige Hilfe bei der Installation von Contao auf meinem Mac, also localhost. Status der Installation ist der System-Check, in dem ein Fehler herausgegeben wird:

(...) PHP Web Process
Unable to write to the temporary system directory.
This is most likely a problem with your hosting configuration. Make sure that either open_basedir does allow access to the temporary directory or that the sys_temp_dir is correctly configured. (...)

Okay, ich habe verstanden, dass ich open_basedir verändern muss. Aber wo, dass habe ich weder mit Hilfe des Forums noch bei Google herausfinden können. Wäre schön, wenn ihr mit das mitteilt.

Vorgeschichte:Mac-User, XAMPP installiert, Contao-Installation über localhost/projekt/web/ontao-manager.phar.php

Viele Grüße
Makkes

Viele verwenden auf dem Mac MAMP anstelle von XAMPP. Möglicherweise funktioniert es damit sofort, ohne dass Du erst Konfigurationen anpassen musst.

Ok, ich gehe zurück zum Start .-)

Zitat:

Zitat von xchs

Viele verwenden auf dem Mac MAMP anstelle von XAMPP. Möglicherweise funktioniert es damit sofort, ohne dass Du erst Konfigurationen anpassen musst.

step by step

Also, ein Schritt bin ich weiter gekommen.
Jetzt stecke ich beim System-Check bei "Composer Environment
Composer dependencies are not installed." fest...
Fehlermeldung: "Console task terminated!
The background task has stopped unexpectedly. Please check the console protocol."

Was fehlt denn jetzt?

#kann_denn_nicht_einfach_mal_etwas_funktionieren?

Was genau steht denn im "Console Protocol"?

Liste der Anhänge anzeigen (Anzahl: 2)

ich habe noch etwas hin- und her versucht und bin nun beim Check durch, kann aber das backend nicht öffnen, da angeblich die Installation nicht durchgelaufen wäre...

Anhang 22406
Anhang 22407

Nur zum Verständnis: Hast du nach der Installation der Contao-Dateien mittels Contao-Manager das Install-Tool aufgerufen (entweder durch direkten Aufruf oder durch Klick auf den Link im Contao-Manager) und die Datenbank-Zugangsdaten angegeben?

###solved###

...ich musste erst einmal überlegen, wie ich die Anmerkung richtig verstehen könnte.

Ich muss sagen, danke für den Wink! Ich habe mich noch mehr damit auseinander gesetzt und habe über den Finder zu der install gefunden. Jetzt erst habe ich den Pfad zur install verstanden.
Des Weiteren konnte ich mich durch die weiteren Installationsschritte durchwursteln.
Nun ist die Installation abgeschlossen, ich bin im Backend angemeldet, mögliche weitere Fragen erscheinen dann in dieser Rubrik nicht mehr.

Viele Dank und viele Grüße
Makkes

Zitat:

Zitat von Makkes

und habe über den Finder zu der install gefunden

Die Route contao/install für das Contao Installtool (bzw. contao/login für das Contao Backend) ist keinem physischem Verzeichnis bzw. Skript zugeordnet, sondern existiert quasi nur "virtuell". Ein entsprechendes Skript findet man daher innerhalb der Installation nicht (mehr).

hm... nicht? Dann war das nur ein Zufallstreffer? Erschreckend!

Aber vielleicht erklärt das, warum ich im Backend, wenn ich im Menü auf "Mate Theme Setup" die Funktion "Theme-Dateien synchronisieren" klicke, zur Fehlermeldung "Not Found The requested URL /contao was not found on this server." führt. Anscheins muss ich noch irgendwo das Wurzelverzeichnis eintragen.

Während ich eigentlich noch im Verzeichnis "http://localhost:8888/projekt/web/contao?..." arbeite,
springt der Klick auf die o. g. Funktion auf "http://localhost:8888/contao?do=mateThemeSetup&act=syncFolder" um. "projekt/web/" geht verloren...

Ich kann es leider nicht besser erklären, aber irgendetwas ist immer noch faul...

In diesem Fall wäre es wahrscheinlich besser, einen virtuellen Host einzurichten (z. B. mate.local) und das Contao Backend via http://mate.local/contao aufzurufen. Der DocumentRoot von mate.local müsste dabei direkt auf das web/ Unterverzeichnis (/projekt/web/) verweisen.

Wie aus der Historie erkennbar habe ich ja MAMP installiert. Sorry, für die Frage, aber: Wie kann ich denn ein mate.local einrichten? Über MAMP?

Dafür gibt es etliche Anleitungen im Netz, z. B.

https://www.wildbits.de/2008/04/20/m...rtuelle-hosts/
https://www.codesolutions.de/mac-mam...-host-anlegen/

Oder hier etwas für die Video-Fraktion: https://www.youtube.com/watch?v=Chyive5BmPk

Schau mal, ob Du damit zurecht kommst.

NB: mate.local ist natürlich nur ein Beispiel. Du kannst für Deinen virtuellen Host natürlich auch einen anderen Namen vergeben, der ggf. besser für das Projekt passt.

...thanx @ xchs!

Ich stehe auf der Leitung...

Habe die Veränderungen wie hier beschrieben durchgeführt:
https://macs-moritz.com/virtual-host...unter-mac-os-x

Mit dem Ziel, dass erst nur Fehlermeldungen kamen, nun komme ich auf localhost, sehe aber nur den Inhalt aus dem Ordner "htdocs".

Es ist ja schon merkwürdig, wenn ich MAMP öffne, "WebStart öffne" klicke, dann im Hauptmenü oben "Meine Website" anklicke und ich wieder nur "Index of / projektbesipiel/" sehe...

Denke ich zu kompliziert?

Wie schaut denn Deine httpd.conf (bzw. httpd-vhosts.conf) und Deine hosts Datei genau aus (inkl. Deiner Änderungen)?

Hi!
Danke, dass du mir noch weiter helfen möchtest...

Ich habe die erste beiden Dateien "httpd.conf" und "httpd-vhosts.conf" doppelt gefunden, die hosts über den Terminal "sudo nano /etc/hosts", in der Hoffnung das war richtig so.

- MAMP > conf > apache > httpd.conf
(gefunden habe ich allerdings auch eine httpd.conf-Datei in MAMP > conf > apache > original > httpd.conf)

- MAMP > conf > apache > extra > httpd-vhosts.conf
(gefunden habe ich allerdings auch eine httpd.conf-Datei in MAMP > conf > apache > original > extra > httpd-vhosts.conf)

Die hosts sieht bei mir so aus:

Code:

## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost vfb 255.255.255.255 broadcasthost ::1 localhost

httpd.conf

Code:

# # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:http://httpd.apache.org/docs/2.2> for detailed information. # In particular, see # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html> # 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 "logs/foo_log" # with ServerRoot set to "/Applications/MAMP/Library" will be interpreted by the # server as "/Applications/MAMP/Library/logs/foo_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 point the LockFile directive # at a local disk. If you wish to share the same ServerRoot for multiple # httpd daemons, you will need to change at least LockFile and PidFile. # ServerRoot "/Applications/MAMP/Library" # # PidFile: The file in which the server should record its process # identification number when it starts. # <IfModule !mpm_netware.c> PidFile logs/httpd.pid </IfModule> # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the <VirtualHost> # 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 8888 # # 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 # LoadModule authn_file_module modules/mod_authn_file.so LoadModule authn_dbm_module modules/mod_authn_dbm.so LoadModule authn_anon_module modules/mod_authn_anon.so LoadModule authn_dbd_module modules/mod_authn_dbd.so LoadModule authn_default_module modules/mod_authn_default.so LoadModule authz_host_module modules/mod_authz_host.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule authz_dbm_module modules/mod_authz_dbm.so LoadModule authz_owner_module modules/mod_authz_owner.so LoadModule authz_default_module modules/mod_authz_default.so LoadModule auth_basic_module modules/mod_auth_basic.so LoadModule auth_digest_module modules/mod_auth_digest.so LoadModule file_cache_module modules/mod_file_cache.so LoadModule cache_module modules/mod_cache.so LoadModule disk_cache_module modules/mod_disk_cache.so LoadModule mem_cache_module modules/mod_mem_cache.so LoadModule dbd_module modules/mod_dbd.so LoadModule bucketeer_module modules/mod_bucketeer.so LoadModule dumpio_module modules/mod_dumpio.so LoadModule echo_module modules/mod_echo.so LoadModule case_filter_module modules/mod_case_filter.so LoadModule case_filter_in_module modules/mod_case_filter_in.so LoadModule reqtimeout_module modules/mod_reqtimeout.so LoadModule ext_filter_module modules/mod_ext_filter.so LoadModule include_module modules/mod_include.so LoadModule filter_module modules/mod_filter.so LoadModule substitute_module modules/mod_substitute.so LoadModule charset_lite_module modules/mod_charset_lite.so LoadModule deflate_module modules/mod_deflate.so LoadModule log_config_module modules/mod_log_config.so LoadModule logio_module modules/mod_logio.so LoadModule env_module modules/mod_env.so LoadModule mime_magic_module modules/mod_mime_magic.so LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule expires_module modules/mod_expires.so LoadModule headers_module modules/mod_headers.so LoadModule ident_module modules/mod_ident.so LoadModule usertrack_module modules/mod_usertrack.so #LoadModule unique_id_module modules/mod_unique_id.so LoadModule setenvif_module modules/mod_setenvif.so LoadModule version_module modules/mod_version.so LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_connect_module modules/mod_proxy_connect.so LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_scgi_module modules/mod_proxy_scgi.so LoadModule proxy_ajp_module modules/mod_proxy_ajp.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule ssl_module modules/mod_ssl.so LoadModule mime_module modules/mod_mime.so LoadModule dav_module modules/mod_dav.so LoadModule status_module modules/mod_status.so LoadModule autoindex_module modules/mod_autoindex.so LoadModule asis_module modules/mod_asis.so LoadModule info_module modules/mod_info.so LoadModule cgi_module modules/mod_cgi.so LoadModule fastcgi_module modules/mod_fastcgi.so LoadModule cgid_module modules/mod_cgid.so LoadModule dav_fs_module modules/mod_dav_fs.so LoadModule vhost_alias_module modules/mod_vhost_alias.so LoadModule negotiation_module modules/mod_negotiation.so LoadModule dir_module modules/mod_dir.so LoadModule imagemap_module modules/mod_imagemap.so LoadModule actions_module modules/mod_actions.so LoadModule speling_module modules/mod_speling.so LoadModule userdir_module modules/mod_userdir.so LoadModule alias_module modules/mod_alias.so LoadModule rewrite_module modules/mod_rewrite.so LoadModule perl_module modules/mod_perl.so LoadModule wsgi_module modules/mod_wsgi.so LoadModule xsendfile_module modules/mod_xsendfile.so LoadModule php7_module /Applications/MAMP/bin/php/php7.3.1/modules/libphp7.so # AddType application/x-httpd-php .php .phtml <IfModule !mpm_netware_module> <IfModule !mpm_winnt_module> # # 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 xyz Group #-1 </IfModule> </IfModule> <IfModule xsendfile_module> XSendFile on </IfModule> # '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 # <VirtualHost> definition. These values also provide defaults for # any <VirtualHost> containers you may define later in the file. # # All of these directives may appear inside <VirtualHost> 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 you@example.com # # 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 localhost:8888 # # 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. # # MAMP DOCUMENT_ROOT !! Don't remove this line !! DocumentRoot "/Applications/MAMP/htdocs" # # Each directory to which Apache has access can be configured with respect # to which services and features are allowed and/or disabled in that # directory (and its subdirectories). # # First, we configure the "default" to be a very restrictive set of # features. # <Directory /> Options Indexes FollowSymLinks AllowOverride None </Directory> # # 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. # # # This should be changed to whatever you set DocumentRoot to. # <Directory "/Applications/MAMP/htdocs"> # # 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.2/mod/core.html#options # for more information. # Options All # # 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. # Order allow,deny Allow from all XSendFilePath "/Applications/MAMP/htdocs" </Directory> # # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # <IfModule dir_module> DirectoryIndex index.html index.php <IfModule perl_module> DirectoryIndex index.pl </IfModule> <IfModule wsgi_module> DirectoryIndex index.wsgi index.py </IfModule> </IfModule> # # 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. # <FilesMatch "^\.ht"> Order allow,deny Deny from all Satisfy All </FilesMatch> <Files ~ "^\.DS_Store"> Order allow,deny Deny from all </Files> # # 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 "/Applications/MAMP/logs/apache_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 error <IfModule log_config_module> # # 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 <IfModule logio_module> # 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 </IfModule> # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a <VirtualHost> # container, they will be logged here. Contrariwise, if you *do* # define per-<VirtualHost> access logfiles, transactions will be # logged therein and *not* in this file. # #CustomLog "/Applications/MAMP/logs/apache_access.log" common # # If you prefer a logfile with access, agent, and referer information # (Combined Logfile Format) you can use the following directive. # #CustomLog "/Applications/MAMP/logs/apache_access.log" combined </IfModule> <IfModule alias_module> # # 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 <Directory> section to allow access to # the filesystem path. # # We include the /icons/ alias for FancyIndexed directory listings. If you # do not use FancyIndexing, you may comment this out. # Alias /favicon.ico "/Applications/MAMP/bin/favicon.ico" Alias /icons/ "/Applications/MAMP/Library/icons/" <Directory "/Applications/MAMP/Library/icons"> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory> Alias /phpMyAdmin "/Applications/MAMP/bin/phpMyAdmin" Alias /phpmyadmin "/Applications/MAMP/bin/phpMyAdmin" <Directory "/Applications/MAMP/bin/phpMyAdmin"> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory> Alias /phpPgAdmin "/Applications/MAMP/bin/phpPgAdmin" Alias /phppgadmin "/Applications/MAMP/bin/phpPgAdmin" <Directory "/Applications/MAMP/bin/phpPgAdmin"> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory> Alias /phpLiteAdmin "/Applications/MAMP/bin/phpLiteAdmin" Alias /phpliteadmin "/Applications/MAMP/bin/phpLiteAdmin" <Directory "/Applications/MAMP/bin/phpLiteAdmin"> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory> Alias /MAMP "/Applications/MAMP/bin/mamp" <Directory "/Applications/MAMP/bin/mamp"> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory> Alias /adminer "/Applications/MAMP/bin/adminer" <Directory "/Applications/MAMP/bin/adminer"> DirectoryIndex adminer.php Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory> # # 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/ "/Applications/MAMP/cgi-bin/" Alias /perl/ "/Applications/MAMP/cgi-bin/" <IfModule perl_module> PerlModule ModPerl::Registry <Location /perl> SetHandler perl-script PerlResponseHandler ModPerl::Registry PerlOptions +ParseHeaders Options +ExecCGI </Location> </IfModule> </IfModule> <IfModule cgid_module> # # ScriptSock: On threaded servers, designate the path to the UNIX # socket used to communicate with the CGI daemon of mod_cgid. # #Scriptsock logs/cgisock </IfModule> # # "/Applications/MAMP/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # <Directory "/Applications/MAMP/cgi-bin"> AllowOverride None Options None Order allow,deny Allow from all </Directory> # # DefaultType: 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. # DefaultType text/plain <IfModule mime_module> # # TypesConfig points to the file containing the list of mappings from # filename extension to MIME-type. # TypesConfig /Applications/MAMP/conf/apache/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 .pl # 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 </IfModule> # # 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. # <IfModule mime_magic_module> MIMEMagicFile /Applications/MAMP/conf/apache/magic </IfModule> # # 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 is 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. # #EnableMMAP off #EnableSendfile off # Supplemental configuration # # The configuration files in the /Applications/MAMP/conf/apache/extra/ directory can be # included to add extra features or to modify the default configuration of # the server, or you may simply copy their contents here and change as # necessary. # Server-pool management (MPM specific) #Include /Applications/MAMP/conf/apache/extra/httpd-mpm.conf # Multi-language error messages #Include /Applications/MAMP/conf/apache/extra/httpd-multilang-errordoc.conf # Fancy directory listings #Include /Applications/MAMP/conf/apache/extra/httpd-autoindex.conf # Language settings #Include /Applications/MAMP/conf/apache/extra/httpd-languages.conf # User home directories #Include /Applications/MAMP/conf/apache/extra/httpd-userdir.conf # Real-time info on requests and configuration #Include /Applications/MAMP/conf/apache/extra/httpd-info.conf # Virtual hosts #Include /Applications/MAMP/conf/apache/extra/httpd-vhosts.conf NameVirtualHost * <VirtualHost *> DocumentRoot "/Applications/MAMP/htdocs" ServerName localhost </VirtualHost> <VirtualHost *> DocumentRoot "/Applications/MAMP/vhost/vfb" ServerName projekt1 </VirtualHost> # Local access to the Apache HTTP Server Manual #Include /Applications/MAMP/conf/apache/extra/httpd-manual.conf # Distributed authoring and versioning (WebDAV) #Include /Applications/MAMP/conf/apache/extra/httpd-dav.conf # Various default settings #Include /Applications/MAMP/conf/apache/extra/httpd-default.conf # Secure (SSL/TLS) connections #Include /Applications/MAMP/conf/apache/extra/httpd-ssl.conf # # Note: The following must must be present to support # starting without SSL on platforms with no /dev/random equivalent # but a statically compiled-in mod_ssl. # <IfModule ssl_module> SSLRandomSeed startup file:/dev/urandom 1024 SSLRandomSeed connect file:/dev/urandom 1024 # # Uncomment the next line if Apache should not accept SSLv3 connections, to learn more google for "POODLE SSLv3". # SSLProtocol All -SSLv2 -SSLv3 </IfModule>

httpd-vhosts.conf

Code:

# # Virtual Hosts # # If you want to maintain multiple domains/hostnames on your # machine you can setup VirtualHost containers for them. Most configurations # use only name-based virtual hosts so the server doesn't need to worry about # IP addresses. This is indicated by the asterisks in the directives below. # # Please see the documentation at # <URL:http://httpd.apache.org/docs/2.2/vhosts/> # for further details before you try to setup virtual hosts. # # You may use the command line option '-S' to verify your virtual host # configuration. # # Use name-based virtual hosting. # NameVirtualHost *:80 # # VirtualHost example: # Almost any Apache directive may go into a VirtualHost container. # The first VirtualHost section is used for all requests that do not # match a ServerName or ServerAlias in any <VirtualHost> block. # <VirtualHost *:80> ServerAdmin webmaster@dummy-host.example.com DocumentRoot "/Applications/MAMP/Library/docs/dummy-host.example.com" ServerName dummy-host.example.com ServerAlias www.dummy-host.example.com ErrorLog "logs/dummy-host.example.com-error_log" CustomLog "logs/dummy-host.example.com-access_log" common </VirtualHost> 2 3 4 5 6 7 8 9 ### <VirtualHost *:80> ServerAdmin my.email@address.com DocumentRoot "/vfb/web/" ServerName local.meinprojekt.com ErrorLog "logs/vfb-error_log" CustomLog "logs/vfb-access_log" common </VirtualHost> ### <VirtualHost *:80> ServerAdmin webmaster@dummy-host2.example.com DocumentRoot "/Applications/MAMP/Library/docs/dummy-host2.example.com" ServerName dummy-host2.example.com ErrorLog "logs/dummy-host2.example.com-error_log" CustomLog "logs/dummy-host2.example.com-access_log" common </VirtualHost>

Du müsstest in Deiner httpd.conf in der Zeile

Code:

#Include /Applications/MAMP/conf/apache/extra/httpd-vhosts.conf

das Kommentarzeichen # vorne löschen, damit die Konfigurationsdatei geladen bzw. berücksichtigt wird.

Ferner würde ich in der hosts Datei als lokale Domain z. B.

Code:

127.0.0.1 vfb.local

verwenden.

Deine Virtualhost-Konfiguration in der httpd-vhosts.conf müsste demnach so ausschauen:

Code:

<VirtualHost *:80> DocumentRoot "/vfb/web/" ServerName vfb.local </VirtualHost>

Unter Umständen müsstest Du in den MAMP-Einstellungen auch noch festlegen, dass der Webserver auf dem Port 80 lauscht.

Ich empfehle dir devilbox zu verwenden. Dafür gibt es sogar eine offizielle Anleitung https://devilbox.readthedocs.io/en/l...up-contao.html

Liste der Anhänge anzeigen (Anzahl: 2)

Hallo zusammen!

@ 41xchs:

Habe ich das richtig verstanden?
Den Port bei den MAMP auf 80 einstellen, s. screenshot
Anhang 22420

die entsprechende Datei habe ich angepasst, erhalte aber immer die Fehlermeldung, dass MAMP oder Asche nicht richtig konfiguriert ist, s. screenshot.
Anhang 22421

Könnte noch etwas falsch sein?

Eine Frage am Rand: Warum sehe ich die Dateien zwei Mal?

@ 06joe:
Vielen Dank für den Tipp. Ich habe jetzt schon zwei System ausprobiert und bin noch nicht so verzweifelt ein drittes auszuprobieren. Ich ziehe das jetzt durch... ,-)

Zitat:

Zitat von Makkes

Habe ich das richtig verstanden?
Den Port bei den MAMP auf 80 einstellen

Ja. Du kannst auch unten auf den Button "Web- und MySQL-Ports auf 80 & 3306 setzen" klicken.

Zitat:

Zitat von Makkes

die entsprechende Datei habe ich angepasst, erhalte aber immer die Fehlermeldung, dass MAMP oder Asche nicht richtig konfiguriert ist

Keine Ahnung. Könnte irgendein Syntax- oder Tippfehler sein. Oben in Deiner httpd-vhosts.conf hattest Du z. B. einen Block mit

Code:

2 3 4 5 6 7 8 9

gepostet. Steht das tatsächlich noch so in Deiner Datei?

Zitat:

Zitat von Makkes

Eine Frage am Rand: Warum sehe ich die Dateien zwei Mal?

Welche Dateien? Wo denn?

Schau Dir vielleicht auch (nochmals) das YouTube-Video an, welches ich oben gepostet hatte. Dort wird das Ganze ausführlich durchexerziert.