Update dev instance deploy script

- We have a flatpages fixture to add in
- Need to let the script exist in the docker context so it can be run

Correct variable name to reflect what it's naming

IT's not the container name, it's the image name. Fix the name to be
less confusing.

Improved handling of static/build and css generation

When the container is mounted, the local contents of . obscure
/app/symposion_app in the image.

Generally speaking, this is handy for development, as it means that
local changes are detected and used immediately without needing to
restart the container.

However, it breaks in the specific case of the sass->css
generation. Prior to this change, the css is generated only after the
first time a page is hit. The generated file is placed in
static/build; however, due to the obscuration, this generated file
isn't visible to the running process.

The next time the container is built, the pre-existing static/build
directory is copied into the container as it's being built; then,
later, that version is what gets served.

This change adds the needed libraries to pre-generate the css as part
of the image build, and runs compilescss to do this, prior to the
collectstatic step.

It also adds a second collectstatic into the make_dev_container
script, so that the visible static/build directory should ahve the
same contents as the obscured static/build directory. It also expands
the .dockerignore file to make sure these files aren't copied into the
image in future.

I'm not sure if this is the right thing to do, as changes to this
directory will be ignored, which could be confusing. Perhaps never
being able to see these generated files is better?

Modify dependencies to suit debian stretch

The python:3.6 tag now points to stretch.

Changed the name of the base image to make this more explicit.

Don't populate inventory yet

We'll turn this back on once we're ready to start testing inventory for LCA2019

Show chair for session on main overview page

Plus keep it a link so opt out is not impossible.

Fix bulk action

Bulk action marks printed + schwag, but as print is automated and
happens after checkin is flagged, we should only set checkin and schwag
and print will happen.

Allow accessing URL to generate boarding pass

Only needed some code fixups to function

Force upnprint badge

So automation can try again

Disallow profile updating if user is checked in

It gives a flash and pops the user back to dashboard.

Expand admin ui for checkins to be useful for admins

... also (and this really should be another commit, I am a horrible
person) change name of exception text fields

Show attendees shirts in overview

So schwag can be given out

Add last minute fixes to flow

Exception text storage and check in needs to be sepearte to badge.

Linkify the rego-code in overview view

Should make checkin of lookups easier, links to the page just after
boarding pass scanning

Add regex validation [A-Z0-9]{6} for input

Don't block submition, but give the user a red bar.

Also a link to overview.

Esp if it is 5+ sec to load, we don't need it 90%+ the time, don't page
through it in the scan print workflow.

Convience redirect on .conf/checkin

Send voli's to the overview, and everyone else to what we want from
them.

Base flow for checkin scanning

It's ugly... But it should do the job.

Ref #40

Add overlay badge support

Support so print can print only important text.

SVG modified to use display:inline/none based on overlay True/False and
a symlink to make it easy to change to a completely seperate svg if that
is not optimal.

SVG added layers to split text and graphic so graphics can be easily
hidden and printed.

Closes: #38

Need to list items per-user

Without this important line, each user gets the same manifest. not helpful.

Decode the image so it can be re-encoded

#sigh

Refactor bpass build/send code

* Pull out the bits that prepare and build the bpass
* Make them not require a request object
* so that we can now call this code from another context

Add track to schedule JSON

Include the track of the slow in the schedule JSON so the miniconf can be identified.

Enhance boarding poass processes

* Add a note about the creation date of boarding pass
* Add a link to ticket review page
* Try to handle some of the expected errors in the boarding pass
sending process
* don't just 502, try to handle the error and move on.

Remove the personalised bits of session chair display

- The schedule grid page is ridculously database-query heavy and hence
terribly lacking in perfmantitude.
- Caching can help with this, but the caching implemention at present
is not user-aware. If one user looks at the page, they'll get a
"YOU" in all the places they're chair and something else everywhere
else - and then everyone will see that for the next 600 seconds,
then YOU will become someone else
- to avoid this, remove the request.user-specific bit of the template

If no boardingpass, make one

