IronPython.net and IronRuby.net
iron-websites.slnin Visual Studio 2010 as "Administrator" That will setup IIS to serve the website from
http://localhost/iron-websites. Building the solution generates the website for viewing; see
If you prefer the command-line:
Generate HTML files for both ruby and python in-place and stage for deployment:
See "Deploying" section below for instruction on how to get your change checked in and pushed to the live website.
IronRuby.net and IronPython.net
share the same infrastructure; basically the same CSS, HTML templates, images,
HTML generation and deployment scripts. The only difference are the content,
which are stored in the
Getting the source
If you intend to submit a change to the website, please fork this repository and follow the instructions on how to get the source code locally. This will make it really easy to check-in your changes to your own private copy, and then send a pull-request to get your changes back into the original repo.
Generating HTML files
The logic for generating the HTML files is in
navigation, style, and template info. The simplest way to generate the HTML
files is to just use:
This will generate HTML for both sites and stage it for deployment. If for some
reason you only want to generate HTML for a specific site, you can use the
Usage: python generate.py [-python|-ruby|-h]
After generating the website, you can view it by going to the language-specific directories:
Staging for deploy
If you used
generate.bat, you already have staged the sites for deployment.
Otherwise, just run
The websites are then staged at:
These directories are ready to go online, with all dependencies self-contained.
Checking in your changes
Before you deploy these changes to the live website(s), they must be checked into the main repository, or else you risk someone else deploying changes which overwrite yours. Here's the simple steps:
- Push your changes back into your own fork.
- Send a pull-request, which effectively starts a code-review.
- When jschementi signs off on the changes, they'll be pulled into the main repository, and then you're ready to deploy.
Currently deploying is only a manual process, so the completion of the code review will also include pushing the site live. Please let jschementi know if the changes are urgent.
Please ask jschementi if you have any additional questions.