If you EC2 (http://aws.amazon.com/ec2) then read on otherwise you can
ignore all of this. I've prepared a Django on Gentoo (DoG) Linux
image for EC2. This is built on the base Gentoo image that I posted
about previously. I added a whole bunch of goodness to run Django.
Included are a whole set of startup scripts that build up the system
and initialize the application. Although this is a long post, please
be sure to read the "Special Instructions" if you want to get maximum
benefit from this image.
AMI ID: ami-29947140
AMI Manifest: eminent-ami/django/10/image.manifest.xml
About this AMI
--------------
* Published by Eminent Consulting Group ([http://
www.djangoconsulting.com]).
* Django on Gentoo (DoG) Linux System
* This image contains a Gentoo Linux 2007.0 installation with
Django application support.
* Gentoo Linux
- dhcpcd,
- logrotate,
- all packages are recent and updated,
- AMI tools have been installed and are fully working
even for
volume imaging,
- EC2 meta-data is fetched from 169.254.169.254 into
/var/spool/ec2/
meta-data,
- EC2 meta-data and user-data include files in
/var/spool/ec2/meta-
data and /var/spool/ec2/user-data respectively,
- Disabled password authentication in
/etc/ssh/sshd_config
- Modifications to startup according to Amazon
documentation
- the portage tree has been bind-mounted to
/mnt/usr/portage to
preserve space on the root file system,
- the /tmp directory has been bind-mounted to /mnt/tmp
to preserve
space,
- the /var/lib/postgresql directory has been
bind-mounted to /mnt/
var/lib/postgresql,
- the root home directory contains a dev-copy directory
that is
needed to build the volume images,
- all packages have been recompiled to correctly
respect the Xen
environment.
* Django
- Apache 2.2.4 installed (not in startup) and
configured with
Python support,
- Python 2.5.1,
- mod_python,
- Postgresql 8.2.4 (not in startup),
- psycopg2
- Subversion 1.4.3 (no repositories are setup)
- Django trunk version checked out into
/home/django/django and
installed as normal into the Python site-packages directory (django-
admin.py copied to /usr/local/bin/),
- Support packages: libjpgeg, zlib, freetype2, zip, and
unzip,
- Python packages: PIL 1.1.6, FeedParser 4.1, Markdown
1.6, Unipath
0.1,
* This image contains the following daemons / services:
- local
- net.eth0 / net.eth1
- netmount
- dhcpcd
- sshd
- syslog-ng
- vixie-cron
- apache 2 (disabled by default)
- postgresql (disabled by default)
Special Instructions
--------------------
Sample Application
------------------
The instance can accept a set of user data parameters for setting up
an application. I've provided a default application to indicate the
process for creating your own application setup scripts. If you run
the instance with the following parameters it will startup a complete
running default application based on the Django Vote tutorial.
ec2-run-instances ami-29947140 -k gsg-keypair -d "app=mysite-
setup&url=http://s3.amazonaws.com/eminent-ami/mysite-setup.tgz";
Once the server is up and running you should be able to to enter the
public hostname (starts with ec2) into your browser and view the
application. The Admin section of the application is in the location /
admin. Credentials are:
Username: admin
Password: password
The default application will be installed into the /home/django/mysite
directory. The setup scripts for the application will get installed
into /opt/mysite-setup. The Admin media directory and the mysite
media directory are both symbolically linked to the /var/www/mysite/
htdocs directory.
Postgresql Configuration
------------------------
Postgresql is installed but there is no database setup and the service
is not started by default. The database directory /var/lib/postgresql
is bind mounted to /mnt/var/lib/postgresql. The configuration files
have been configured according to the Gentoo Postgresql How-To (http://
gentoo-wiki.com/HOWTO_Configure_Postgresql) document with the included
logging changes. Configuration files are symbolically linked in from /
etc/postgresql for those that like that sort of thing. A sample of
creating and restoring the database can be found in the mysite-setup
scripts for the Sample Application. Write Ahead Logging (WAL) is not
implemented, but would be necessary implementation detail for most
sites.
Creating an Application Setup Package
-------------------------------------
The mysite-setup package (http://s3.amazonaws.com/eminent-ami/mysite-
setup.tgz) is the base requirements for your own application setup
package. At a minimum you are required to have a bin directory with a
file in it called setup.sh. Within the setup.sh script you are free
to put any setup instructions you need or pass those tasks off to
other scripts written in the language of your choice.
Currently the configuration of this image requires that the
application setup package is publicly available and downloadable via
curl (see the application-setup.sh script). I plan to add security
implementation details in the future.
What's New?
-----------
The following changes were made on 2007-06-01.
* Initial release
Thanks
------
Grateful thanks to Geert Bevin for his initial Gentoo image.
Special thanks to RightScale for ideas and guidance provided by their
startup scripts
Michael Trier
Eminent Consulting Group
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
