gramps/gramps/webapp
2015-05-13 07:29:16 -04:00
..
databases Webapp: added databases directory; changed semantics of save_cache; 2015-05-11 12:36:35 -04:00
grampsdb DbDjango: use Gramps signals; to update, delete and add; 2015-05-11 16:53:43 -04:00
__init__.py
client.py Remove imports from __future__ module 2015-03-14 16:10:36 +00:00
connection.py Remove python2 specific code 2015-03-14 19:29:16 +00:00
context.py Update FSF address to current location. 2014-08-08 19:39:45 -07:00
dbdjango.py DbDjango: added load() for delayed init 2015-05-13 07:29:16 -04:00
empty.sql Remove use-bsddb3 configuration setting 2015-03-14 19:52:13 +00:00
example.sql Remove use-bsddb3 configuration setting 2015-03-14 19:52:13 +00:00
init_gramps.py Update FSF address to current location. 2014-08-08 19:39:45 -07:00
init.py Remove imports from __future__ module 2015-03-14 16:10:36 +00:00
libdjango.py DbDjango database works read-only in Gtk Gramps 2015-05-10 22:43:51 -04:00
Makefile Bring webapp in master up to Django, version 1.6.1 2015-05-08 10:54:35 -04:00
manage.py Bring webapp in master up to Django, version 1.6.1 2015-05-08 10:54:35 -04:00
modules_checkpoint.py DbDjango: method to checkpoint modules, to allow reloading Django 2015-05-11 21:17:57 -04:00
README.md mention 1.8 is LTS 2015-04-05 08:28:07 +10:00
reports.py Remove python2 specific code 2015-03-14 19:29:16 +00:00
settings.py django.setup() now required; bringing database up to date 2015-05-09 18:07:54 -04:00
shell.py django.setup() now required; bringing database up to date 2015-05-09 18:07:54 -04:00
shell.sh Bringing webapp up to date with python3 and django 1.6 2015-05-09 17:52:11 -04:00
urls.py Bring webapp in master up to Django, version 1.6.1 2015-05-08 10:54:35 -04:00
utils.py Replace cuni with str 2015-03-14 23:48:32 +00:00

UNSTABLE package for testing.

This webapp, is a web-based application that runs in your browser, and requires a server.

Many Gramps users would like to collaborate or share their genealogy data on the web. The main focus of this Gramps-based webapp is collaboration, allow users to easily move their genealogy data to the web to be seen, and edited with proper login and permissions, in a live, collaborative environment.

A prototype is on-line at http://gramps-connect.org/

Requires Django (version 1.7 supported until October 2015) (version 1.8 LTS supported until April 2018) ( https://www.djangoproject.com/ )

Webapp

  • 'gramps-webapp' packages are in progress...

For Testing only.

See https://www.gramps-project.org/wiki/index.php?title=Gramps-Connect for more details.

Some commands

$ cd /usr/lib/python3.4/dist-packages/gramps/webapp $ python manage.py help $ sudo make

Initialize Gramps Django site

PYTHON=GRAMPS_RESOURCES=../.. PYTHONPATH=../.. python3.4

  • update: grampsdb/fixtures/initial_data.json $(PYTHON) manage.py syncdb --noinput $(PYTHON) manage.py createsuperuser --username=admin --email=bugs@gramps-project.org $(PYTHON) manage.py createsuperuser --username=admin1 --email=bugs@gramps-project.org

  • grampsdb/fixtures/initial_data.json: init.py mkdir -p grampsdb/fixtures $(PYTHON) init.py > grampsdb/fixtures/initial_data.json

  • init_gramps: $(PYTHON) init_gramps.py # clear primary and secondary tables

  • run: $(PYTHON) manage.py runserver

  • sql: $(PYTHON) manage.py sqlall > gramps-sql.sql

  • dump: echo ".dump" | sqlite3 sqlite.db > gramps-data.sql

  • load: sqlite3 sqlite.db < gramps-data.sql

  • superusers: $(PYTHON) manage.py createsuperuser --username=admin --email=bugs@gramps-project.org $(PYTHON) manage.py createsuperuser --username=admin1 --email=bugs@gramps-project.org

  • backup: $(PYTHON) manage.py dumpdata > backup.json

  • restore: empty $(PYTHON) manage.py loaddata backup.json

  • initial_data: $(PYTHON) manage.py loaddata grampsdb/fixtures/initial_data.json

  • docs: mkdir -p docs $(PYTHON) graph_models grampsdb -i Person,Family,Source,Event,Repository,Place,Media,Note -o docs/primary-tables.png $(PYTHON) graph_models grampsdb -i Note -o docs/note-table.png $(PYTHON) graph_models grampsdb -i Media -o docs/media-table.png $(PYTHON) graph_models grampsdb -i Place -o docs/place-table.png $(PYTHON) graph_models grampsdb -i Repository -o docs/repository-table.png $(PYTHON) graph_models grampsdb -i Event -o docs/event-table.png $(PYTHON) graph_models grampsdb -i Source -o docs/source-table.png $(PYTHON) graph_models grampsdb -i Family -o docs/family-table.png $(PYTHON) graph_models grampsdb -i Person -o docs/person-table.png $(PYTHON) graph_models grampsdb -o docs/all-tables.png $(PYTHON) graph_models grampsdb -i Attribute,Datamap,Name,Lds,Tag,Address,Location,Url -o docs/secondary-tables.png $(PYTHON) graph_models grampsdb -i Person,Family,Source,Event,Repository,Place,Media,Note,Attribute,Datamap,Name,Lds,Tag,Address,Location,Url -o docs/prim-sec-tables.png $(PYTHON) graph_models grampsdb -i Person,Family,Source,Event,Repository,Place,Media,Note,Attribute,Datamap,Name,Lds,Tag,Address,Location,Url -o docs/prim-sec-tables.png $(PYTHON) graph_models grampsdb -i Person,Family,Source,Event,Repository,Place,Media,Note,Attribute,Datamap,Name,Lds,Tag,Address,Location,Url,NoteRef,SourceRef,EventRef,RepositoryRef,PersonRef,ChildRef,MediaRef -o docs/prim-sec-ref-tables.png

  • make-empty: echo ".dump" | sqlite3 sqlite.db > empty.sql

  • empty: rm -f sqlite.db sqlite3 sqlite.db < empty.sql

  • example: rm -f sqlite.db sqlite3 sqlite.db < example.sql

  • clean: rm -f sqlite.db rm -f *~ *.pyc *.pyo rm -f grampsdb/fixtures/initial_data.json