126
edits
| Willipedia is now back online as of 5/5/2019 |
| It has been several years since Willipedia closed. Please help get it updated! |
| Go to the Willipedia 2.0 Project to learn more. |
Changes
Updated for petunia as devel server...
[[Category:How-To]] [[Category:Computers]] [[Category:WSO]]
[http://wso.williams.edu WSO's web site] is a work in progress. You can always see "the next step" at http://wso.williams.edu:3000, where the latest "stable" (stable being a relative term) version of the next update to the site lives. If you're impatient about the new facebook, or you know web design or Ruby, or if you just want to see how it's done, you're welcome to check out a copy of the code and go to work. This page will tell you how to get started.
== Get a Subversion account ==
Email root at wso to get an account and password so that you can checkout a copy of the code from our Subversion repository. You'll need this when running any of the svn commands below.
==SSH to WSO==
Once you've logged in with SSH, you're ready to check out your very own copy of the WSO code. In your home directory, or wherever you'd like to keep your copy of the WSO site, run the following command to use Subversion to check out the code. (Don't forget the dot at the end!) This will spew a whole log of output onto your screen, listing all the files it's checking out. You can replace "wso-devel" with whatever name you want for your local copy of the code.
svn co filecheckout svn://wso.williams.edu/var/svnwso-on-rails/wso trunk wso-devel
Now change directory into the code directory:
If you see something like the following, then you're in business.
=> Booting Mongrel (use 'script/server webrick' to force WEBrick...) => Rails application started starting on http://0.0.0.0:3001your_port => Call with -d to detach => Ctrl-C to shutdown server; call with --help for options [2006-11-29 21** Starting Mongrel listening at 0.0.0.0:15:31] INFO your_port WEBrick 1** Starting Rails with development environment...3 ** Rails loaded.1 [2006-11-29 21:15:31] INFO ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. ruby 1INT => stop (no restart).8 ** Rails signals registered.5 HUP => reload (2006-08-25without restart) [powerpc-darwin8.8 It might not work well. ** Mongrel available at 0.0.0].0:your_port [2006** Use CTRL-11-29 21:15:32] INFO WEBrick::HTTPServer#start: pid=9210 port=3001C to stop.
Before breaking out the champagne, we need to check to see that the server actually works. Unfortunately, you can't just pop open a web browser and surf to your new site. WSO's servers are behind a firewall. The firewall only allows connections on certain ports. Yours is not one of them.
Of course, if it doesn't work, please describe your problem on [[Talk:How to hack on the WSO siteweb development]].
Now, you can change a file in wso-devel, and the change will show up on your development server at this address the next time you reload the page in your browser. Sweet.
==Making changes==
Nice work getting this far. So now you actually want to ''do'' something with the code. For now, come to a WSO meeting Thursdays at 10:30pm in the vicinity of TCL 217a, or email wso-staff@wso.williams.edu with questions/interest. CurrentlyWith the new Facebook nearing completion, our next big project prospect is the new facebookrewriting old PageKit services (Factrak, Jobs, RideBoard) in Ruby on Rails.
It's a good idea to run an update every so often so that your local working copy picks up changes that other people have made. Change directory into your wso-devel directory and run
Email root at wso if you'd like to change the WSO site, add a new service, or fix a bug. If you get the go-ahead, you're in good shape, so go to work. Once you think your change is ready for the world, you'll need to get permission to commit add your changes to our code repository, where it will be tested and deployed. Email root at wso about that. They'll take care of you. == To Do == * Pictures are broken on the front page...
