A Django website for GITenberg
The goal of gitensite is to:
provide information about the GITenberg project
document the major areas of work of GITenberg
connect visitor with areas to contribute
list information about GITenberg books
distribute completed ebooks
This is a django/python project, so you are going to want to use some standard python dev tools.
.env and store your local db secret and other values there.
Virtual environments in python are a way of separating and reproducing the python package requirements.
From the root of the project
pipenv install -r requirements.txt
For every new terminal, or when returning to work on the project, you will need to run
We use Postgres.
To start a local db run:
./manage.py migrate ./manage.py createsuperuser
If you have modified the database, generate new database migrations:
And run them with:
Getting db data
To fill out data in your local db, you’ll first need to download and unpack the Project Gutenberg RDF metadata. you can run the provided
load_repos management command:
Then run ./manage.py load_repos <rdf_library_path>
<rdf_library_path> is the address where you unzipped the rdf metadata
There are currently three apps in the project:
content for containing templates and views for website pages
bookrepo [deprecated] for interacting with github and storing info about books
bookinfo for metadata for the repos
this website is deployed on Elastic Beanstalk. Install the awsebcli tool in it’s own py 3.7+ environment- it doesn’t play well with other packages, even boto from aws!
cd to the project directory and you should be able to deploy updates using
eb deploy [giten-site-new]
Remember to commit changes before deploying.
To install with Vagrant, follow these steps:
First install (on the local machine):
Then from the project directory run this command:
Then wait about 2 hours while it does its thing (loading the DB takes a very long time)
To log in:
Once logged in
The virtualenv and environment variables should be automatically loaded upon login.
Start the server
python manage.py runserver 0.0.0.0:5001
Use port 5001 since the Vagrantfile will automatically forward this port to the local port 5001. To use a different port, change the Vagrantfile on the host machine and run
vagrant up. Using the IP 0.0.0.0 will permit django to serve this on any IP. When running in vagrant the webserver doesn’t recognize
localhostaddresses as being from localhost since it is port-forwarded into the virtual machine.
Go to http://localhost:5001