Pylons is becoming Pyramid which is based on repoze.bfg framework. Good to know if one of the larger frameworks are needed in the future.

see also python/templates.txt

if using the site templates frequently (and once they stabalize) would be nice to have a paster

paster serve --reload development.ini

view in firefox: | http://localhost:5000/

if no controller has been created, will get a 404

remove public index.html (otherwise it will be default) cd (package)/public #rm index.html bg.png pylons-logo.gif hg rm personnel/public/bg.png hg rm personnel/public/pylons-logo.gif hg rm personnel/public/index.html

#make images and css directories in public: cp -R /c/external/sites/charlesbrandt.com/templates/pylons/public/css public/ #import other default template files: cp -R /c/external/sites/charlesbrandt.com/templates/pylons/templates/* templates/ cp -R /c/external/sites/charlesbrandt.com/templates/pylons/controllers/* controllers/

#be sure to choose if you want the sqlalchemy version (model-sa) or non-sa: cp /c/external/sites/charlesbrandt.com/templates/pylons/model/* model/

update the imports in the controllers you plan to use

update lib/helpers.py to import webhelpers cp /c/external/sites/charlesbrandt.com/templates/pylons/lib/* lib/

sudo easy_install virtualenv

make sure model files have been created cp ../personnel-try1/personnel/model/__init__.py personnel/model/

paster setup-app development.ini

#make sure development.ini is using an open port: vi development.ini

update routes

python setup.py develop

have done this essentially with the main page for contextiskey.com any other modifications should be requested [2008.03.15 10:40] put "hello world" in the middle of the cloud

maybe use inkskape to clean it up a bit? (raster can look cool though)

file:///media/Charles/personal/projects/journal/browser/interface/slice.html

virtualenv --no-site-packages personnel-virtual

cd personnel-virtual

source bin/activate

easy_install pylons easy_install formalchemy

paster create -t pylons_fa

cd personnel

hg init cp ../.hgignore .

hg add hg ci -m "new repo for new project"

spent a while today looking into tosca widgets, dbmechanics and db sprockets doesn't quite seem to be in the same place that form alchemy is

hg clone http://toscawidgets.org/hg/tw.forms/

#2009.02.20 13:29:59 admin@one:/c/downloads/python hg clone http://toscawidgets.org/hg/ToscaWidgets/

downloading and trying out: sudo easy_install -zmaxd . ToscaWidgets sudo easy_install -zmaxd . tw.forms

paster setup-app development.ini

• The MetaData object Pylons uses is defined in model/meta.py so is accessed here as meta.metadata whereas in the previous chapter it was defined in the same file so the examples just used metadata.
• Pylons generated the init_model() function when the project was created. It gets called after the engine has been created each time your application starts from config/environment.py to connect the model to the database.

Caution!

Pylons generates a project to use SQLAlchemy 0.4 but many users will want to use the newer SQLAlchemy 0.5 described in Chapter 7. They are very similar but the transactional=True argument to orm.sessionmaker() in init_model() is deprecated. Instead you should specify autocommit=False. This has exaclty the same behaviour but will not generate a deprecation warning.

change: model/meta.py # SQLAlchemy session manager. Updated by model.init_model() Session = scoped_session(sessionmaker(autoflush=True, autocommit=False))

#then offline in /c/downloads/python sudo easy_install -f . SQLAlchemy

cd /c/downloads/python/pylons-eggs sudo easy_install -zmaxd . easy_install -zmaxd . "SQLAlchemy >= 0.5, <=0.5.99"

could use a little cleanup, but is available somewhat manually at this point via:

also downloaded to (see also) /charles/downloads/reference/mako-documentation.html

currently reading pylons_book here may want to point pylons-book.txt here

Jonathan Vanasco Wed, 24 Sep 2008 08:20:09 -0700

I've had to do this before...

you'll want to rename the appropriate files / directories , and then replace all the module name instances in your project

ie: if your project is named ASDFGHJK , then you'll need to rename: /ASDFGHJK /ASDFGHJK/asdfhjk /ASDFGHJK/asdfhjk.egg-info

then do a s/ASDFGHJK/? on the files

there are lots of

import ASDFGHJK from ASDFGHJK import

if you're using a mac, TextWrangler has a great find/replace function that works on directories

if you're using subversion for version control, i generaly like to do it like this: 1- rename files 2- commit 3- find/replace text 4- commit

if you're using git or mercurial, i think you can do the commits in one step. svn needs them in two though.

see also dreamhost pylons-deploy.txt

forms are closely related to models

you'll need a way to persist the data.

if it's not tied to a specific directory of content, then it should probably be stored in a database of sorts to allow data lookup.

with pylons that probably means using sqlalchemy

if you didn't enable it in your project to begin with, you'll need to do so now following: | http://wiki.pylonshq.com/display/pylonsdocs/Using+SQLAlchemy+with+Pylons

set up meta.py set up model

init_model in __init

configure database string in config (development.ini) sqlalchemy.url = sqlite:///%(here)s/jb-dev.sqlite

environment.py websetup.py

don't forget! paster setup-app development.ini

forms are closely related to models

you'll need a way to persist the data.

if it's not tied to a specific directory of content, then it should probably be stored in a database of sorts to allow data lookup.

with pylons that probably means using sqlalchemy

if you didn't enable it in your project to begin with, you'll need to do so now following: | http://wiki.pylonshq.com/display/pylonsdocs/Using+SQLAlchemy+with+Pylons

set up meta.py set up model

init_model in __init

configure database string in config (development.ini) sqlalchemy.url = sqlite:///%(here)s/jb-dev.sqlite

environment.py websetup.py

don't forget! paster setup-app development.ini

to start working with forms, you will new to methods to a class... one to show the form, one to handle the form.

you will also need to import the validate code. (formencode)

layouts and other form validation can be stored with other model code (I'm torn if that is more UI or model validation... pylons seems to go with model validation).

Pylons comes with an easy to use validate decorator, imported by default in your lib/base.py. Using it in your controller is pretty straight-forward:

#this gets the validate decorator. from pylons.decorators import *

to start working with forms, you will new to add methods to a class... one to show the form, one to handle the form.

you will also need to import the validate code. (formencode)

layouts and other form validation can be stored with other model code (I'm torn if that is more UI or model validation... pylons seems to go with model validation).

Pylons comes with an easy to use validate decorator, imported by default in your lib/base.py. Using it in your controller is pretty straight-forward:

#this gets the validate decorator. from pylons.decorators import *

once you have a basic pylons instance created, there are a few things that need to be configured for most sites to get started.

This seems beyond the scope of a basic installation document, but nonetheless should be documented.

from root of project:

paster controller name-of-new-controller

start with a main controller:

for simple sites this may be enough. (i.e. sites with only one level deep) for these sites it seems like over kill to make a separate controller for each page if there is really only an index page for each one.

some might argue to just stick with a templating system for a simple site, but just incase needs grow in the future, it is nice to have a framework in place. Pylons doesn't add a lot of bloat to even a simple site... so why not. Also keeps things consistent across projects.

make images and css directories in public:

remove public index.html (otherwise it will be default)

add standard templates

update routes

paster controller name-of-new-controller

start with a main controller:

for simple sites this may be enough. (i.e. sites with only one level deep) for these sites it seems like over kill to make a separate controller for each page if there is really only an index page for each one.

It may be adequate to stick with a template system (i.e. manual static, sphynx, webby) for a simple site. On the other hand, if you're comfortable with python and needs grow in the future, it is nice to have a framework in place. Pylons doesn't add a lot of bloat to even a simple site. A framework keeps things consistent across projects.

paster serve --stop-daemon

this picks up where installation leaves off

overlap is in starting server:

paster serve --reload development.ini

figure out how to run server as a daemon pass --deamon to paster serve: paster serve --daemon --reload development.ini paster serve --daemon --reload production.ini

pylons informational links | http://www.google.com/search?hl=en&q=pylons+based+blog&start=20&sa=N | pylons based blog - Google Search | http://blog.micampe.it/articles/2006/11/26/a-tale-of-pylons-python-and-fastcgi-on-dreamhost | A tale of Pylons, Python and FastCGI on Dreamhost | http://blog.micampe.it/ | Michele Campeotto | http://diffle-history.blogspot.com/2007/12/pylons-and-django.html | Diary of a Failed Startup: Pylons and Django | http://my.opera.com/WebApplications/blog/index.dml/tag/Pylons | Pylons - Web Applications Blog | http://truefalsemaybe.com/2008/06/authorization-in-pylons-with-repozewho-part-1-htaccess/ | Authorization in Pylons with Repoze.who (Part 1 - HTAccess) | http://mgratzer.topmind.at/2007/07/04/pylons-framework-as-ruby-on-rails-opponend/ | mgratzer’s Blog » Blog Archive » Pylons Framework as Ruby on Rails opponend | http://www.rexx.com/~dkuhlman/pylons_quick_site.html#creating-an-application | Pylons Quick Site Development | http://www.pylonscasts.com/ | Welcome :: Pylons Screencasts | http://swik.net/pylons | pylons - SWiK | http://www.devchix.com/2007/08/16/restful-thoughts-on-a-web-20-python-project/ | » RESTful Thoughts on a Web 2.0 Python Project - DevChix - Blog Archive | http://wiki.pylonshq.com/display/pylonscookbook/A+Pylons+Controller+with+Trac+as+WSGI+Callable | A Pylons Controller with Trac as WSGI Callable - Pylons Cookbook - PythonWeb | http://wiki.pylonshq.com/display/pylonsdocs/Form+Handling | Form Handling - Pylons Official Docs - PythonWeb

looking in to a CRUD like scaffolding generation script for pylons. didn't see much out there. maybe it's best just to create manually, so you don't have to weed out unnecessary code.

just installed pylons on ubuntu