Conference management site for FOSSY. Forked from Linux Australia's version at https://gitlab.com/laconfdev/symposion_app.
Find a file
James Polley b833b7d869 Order slots by room order first
* lca2018 has a situation where we have multiple slots starting at the
  same time, but ending at different times
* The headers of the timetable grid are sorted by room sort order
* In sqlite at least, ordering by start,order seems to implicitly
  resolve duplicate start times by looking at the other sort fields
  first, and will only sort on order if all other fields are identical

* This results in the slot that ends first going in column 1, which
  gets out of sync with the room listed in the header

* I can't figure out how to solve this in the database, so...

* Force the slots to be sorted by room order.
* Then, for each start_time, select out slots starting at that time
  and operate on them
* This both gets the slots in the right order *and* keeps multi-room
  slots with the right colspan. Yay!

* It's possible that this wouldn't be needed on some DBs which might
do the sorting differently.
2017-12-24 19:20:04 +11:00
docker Increase uwsgi buffer size 2017-10-05 00:38:05 +11:00
docs Fix duplicate room-slot in sample data 2017-10-15 15:31:20 +10:00
fixtures Rework navbar to have a consistent look with the static site. 2017-10-14 16:47:06 +11:00
pinaxcon Display Room for everything that's not break 2017-12-24 14:50:59 +11:00
static Make Emoji-capable fields greyscale 2017-12-23 02:27:40 +00:00
vendor Order slots by room order first 2017-12-24 19:20:04 +11:00
.dockerignore rename symposion-fixtures->symposion-tools 2017-10-16 20:05:30 +11:00
.gitignore Kludge tox to run flake8 2017-03-31 11:54:46 +11:00
.gitlab-ci.yml Test sphinx generation on every commit 2017-10-15 16:20:36 +10:00
constraints.txt dj-gapc-storage fix for num_retries went upstream 2017-09-15 10:06:49 +10:00
dev-env.sh DATABASE_URL as ENV_VAR 2017-06-24 15:59:46 +10:00
LICENSE added MIT license 2016-04-26 17:18:28 +08:00
make_dev_container.sh rename symposion-fixtures->symposion-tools 2017-10-16 20:05:30 +11:00
manage.py Initial commit of the PinaxCon demo site 2015-10-16 12:53:02 -05:00
README.rst Utilise multi-stage docker build for consistent dev/prod base 2017-10-04 20:43:01 +11:00
requirements.txt dj-gapc-storage fix for num_retries went upstream 2017-09-15 10:06:49 +10:00
tox.ini Use full imports not . 2017-04-29 14:28:48 +10:00
vendored_requirements.txt git subrepo pull vendor/registripe 2017-09-30 02:30:56 +10:00

symposion_app
=============

.. contents::

At this time, considerations have not been made to have the django project run
without additional infrastructure.

This can be configured in the future by switching the default
DEFAULT_FILE_STORAGE django default, and properly configuring django to load
subsequent configuration to switch this back to GCS on run in our testing
and production environments.

Login is a bit more complicated, the default flow redirects you out to a SAML
server, you can probably work something out with testshib.   But if you go to
/admin and log in, that will persist into /dashboard.


Required Configuration
----------------------

GCS
~~~

1. Set the bucket in settings.py
1. Store your Service Account JSON in a file
1. Set GOOGLE_APPLICATION_CREDENTIALS to your account file
1. Set GCS_BUCKET to your bucket name

SAML2
~~~~~

Please familiarise yourself with Shibboleth configuration and the general
flow of how to register a SP with an IDP.

If you send the SP metadata statically, validity time must be removed.

You will also need to register your IDP metadata here either statically or
remotely updated.

You may consider testing with testshib.

Configure signing and encryption keys, and configure them in the settings.py

Running a dev instance in Docker
--------------------------------

Assuming you have docker installed and working on your machine::
    ./make_dev_container.sh

will build you a container and run through the initial setup steps.
The last stage interactively creates a superuser account: you'll need
to interact with this for it to finish.

Once this has completed, you can hit http://localhost:28000/admin to
log into the admin interface. Once you're logged in,
http://localhost:28000 will take you to the dashboard.

Note that when you do this you're logged in as a superuser, so what
you see will be different from what a normal user will see.

Making migrations
~~~~~~~~~~~~~~~~~

If you make changes to the data model, you'll need to run "manage.py
makemigrations" to create a matching migration file. If you're on a
mac, or a system without python3, this can be difficult.

In such a case, you can use the above script to make and run a dev
container; then::
    docker exec -it symposion ./manage.py makemigrations


Running a dev instance in a VirtualEnv
--------------------------------------

Not all things are lovely, so we use constraints to force the versions we
we wish for without having to do anything ugly.  This may require a newer
version of pip than is packaged with distros virtualenv.

Note that this application is python 3 only so you must create your virtualenv
with a python3 interpreter.

- ``python3 -m venv venv``
- ``source ./venv/bin/activate``
- ``pip install -c constraints.txt -r requirements.txt``
- ``pip install -c constraints.txt -r vendored_requirements.txt``

Once your dev instance is up and running
----------------------------------------

Pre-post-start configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Now that we are ready to start the app, we need to do initial setup, start
it, perform voodoo string magic, run more database jingling voodoo, and then
we can start it up and start looking around and customising the application.

``./manage.py migrate``
``./manage.py runserver``

Now we hit up the admin interface, find `symposion_proposals` `proposalkind`
and add `Talk` slug `talk`, `Tutorial`:`tutorial`, and `Miniconf`:`miniconf`.

Shut down and now run:
``./manage.py populate_inventory``

Now you can run the system and see how it goes.

Admin tasks
-----------

Admin Credentials
~~~~~~~~~~~~~~~~~

To create a local administrator account run:

``./manage.py createsuperuser``

and enter your username, email and password. This can then be used to login to: (http://localhost:8000/admin).

Base Data
~~~~~~~~~

On initial creation and whenever you reset the database you must reload the
basic data. This data is stored in the /fixtures directory. You can load this with:

``./manage.py loaddata ./fixtures/{conference,proposal_base,sites,sitetree}.json``

And to load the base admin users:

``./manage.py loaddata ./fixtures/admin_users.json``

admin1:Inq4JVQyQvWnqXDI

admin2:w0jYMJsM4S+1zHds

admin3:XzynbNH9Sw3pLPXe

Creating review permissions objects
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

After conference Sections have been created, this command will add
Permission objects for those sections.

``./manage.py create_review_permissions``