Last modified 4 years ago Last modified on 05/17/13 14:28:30

Set up a Development Environment

To develop for the Transition Network, you need to be able to run an independent copy of the website that only you will change. There are a few alternative ways you can do this:

Only 1 is complete. 2-4 need more work.
  1. 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.
  2. 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.
  3. 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!
  4. 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.

All of these methods have advantages, and the one you choose will depend on your preferences as a developer. Have a read through all of them, pick the one you think will get you going the quickest. Once you've followed one of the above guides, you should have an independent, functioning Development copy of the site where you are able to develop the site through both its UI (direct in the browser) and its codebase.