Changes between Version 5 and Version 6 of website/devEnvironment
- Timestamp:
- 05/17/13 14:28:30 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
website/devEnvironment
v5 v6 9 9 1. [[website/devEnvironment/workstation|Through a webserver installed on your workstation]]. If you've already got an Apache/PHP/MySQL server set up on your workstation, this could be the easiest way to go. WAMP (Windows) and MAMP (Mac) are pretty easy to install if you haven't, and LAMP-setup is well documented for popular Linux distrubutions. If this looks feasible, and you can get it working, it results in a nice light-weight development environment. 10 10 2. [[website/devEnvironment/otherVM|Through another webserver you have access to]]. If you're a web developer with access to a LAMP server somewhere else on the internet, you can also use this, with just a couple of extra steps involved beyond method 2. 11 3. [[website/devEnvironment/premadeVM|In a pre-made development environment]]. Run a read-made development environment from a virtual machine on your workstation. Not recommended if (a) you're already very comfortable with your development tools, or (b) you have a workstation with less than 4GB RAM. 11 3. [[website/devEnvironment/premadeVM|In a pre-made development environment]]. Run a read-made development environment from a virtual machine on your workstation. Not recommended if (a) you're already very comfortable with your development tools, or (b) you have a workstation with less than 4GB RAM. Recommended by the deeper developers however! 12 12 4. [[website/devEnvironment/aegir|Directly on Transition Network's Aegir platform]]. Relatively easy to set up, but still a bit experimental. It's basically a variation on method 3, except you're using the Transition Network's Aegir server to host your development platform. 13 13