This is an updated version of our prior OS X development series. The newly released macOS 10.14 Mojave and the accompanying updates to Brew require significant changes compared to prior releases, necessitating a thorough revamp in the process. Since macOS 10.12 we now use Homebrew's Apache, rather than the built-in version, but this new appraoch is more flexible and should continue to work on prior OS X versions. Developing web applications on macOS is a real joy. There are plenty of options for setting up your development environments, including the ever-popular that provides a nice UI on top of Apache, PHP and MySQL.

However, there are times when MAMP Pro has slow downs, or out of date versions, or is simply behaving badly due to its restrictive system of configuration templates and non-standard builds. It is times like these that people often look for an alternative approach, and luckily there is one, and it is relatively straight-forward to setup. In this blog post, we will walk you through setting up and configuring Apache 2.4 and multiple PHP versions. In the second blog post in this two-post series, we will cover MySQL, Apache virtual hosts, APC caching, and Xdebug installation. This guide is intended for experienced web developers. If you are a beginner developer, you will be better served using.

XCode Command Line Tools If you don't already have XCode installed, it's best to first install the command line tools as these will be used by homebrew: $ xcode-select -install Homebrew Installation This process relies heavily on the macOS package manager called Homebrew. Using the brew command you can easily add powerful functionality to your mac, but first we have to install it. This is a simple process, but you need to launch your Terminal ( /Applications/Utilities/Terminal) application and then enter: $ ruby -e '$(curl -fsSL Just follow the terminal prompts and enter your password where required. This may take a few minutes, but when complete, a quick way to ensure you have installed brew correctly, simply type: $ brew -version Homebrew 1.7.6 Homebrew/homebrew-core (git revision a1ed; last commit 2018-09-25) You should probably also run the following command to ensure everything is configured correctly: $ brew doctor It will instruct you if you need to correct anything. Mojave Required Libraries When installing fresh on Mojave, I ran into a few libraries that were missing when completing all the steps below.

To make things easier, please simply run these now: $ brew install openldap libiconv Apache Installation The latest macOS 10.14 Mojave comes with Apache 2.4 pre-installed, however, it is no longer a simple task to use this version with Homebrew because Apple has removed some required scripts in this release. However, the solution is to install Apache 2.4 via Homebrew and then configure it to run on the standard ports (80/443). If you already have the built-in Apache running, it will need to be shutdown first, and any auto-loading scripts removed. It really doesn't hurt to just run all these commands in order - even if it's a fresh installation: $ sudo apachectl stop $ sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist 2/dev/null Now we need to install the new version provided by Brew: $ brew install httpd Without options, httpd won't need to be built from source, so it installs pretty quickly.

Upon completion you should see a message like: 🍺 /usr/local/Cellar/httpd/2.4.35: 1,648 files, 26.9MB Now we just need to configure things so that our new Apache server is auto-started $ sudo brew services start httpd You now have installed Homebrew's Apache, and configured it to auto-start with a privileged account. It should already be running, so you can try to reach your server in a browser by pointing it at you should see a simple header that says 'It works!' Troubleshooting Tips If you get a message that the browser can't connect to the server, first check to ensure the server is up. $ ps -aef grep httpd You should see a few httpd processes if Apache is up and running. Try to restart Apache with: $ sudo apachectl -k restart You can watch the Apache error log in a new Terminal tab/window during a restart to see if anything is invalid or causing a problem: $ tail -f /usr/local/var/log/httpd/errorlog Apache is controlled via the apachectl command so some useful commands to use are: $ sudo apachectl start $ sudo apachectl stop $ sudo apachectl -k restart. The -k will force a restart immediately rather than asking politely to restart when apache is good and ready Visual Studio Code In past guides, I've always provided instructions to edit files using the default TextEdit application that comes pre-installed.

However, this is not what I use myself as it's a terrible editor and when testing my guide for Mojave, I kept running into problems with encoding, finding line numbers etc. The better solution is to simply install a better editor. So please install the amazingly versatile yet, 100% free, Visual Studio Code. It's available on Mac, Windows, and Linux, but right now we only care about the mac version. Go to the and click Download for Mac Once downloaded, drag the application to your preffered Applications location. Next, you want to install the command line tools, so follow the so that you can use the code command from the Terminal.

Apache Configuration Now that we have a working web server, we will want to do is make some configuration changes so it works better as a local development server. In the latest version of Brew, you have to manually set the listen port from the default of 8080 to 80, so we will need to edit Apache's configuration file.

/usr/local/etc/httpd/httpd.conf If you followed the instructions above you should be able to use Visual Studio Code to edit your files using the code Terminal command. However, if you want to use the default TextEditor application to perform edits, you can use the open -e command followed by the path to the file. $ code /usr/local/etc/httpd/httpd.conf Find the line that says Listen 8080 and change it to 80: Listen 80 Next we'll configure it to use the to change the document root for Apache. This is the folder where Apache looks to serve file from.