- Use the first template in the system
- If there's no template, use /tickets/review as it at least gives
- people an overview of what they've paid for and warns them of
missing categories

Don't require login to view qrcode

* The qrcode contains no information that isn't in the URL you used to
access the code, so information is being leaked
* Allowing unauthenicated access lets people see the image in their
mail client

Not ideal. Let's revert this later and think of something better next
year - perhaps spending some more time researching best practices on
images in email..

Switch to png as a plain boring attachment

In the body of the email, we can load the image direct from the
site. Prolly gonna fail a lot but at least it's a loud known visible
failure

Revert to fixed string in email, for easier substitution

Harder to swap it out when it changes every time..

Update badge rendering to reflect actual render

* Switch to showing the PNG version by default, as this reflects what
will actually be rendered and sent to the printer
* Include the greyscale filter
* Include the twemoji font we'll use for rendering the badges

Quick and dirty voucher use report

Dumps a list of voucher code, invoice id, invoice details in a listreport.

Make narrow-screen schedule details more distinct

In the narrow view, lots of details that aren't in the normal view
appear to compensate for not having clear row/column headers any more.

However, all the detail can look very same-same; this tweak makes rooms and end times more distinct.

Session chair info is made always italic, and a label is added to make
it clear that this person is not the speaker.

Add admin action to update slot names

* The slot object updates its name every time it is saved
* But sometimes its slotrooms are changed underneath it, and so the
name can become out of date
* This method is a simple way of updating the names for all the slots

Chrisjrn/session chair (#94)

* Adds session_detail page

* Adds session chairing information to the schedule grid

* Adds session_list.html

* Nicer volunteer text

Conflicts:
pinaxcon/templates/symposion/schedule/_grid.html

Conflict and migration performed by Sachi King <nakato@nakato.io>
Emoji changed, lca2017_tags to lca2018_tags, remove needless dependency
on django-user-account, use request instead like the remainder of the
calls n the template do anyways.

Remove blocktrans from a number of texts as they break {{ templating }}
and we don't translate anyways.

Modified-by: Sachi King <nakato@nakato.io>

Add support for a "ready for boarding" group

This allows for the boarding functionality to be safely tested with
just a subset of users first. Once you're ready to go live Fur Reals,
just delete the group and all users will become eligible.

Create regidesk app

Shows summary of all attendees with a paid ticket, including
boarding_pass status.

Currently, regidesk allows staff with the requisite permission the
ability to view the checkin status of attendees, and email the user
their boarding pass email.

Included is a view for the user to retrieve their own QR code (in case
they got the plain-text version of the email, they can use this to
download an image to their phone for faster checkin)

git subrepo clone git@gitlab.com:LCA2018/registrasion-desk.git vendor/regidesk

subrepo:
subdir: "vendor/regidesk"
merged: "a8096d0"
upstream:
origin: "git@gitlab.com:LCA2018/registrasion-desk.git"
branch: "master"
commit: "a8096d0"
git-subrepo:
version: "0.3.1"
origin: "???"
commit: "???"

More consistent color-coding for talk status buttons

- there's no btn-default, switch that to btn-primary
- consistently use info for standby, primary for undecided, success
for accept and warn for rejected

urlize abstracts

I've looked through the database and I can't find any accepted
proposals that actually contain anything to linkify - but I've had
several requests from people that I think are reasonable, things like
being able to link to their project (we ask them to provide a project
url but we don't use that link)

This seems like a reasonably fast way to let those people add a
link. We still have to manually accept changes to their proposal so we
have a chance to look at the content of the url if we want.

The urlize filter adds rel=nofollow to the link automatically.

Modify limits report to include category inclusions as well

* A TimeOrStockLimit limit can apply a limit to a whole category, or
to specific products
* This report was only counting the products directly listed
* Take advantage of the new all_products property to include the
products indirectly listed as well as those directly listed

Add an all_products property to FlagBase

It's common to need to query the fill list of products covered by a
Flag - whether directly, or by being in an included category.

Add an all_products property which does this.