mountaindogmedia left the following comment on my post for installing Apache, PHP, and MySQL on Mac OS X:
- How to deactivate MacOS server apache. This command deactivates web services $ sudo serveradmin stop web These commands should unload the launch daemons inside Server app. Following my experience Server Apache takes over as soon as you install server app. Stopping web services in some cases is not sufficient.
- The other option is XAMPP, which is available for both OS X and Linux.XAMPP is completely free and version 1.7.3 includes Apache 2.2.14, MySQL 5.1.144, PHP 5.3.1, Perl 5.10.1, and ProFTPD 1.3.3.
Jason, have you tried a modified
Include
statement for virtual hosts to map a directory? So instead of /etc/apache2/extra/httpd-vhosts.conf
as indicated, one would use /etc/apache2/extra/vhosts/*.conf
and then just create a default.conf
for the first virtual host, and then add/edit/delete vhost files as needed. I think it would be easier to manage host files and changes.If you use Mac OS X as your platform for development work, then you may be interested to know how easy it is to use Apache Cassandra on the Mac. The following shows you how to download and setup Cassandra, its utilities, and also use DataStax OpsCenter, which is a browser-based, visual management and monitoring tool for Cassandra. Convert the httpdserverapp.conf file Example diff file for httpdserverapp.conf Page 33 Wiki Overview Before you begin Post-migration result Manually migrate wikis to WordPress Export a browsable wiki HTML snapshot to file system After you finish macOS Server— Service Migration Guide March 2018 2. With Apples’ new macOS High Sierra 10.13 available for download, here is how to get the AMP stack up and running on the new macOS. This tutorial will go through the process on getting Apache, MySQL, PHP (or otherwise known as the ‘AMP’ stack) and phpMyAdmin running on the new mac OS High Sierra.
Indeed, mountaindogmedia, this is an easier way. In fact, this is the default configuration for many servers.
By default, the Apache Virtual Host configuration on Mac OS X is located in a single file:
/etc/apache2/extra/httpd-vhosts.conf
. You need to edit the Apache configuration to include this file and enable virtual hosts.Over the years, I have created many virtual hosts. Each time editing
httpd-vhosts.conf
. To mountaindogmedia's point, this becomes difficult to manage. Furthermore, Apache configurations often get reset when upgrading Mac OS X. In the same amount of steps (two), you can adopt a more manageable configuration.What are Virtual Hosts?
From the Apache Virtual Host documentation:
The term Virtual Host refers to the practice of running more than one web site on a single machine.
Xerox phaser 3124 driver mac download. By default, the Apache configuration on Mac OS X serves files from
/Library/WebServer/Documents
accessed by the name locahost
. This is essentially a single site configuration. You could mimic multiple sites by creating subdirectories and access a site at localhost/somesite
.This is not ideal for several reasons. Primarily, we would rather access the site using a name like
somesite.local
. To do that, you need to configure virtual hosts.A Cleaner Configuration
Before I being, I assume you already installed and configured Apache on Mac OS X.
First, open the Terminal app and switch to the
root
user to avoid permission issues while running these commands.Edit the Apache configuration file:
Find the following line:
Below it, add the following line:
Just the Mac App StoreThe safest option to choose here would be the 'Mac App Store,' since Apple reviews all apps that are accepted in their store and can remove them quickly if necessary. https://fsaumkv.weebly.com/blog/install-mac-apps-from-unidentified-developer. You will know that your Mac will be as free as possible from malware if you use this option only.
This configures Apache to include all files ending in
.conf
in the /private/etc/apache2/vhosts/
directory. Now we need to create this directory.Create the default virtual host configuration file.
Add the following configuration:
I create this file to serve as the default virtual host. When Apache can not find a matching virtual host, it will use the first configuration. By prefixing this file with an underscore, Apache will include it first. Techincally this file is not needed as it simply repeats the configuraton already in
httpd.conf
. However, it provides a place to add custom configuration for the default virtual host (i.e. localhost
).Now you can create your first virtual host. The example below contains the virtual host configuration for my site. Of course, you will want to substitute jasonmccreary.me with your domain name.
Create the virtual host configuration file:
Add the following configuration:
This
VirtualHost
configuration allows me to access my site from http://jasonmccreary.local for local development.Note: I use the extension local. This avoids conflicts with any real extensions and serves as a reminder I am developing in my local environment.
Note: The
Require all granted
configuration became available in Apache 2.4 which comes with Mac OS X Yosemite. If you are running a version of OS X before Yosemite, use the equivalent 2.2 configuration in the upgrading Apache examples.The final step is to restart Apache:
If you run into any problems, run:
This will test your Apache configuration and display any error messages.
Mapping the .local extension
In order to access sites locally you need to edit your hosts file.
Add a line to the bottom of this file for your virtual host. It should match the value you used for the
ServerName
configuration. For example, my site:I like to run the following to clear the local DNS cache:
Now you can access your site using the .local extension. For example, http://jasonmccreary.local.
A note about permissions
You may receive 403 Forbidden when you visit your local site. This is likely a permissions issue. Simply put, the Apache user (
_www
) needs to have access to read, and sometimes write, to your web directory.If you are not familiar with permissions, read more. For now though, the easiest thing to do is ensure your web directory has permissions of
755
. You can change permissions with the command:In my case, all my files were under my local
~/Documents
directory. Which by default is only readable by me. So I had to change permissions from my web directory all the way up to ~/Documents
to resolve the 403 Forbidden issue.Note: There are many ways to solve permission issues. I have provided this as the easiest solution, not the best.
In Closing
Any time you want to add a site to Apache on your Mac, simply create a virtual host configuration file for that site and map it in your hosts file.
Find this interesting? Let's continue the conversation on Twitter.
Get your Local Web Development Environment Up & Running on macOS High Sierra 10.13
With Apples’ new macOS High Sierra 10.13 available for download, here is how to get the AMP Mac open non appstore apps. stack up and running on the new macOS. This tutorialwill go through the process on getting Apache, MySQL, PHP (or otherwise known as the ‘AMP’ stack)and phpMyAdmin running on the new mac OS High Sierra.
This tutorial sets up the AMP stack in more of a traditional way using the loaded Apache and PHP and downloading MySQL and phpMyAdmin.
Setting Stuff Up
Apache/WebSharing
Web serving is built into High Sierra with Apache app, it is installed ready to be fired up.
This needs to be done in the Terminal which is found in the OS filing system at /Applications/Utilities/Terminal
For those not familiar with the Terminal, it really isn’t as intimidating as you may think, once launched you are faced with a command prompt waiting for your commands – just type/paste in a command and hit enter, some commands give you no response – it just means the command is done, other commands give you feedback.
Using the prefix of sudo is required for commands that have their applications protected in certain folders – when using sudo you will need to confirm with your admin password or iCloud password if set up that way…. lets get to it….
to start Apache web sharing
to stop it
to restart it
To find the Apache version
The Apache version that comes in macOS High Sierra is Apache/2.4.27
After starting Apache – test to see if the webserver is working in the browser – http://localhost – you should see the “It Works!” text.
If you don’t get the localhost test, you can try troubleshooting Apache to see if there is anything wrong in its config file by running
This will give you an indication of what might be wrong.
Document Root
Document root is the location where the files are shared from the file system and is similar to the traditional names of ‘public_html‘ and ‘htdocs‘, macOS has historically had 2 web roots one at a system level and one at a user level – you can set both up or just run with one, the user level one allows multiple accounts to have their own web root whilst the system one is global for all users. It seems there is less effort from Apple in continuing with the user level one but it still can be set up with a couple of extra tweaks in configuration files. It is easier to use the user level one as you don’t have to keep on authenticating as an admin user.
System Level Web Root
– the default system document root is still found at –
http://localhost/
The files are shared in the filing system at –
User Level Root
The other web root directory which is missing by default is the ‘~/Sites’ folder in the User account. This takes a bit longer to set up but some users are very accustomed to using it.
You need to make a “Sites” folder at the root level of your account and then it will work. Once you make the Sites folder you will notice that it has a unique icon which is a throwback from a few versions older. Make that folder before you set up the user configuration file described next.
You have to make a few additional tweaks to get the ~/Sites folder back up and running.
Sites Folder
Add a “username.conf” filed under:
If you don’t already have one (very likely), then create one named by the short username of the account with the suffix .conf, its location and permissions/ownership is best tackled by using the Terminal, the text editor ‘nano‘ would be the best tool to deal with this.
If you would rather edit config files in a text editor as an app I would suggest the free BBEdit which allows you to open hidden system files.
Launch Terminal, (Applications/Utilities), and follow the commands below, first one gets you to the right spot, 2nd one opens the text editor on the command line (swap ‘username‘ with your account’s shortname, if you don’t know your account shortname type ‘whoami‘ the Terminal prompt):
![Macos server free Macos server free](/uploads/1/3/4/2/134275171/871414727.png)
Then add the content below swapping in your ‘username’ in the code below:
Permissions on the file should be:
If not you need to change…
Open the main httpd.conf and allow some modules:
And make sure these modules are uncommented (the first 2 should already be on a clean install):
Whilst you have this file open also to get php running uncomment. (Mentioned also in the PHP part of the article).
And also uncomment this configuration file also in httpd.conf – which allows user home directories.
Save all your changes (Control + O in nano)
Then open another Apache config file and uncomment another file:
The software is available for both Mac and Windows. A wide range of file formats is supported by MassWatermark such as TIFF, GIF, JPG and many more.Directly upload your images to Flickr and Picasa. MassWatermark also allows you to create zip file of all the processed images. Pdf watermark app mac.
And uncomment:
Save all your changes (Control + O in nano)
Restart Apache for the new file to be read:
Then this user level document root will be viewable at:
http://localhost/~username/
You should only see a directory tree like structure if the folder is empty.
Override .htaccess and allow URL Rewrites
If you are going to use the web serving document root at /Library/WebServer/Documents it is a good idea to allow any .htaccess files used to override the default settings – this can be accomplished by editing the httpd.conf file at line 217 and setting the AllowOverride to All and then restart Apache. Some programs on mojave says not optimized for your mac. This is already taken care of at the Sites level webroot by following the previous step.
Also whilst here allow URL rewrites so your permalinks look clean not ugly.
Uncomment in httpd.conf – should be uncommented on a clean install.
PHP
PHP 7.1.7 is a first for macOS and is loaded in this version of macOS High Sierra and needs to be turned on by uncommenting a line in the httpd.conf file.
Use “control” + “w” to search within nano and search for ‘php’ this will land you on the right line then uncomment the line (remove the #):
Write out and Save using the nano short cut keys at the bottom ‘control o’ and ‘control x’
Reload apache to kick in
To see and test PHP, create a file name it “phpinfo.php” and file it in your document root with the contents below, then view it in a browser.
MySQL
MySQL doesn’t come pre-loaded with macOS High Sierra and needs to be dowloaded from the MySQL site.
The latest version of MySQL 5.7.19 does work with the public release of macOS.
If you already have MySQL 5.7 and you have upgraded OS from El Capitan to Sierra I expect that to be ok, but will be interested if anyone comments on that.
Use the Mac OS X 10.12 (x86, 64-bit), DMG Archive version (works on macOS High Sierra).
If you are upgrading from a previous macOS and have an older MySQL version you do not have to update it. One thing with MySQL upgrades always take a data dump of your database in case things go south and before you upgrade to macOS High Sierra make sure your MySQL Server is not running.
When downloading you don’t have to sign up, look for » No thanks, just take me to the downloads! – go straight to the download mirrors and download the software from a mirror which is closest to you.
Once downloaded open the .dmg and run the installer.
When it is finished installing you get a dialog box with a temporary mysql root password – that is a MySQL root password not a macOS admin password. But I have found that the temporary password is pretty much useless so we’ll need to change it straight away, but first it is better to add mysql commands to your shell path.
You are told:
If you lose this password, please consult the section How to Reset the Root Password in the MySQL reference manual.
Add Mysql to your path
After installation, in order to use mysql commands without typing the full path to the commands you need to add the mysql directory to your shell path, (optional step) this is done in your “.bash_profile” file in your home directory, if you don’t have that file just create it using vi or nano:
The first command brings you to your home directory and opens the .bash_profile file or creates a new one if it doesn’t exist, then add in the line above which adds the mysql binary path to commands that you can run. Exit the file with type “control + x” and when prompted save the change by typing “y”. Last thing to do here is to reload the shell for the above to work straight away.
Change the MySQL root password
Note that this is not the same as the root or admin password of macOS – this is a unique password for the mysql root user. https://primebrown462.weebly.com/blog/wavelab-6-mac-os-x-download.
Stop MySQL
Start it in safe mode:
This will be an ongoing command until the process is finished so open another shell/terminal window, and log in without a password as root:
Change the lowercase ‘MyNewPass’ to what you want – and keep the single quotes.
Start MySQL
Starting MySQL
You can then start the MySQL server from the System Preferences or via the command line.
Or to Command line start MySQL.
To find the MySQL version from the terminal, type at the prompt:
This also puts you in to a shell interactive dialogue with mySQL, type q to exit.
Fix the 2002 MySQL Socket error
Fix the looming 2002 socket error – which is linking where MySQL places the socket and where macOS thinks it should be, MySQL puts it in /tmp and macOS looks for it in /var/mysql the socket is a type of file that allows mysql client/server communication.
Macos Apache Server App Setup
phpMyAdmin
First fix the 2002 socket error if you haven’t done so from the MySQL section-
Download phpMyAdmin, the zip English package will suit a lot of users, then unzip it and move the folder with its contents into the document root level renaming folder to ‘phpmyadmin’.
Make the config folder
Change the permissions
Run the set up in the browser
http://localhost/~username/phpmyadmin/setup/ orhttp://localhost/phpmyadmin/setup/
You need to create a new localhost mysql server connection, click new server.
Switch to the Authentication tab and set the local mysql root user and the password.
Add in the username “root” (maybe already populated, add in the password that you set up earlier for the MySQL root user set up, click on save and you are returned to the previous screen.
(This is not the macOS Admin or root password – it is the MySQL root user)
Now going to http://localhost/~username/phpmyadmin/ will now allow you to interact with your MySQL databases.
Permissions
To run a website with no permission issues it is best to set the web root and its contents to be writeable by all, since it’s a local development it shouldn’t be a security issue.
Lets say that you have a site in the User Sites folder at the following location ~/Sites/testsite you would set it to be writeable like so:
Macos File Server
If you are concerned about security then instead of making it world writeable you can set the owner to be Apache _www but when working on files you would have to authenticate more as admin you are “not” the owner, you would do this like so:
This will set the contents recursively to be owned by the Apache user.
If you had the website stored at the System level Document root at say /Library/WebServer/Documents/testsite then it would have to be the latter:
Macos Server Download
Another easier way to do this if you have a one user workstation is to change the Apache web user from _www to your account.
Disable Macos Server Apache
That’s it! You now have the native AMP stack running on top of macOS High Sierra.