By default, the document root is configured as /usr/local/var/www. As this is a development machine, let's assume we want to change the document root to point to a folder in our own home directory. Search for the term DocumentRoot, and you should see the following line: DocumentRoot '/usr/local/var/www' Change this to point to your user directory where youruser is the name of your user account: DocumentRoot /Users/youruser/Sites You also need to change the tag reference right below the DocumentRoot line. This should also be changed to point to your new document root also. We removed the optional quotes around the directory paths as TextEdit will probably try to convert those to smart-quotes and that will result in a Syntax error when you try to restart Apache.

Even if you edit around the quotes and leave them where they are, saving the document may result in their conversion and cause an error. In that same block you will find an AllowOverride setting, this should be changed as follows: # AllowOverride controls what directives may be placed in.htaccess files. # It can be 'All', 'None', or any combination of the keywords: # AllowOverride FileInfo AuthConfig Limit # AllowOverride All Also we should now enable modrewrite which is commented out by default. Search for modrewrite.so and uncomment the line by removing the leading #: LoadModule rewritemodule lib/httpd/modules/modrewrite.so User & Group Now we have the Apache configuration pointing to a Sites folder in our home directory. One problem still exists, however. By default, apache runs as the user daemon and group daemon.

This will cause permission problems when trying to access files in our home directory. About a third of the way down the httpd.conf file there are two settings to set the User and Group Apache will run under. Change these to match your user account (replace youruser with your real username), with a group of staff: User youruser Group staff Servername Apache likes to have a server name in the configuration, but this is disabled by default, so search for: #ServerName www.example.com:8080 and replace it with: ServerName localhost Sites Folder Now, you need to create a Sites folder in the root of your home directory. You can do this in your terminal, or in Finder.

In this new Sites folder create a simple index.html and put some dummy content in it like: My User Web Root. $ mkdir /Sites $ echo 'My User Web Root' /Sites/index.html Restart apache to ensure your configuration changes have taken effect: $ sudo apachectl -k restart. If you have existing PHP installations via Brew, you need to first cleanup your setup with our guide before continuing with this section. We will proceed by installing PHP 5.6, PHP 7.0, PHP 7.1 and PHP 7.2 and using a simple script to switch between them as we need. Up until the end of March 2018, all PHP related brews were handled by Homebrew/php tab, but that has been deprecated, so now we use what's available in the Homebrew/core package. This should be a better maintained, but is a much less complete, set of packages. $ brew install php@5.6 $ brew install php@7.0 $ brew install php@7.1 $ brew install php@7.2 The first one will take a little bit of time as it has to install a bunch of brew dependencies.

Subsequent PHP versions will install faster. You no longer have to unlink each version between installing PHP versions as they are not linked by default Also, you may have the need to tweak configuration settings of PHP to your needs. A common thing to change is the memory setting, or the date.timezone configuration. The php.ini files for each version of PHP are located in the following directories: /usr/local/etc/php/5.6/php.ini /usr/local/etc/php/7.0/php.ini /usr/local/etc/php/7.1/php.ini /usr/local/etc/php/7.2/php.ini Let's switch back to the first PHP version now: $ brew unlink php@7.2 && brew link -force -overwrite php@5.6. At this point, I strongly recommend closing ALL your terminal tabs and windows. This will mean opening a new terminal to continue with the next step. This is strongly recommended because some really strange path issues can arise with existing terminals (trust me, I have seen it!).

Quick test that we're in the correct version: php -v PHP 5.6.38 (cli) (built: Sep 14 2018 22:30:40) Copyright (c) 1997-2016 The PHP Group Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies Apache PHP Setup - Part 1 You have successfully installed your PHP versions, but we need to tell Apache to use them. You will again need to edit the /usr/local/etc/httpd/httpd.conf file scroll to the bottom of the LoadModule entries. You will need to switch to each of your installed PHP versions and run update again to get updates for each PHP version and ensure you are running the version of PHP you intend. Activating Specific/Latest PHP Versions Due to the way our PHP linking is set up, only one version of PHP is linked at a time, only the current active version of PHP will be updated to the latest version. You can see the current active version by typing: $ php -v And you can see the specific versions of PHP available by typing: $ brew info php@7.0 php@7.0: stable 7.0.32 (bottled) keg-only General-purpose scripting language.

OK, that wraps up Part 1 of this 3 part series You now have a fully functional Apache 2.4 installation with a quick-and-easy way to toggle between PHP 5.6, 7.0, 7.1 and 7.2. To find out how to setup your environment with MySQL, Virtual Hosts, APC caching, YAML, and Xdebug. Also to find out how to setup SSL for your Apache Virtual Hosts.

So, you’ve decided to get Grav and build a site with it. Building with Grav gives you the power and flexibility you need to realize your site but you need to develop that site first. Using an efficient development strategy will allow you to build your site faster and hassle-free. You might even have fun while doing it!

When you look at how easy it is to set Grav up and get it running on a remote server, it can be very tempting to just do development there, especially given the fact that there are no databases to migrate over, and everything is file-based. However, don't be tempted by this approach! In this blog post I'll endeavor to explain why.

