For every user of Adobe Dreamweaver comes a time when it’s no longer feasible to work offline: sooner rather than later, you need access to a remote server, (either your staging or your production server, or both). If you are among the lucky ones whose staging or production environment runs on AWS EC2, Amazon’s high-performance low-cost compute cloud, you may hit quite a series of roadblocks before you get Dreamweaver CC/CC 2017 to communicate with your server instance(s). Here is a short and sweet tutorial on how to set up SFTP access in Dreamweaver without exposing your environment to the dangers of unsecured FTP.
In order to comfortably edit several dynamic websites in Dreamweaver at the same time you do not need several teting servers. Instead, you can set up virtual hosts on your existing Apache installation. This will work with any popular distribution including MAMP, WAMP and XAMP. Today we will show you how to set up virtual hosts on MAMP.
Adobe Dreamweaver CS5.5 sports some very exciting visual tools you can’t use with most sites unless you point it to a testing (or: staging) server. Unfortunately, many users struggle with nondescript error messages and frustrating demands of the app. While it works for some sites, it seems there is nothing you can do to make it work for others. Well, you can. Today we debunk the myths.
An update to this post explains How to Set Up Adobe Dreamweaver for Uploads to Amazon AWS EC2 without an FTP Account.