LearningZope3
Size: 1115
Comment:
|
Size: 1813
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
Creating zope3 applications is no easy task. This document comes out of a desire to help build a zope3 user community in support of SchoolTool and the CanDo competency tracking application which is being built on top of SchoolTool. |
Creating zope3 applications is no easy task. This document comes out of a desire to help build a zope3 user community in support of SchoolTool and the CanDo competency tracking application which is being built on top of SchoolTool. |
Line 7: | Line 7: |
The goal here is to keep things as simple as possible. Zope3 is extremely complex, and the learning curve is steep to say the least. I'm assuming that the aspiring zope3 developer here will be using Ubuntu Hoary, and running their zope instance from their home directly on port 8080. I'm using zope3 from the {{{zope3-lib}}} package available with Hoary. |
The goal here is to keep things as simple as possible. Zope3 is extremely complex, and the learning curve is steep to say the least. I'm assuming that the aspiring zope3 developer here will be using Ubuntu Hoary, and running their zope instance from their home directly on port 8080. I'm using zope3 from the {{{zope3-lib}}} package available with Hoary. |
Line 12: | Line 12: |
= Installing zope3 on Ubuntu 5.04 = | = Installation = |
Line 14: | Line 14: |
As root: 0. {{{apt-get install zope3-lib}}} 0. {{{cd /usr/lib/zope3x/bin}}} 0. {{{chmod +x mkzopeinstance}}} (this is needed because it does not come executable) |
As root: 0. {{{apt-get install zope3-lib}}} 0. {{{cd /usr/lib/zope3x/bin}}} 0. {{{chmod +x mkzopeinstance}}} (this is needed because it does not come executable) |
Line 19: | Line 19: |
As the developer from their home directory: 0. {{{/usr/lib/zope3x/bin/mkzopeinstance}}} 0. For {{{Directory}}} we will be using {{{zope3}}} 0. Choose a {{{Username}}} and {{{Password}}} which you will remember |
As the developer: 0. {{{cd ~}}} (to get to your home directory) 0. {{{/usr/lib/zope3x/bin/mkzopeinstance}}} 0. For {{{Directory}}} we will be using {{{zope3}}} 0. Choose a {{{Username}}} and {{{Password}}} you will remember That's all there is to it! You should now have a {{{zope3}}} directory inside your home directory containing an instance of zope3. = Starting zope = As the developer from your home directory, there are two easy ways to start your zope3 instance: 0. {{{./zope3/bin/runzope}}} 0. {{{./zope3/bin/zopectl start}}} For testing new code use {{{runzope}}}. Messages and debugging information will applear in the console, and you will be able to see when zope fails to start. Keep in mind that when using {{{runzope}}} the application server will stop when you close the terminal from which it is run, so to keep the server running use {{{zopectl start}}}. = User stories = = Application development steps = |
Motivation
Creating zope3 applications is no easy task. This document comes out of a desire to help build a zope3 user community in support of SchoolTool and the CanDo competency tracking application which is being built on top of SchoolTool.
The goal here is to keep things as simple as possible. Zope3 is extremely complex, and the learning curve is steep to say the least. I'm assuming that the aspiring zope3 developer here will be using Ubuntu Hoary, and running their zope instance from their home directly on port 8080. I'm using zope3 from the zope3-lib package available with Hoary.
Installation
As root:
apt-get install zope3-lib
cd /usr/lib/zope3x/bin
chmod +x mkzopeinstance (this is needed because it does not come executable)
As the developer:
cd ~ (to get to your home directory)
/usr/lib/zope3x/bin/mkzopeinstance
For Directory we will be using zope3
Choose a Username and Password you will remember
That's all there is to it! You should now have a zope3 directory inside your home directory containing an instance of zope3.
Starting zope
As the developer from your home directory, there are two easy ways to start your zope3 instance:
./zope3/bin/runzope
./zope3/bin/zopectl start
For testing new code use runzope. Messages and debugging information will applear in the console, and you will be able to see when zope fails to start. Keep in mind that when using runzope the application server will stop when you close the terminal from which it is run, so to keep the server running use zopectl start.
User stories
Application development steps
LearningZope3 (last edited 2008-08-06 17:01:05 by localhost)