How to do development

Testing out changes

Edit files in the directory/disk image from which you start the VM. You can do this from within the vagrant ssh session or outside it.

then stop and rerun paster serve --reload development.ini sometimes has some lag in showing changes cant figure it out but hard shift-f5 web page refreshes seem to help

(Patrick has found he hasn’t had to restart server. If anyone can figure this out that’d be cool.)

Then you should be able to see your changes at your local URL, which should be http://lesswrong.local:8080 or http://lesswrong.local:3000

Committing changes

Use git. Submit your changes in a separate branch, and we can then merge them into the master branch which contains commits we've actually submitted to the live site.

Submitting changes to the tech team for comment and/or pushing to the live site

Use git. Submit your changes in a separate branch, and we can then merge them into the master branch which contains commits we've actually submitted to the live site. Alert the tech team to this by posting in https://github.com/tog22/issues or emailing Peter at peter@peterhurford.com