Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Website designs for both ironruby.net and ironpython.net

branch: master

This branch is 0 commits ahead and 0 commits behind master

Octocat-spinner-32 Properties Allow for website to be opened in VS2010, and run generate.bat on eac… April 20, 2010
Octocat-spinner-32 css Initial preparations of IronRuby site for first push February 05, 2011
Octocat-spinner-32 deploy Remove a bunch of unused/obsolete pages and change links to PTVS. May 15, 2013
Octocat-spinner-32 docutils directly check in docutils and jinja2 February 26, 2010
Octocat-spinner-32 images Make tools page point at new Python tools July 07, 2011
Octocat-spinner-32 jinja2 directly check in docutils and jinja2 February 26, 2010
Octocat-spinner-32 python Remove a bunch of unused/obsolete pages and change links to PTVS. May 15, 2013
Octocat-spinner-32 ruby Update IronRuby and IronPython websites for latest released version (… June 14, 2011
Octocat-spinner-32 silverlight Finish moving important content over from the IronPython CodePlex site November 15, 2009
Octocat-spinner-32 templates Make tools page point at new Python tools July 07, 2011
Octocat-spinner-32 .gitignore Create IronPythonNet submodule that points to ironpython.net gh-pages… May 14, 2013
Octocat-spinner-32 .gitmodules Create IronPythonNet submodule that points to ironpython.net gh-pages… May 14, 2013
Octocat-spinner-32 NEWRELEASE.rst Update IronPython.net for IronPython 2.7A1 July 20, 2010
Octocat-spinner-32 README.rst fix slash direction May 11, 2010
Octocat-spinner-32 TODO.txt Make required version of VS for IPyTools obvious, and add release not… May 03, 2010
Octocat-spinner-32 Web.Debug.config Allow for website to be opened in VS2010, and run generate.bat on eac… April 20, 2010
Octocat-spinner-32 Web.Release.config Allow for website to be opened in VS2010, and run generate.bat on eac… April 20, 2010
Octocat-spinner-32 Web.config IronPython Tools CTP2 release April 30, 2010
Octocat-spinner-32 clean Fix typo Jeff found, and add "./clean" script June 14, 2011
Octocat-spinner-32 clean.bat Depend on ruby and python exe's in the path January 30, 2011
Octocat-spinner-32 clean.py split browser download/examples page February 27, 2010
Octocat-spinner-32 deploy.rb Remove a bunch of unused/obsolete pages and change links to PTVS. May 15, 2013
Octocat-spinner-32 generate Update IronRuby and IronPython websites for latest released version (… June 14, 2011
Octocat-spinner-32 generate.bat Remove "Browser" link and stop wiping out deployment folder. May 15, 2013
Octocat-spinner-32 generate.py Remove "Browser" link and stop wiping out deployment folder. May 15, 2013
Octocat-spinner-32 index.html Force IE8 mode, change prerequisites link background color, and limit… November 09, 2009
Octocat-spinner-32 iron-websites.csproj Update website to include IronPython 2.7 Beta 2. February 07, 2011
Octocat-spinner-32 iron-websites.sln Initial preparations of IronRuby site for first push February 05, 2011
Octocat-spinner-32 ironpython-blog-template.xml Add IronPython blog template before modifying it. March 04, 2012
README.rst

IronPython.net and IronRuby.net

Quickstart

  • Open iron-websites.sln in 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 generate.bat for details.

If you prefer the command-line:

  • Generate HTML files for both ruby and python in-place and stage for deployment:

    generate.bat
    
  • See "Deploying" section below for instruction on how to get your change checked in and pushed to the live website.

Overview

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 python and ruby directories.

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.

Updating content

The content of each website is represented by reStructuredText, a plaintext markup syntax. Each file is processed first by jinja, and then by RST to generate a HTML file to disk.

Generating HTML files

The logic for generating the HTML files is in generate.py, including navigation, style, and template info. The simplest way to generate the HTML files is to just use:

generate.bat

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 -python or -ruby flags:

Usage: python generate.py [-python|-ruby|-h]

View website

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 deploy.rb:

ruby deploy.rb

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:

  1. Push your changes back into your own fork.
  2. Send a pull-request, which effectively starts a code-review.
  3. When jschementi signs off on the changes, they'll be pulled into the main repository, and then you're ready to deploy.

Deploying

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.

Something went wrong with that request. Please try again.