I had originally planned on penning a blog post about how easy it is to setup and deploy a Grav site with with. While that is a fantastic VPS service, someone on Gitter asked me about setting up Grav on Amazon's AWS, so I checked it out. What I found was pretty amazing. Even the free tier of the EC2 t2.micro package runs Grav like a boss! Combine this with awesome automated setup and server management via ServerPilot, and you have the makings of an unbeatable combination. In this blog post I'll go through step-by-step on how to get this setup on your own.

The hardest part is setting up EC2 as it's a bit ungainly, but other than that it's a doddle, and more importantly, it's free!

This page aims to help you remove Zeus “Virus” Scam. These Zeus “Virus” scam removal instructions work for every version of Mac and Microsoft Windows – 10, 7 and more. Browser hijackers could be a form of panic-ware which tricks you into thinking that your computer has been infected when in fact all you are really experiencing is some form of a pop-up or browser redirect. They are becoming more and more common nowadays. In this article we will describe one particular hijacker (panic-ware) – Zeus “Virus”. Briefly speaking, these annoying programs may be fully capable of disturbing all your browsers (Safari/ Firefox/ Chrome/ etc.) and irritating you by constantly producing pop-up ads; sometimes redirecting you to various places or changing your browser’s appearance by substituting your favorite search engine and homepage with new ones.

For all details about Zeus, proceed with the following paragraphs. If SpyHunter detects a malware, you will have to purchase a license to remove it. Keep in mind, SpyHunter’s malware detection tool is free.

To remove the infection, you’ll need to purchase the full version. And Zeus Virus Removal (Microsoft Support Scam) If you are a Windows user, continue with the guide below.

Zeus Web Server Due For Mac Free

If you are a Mac user, please use our guide. If you are an Android user, please use our guide. Some of the steps will likely require you to exit the page. Nvidia geforce 8400 gs windows 7 video card driver download.

Bookmark it for later reference. (use this guide if you don’t know how to do it). READ CAREFULLY BEFORE PROCEEDING! File Name: File Size: File Type: Detection ratio: Scan Results Virus Scanner Result ClamAV AVG AV Maldet A fter you open their folder, end the processes that are infected, then delete their folders. Note: If you are sure something is part of the infection – delete it, even if the scanner doesn’t flag it. No anti-virus program can detect all infections. Hold together the Start Key and R.

Type appwiz.cpl – OK. You are now in the Control Panel. Look for suspicious entries. Uninstall it/them. Type msconfig in the search field and hit enter. A window will pop-up: Startup — Uncheck entries that have “Unknown” as Manufacturer or otherwise look suspicious. Hold the Start Key and R – copy + paste the following and click OK: notepad%windir%/system32/Drivers/etc/hosts A new file will open. If you are hacked, there will be a bunch of other IPs connected to you at the bottom.

Look at the image below: If there are suspicious IPs below “ Localhost” – write to us in the comments. Open the start menu and search for Network Connections (On Windows 10 you just write it after clicking the Windows button), press enter. Right-click on the Network Adapter you are using — Properties — Internet Protocol Version 4 (ICP/IP), click Properties.

The DNS line should be set to Obtain DNS server automatically. If it is not, set it yourself. Click on Advanced — the DNS tab.

Remove everything here (if there is something) — OK. After you complete this step, the threat will be gone from your browsers. Finish the next step as well or it may reappear on a system reboot. Right click on the browser’s shortcut — Properties. NOTE: We are showing Google Chrome, but you can do this for Firefox and IE (or Edge).

Properties —– Shortcut. In Target, remove everything after.exe. Remove Zeus Virus from Internet Explorer: Open IE, click —– Manage Add-ons. Find the threat — Disable. G o to —– Internet Options — change the URL to whatever you use (if hijacked) — Apply. Remove Zeus Virus from Firefox: Open Firefox, click ——- Add-ons —- Extensions. Find the adware/malware — Remove.

Remove Zeus Virus from Chrome: Close Chrome. Navigate to: C:/Users/!!!!USER NAME!!!!/AppData/Local/Google/Chrome/User Data. There is a Folder called “Default” inside: Rename it to Backup Default.

Restart Chrome. And Please review SpyHunter's,. Keep in mind, only SpyHunter’s scanner is free. If it detects a malware, you'll need to purchase its full version to remove it.

Type Regedit in the windows search field and press Enter. Inside, press CTRL and F together and type the threat’s Name. Right click and delete any entries you find with a similar name. If they don’t show up this way, go manually to these directories and delete/uninstall them:. HKEYCURRENTUSER—-Software—–Random Directory. It could be any one of them – ask us if you can’t discern which ones are malicious. HKEYCURRENTUSER—-Software—Microsoft—-Windows—CurrentVersion—Run– Random HKEYCURRENTUSER—-Software—Microsoft—Internet Explorer—-Main—- Random If the guide doesn’t help, download the anti-virus program we recommended or try our.

Also, you can always ask us in the comments for help!