GitLab

- forgot to add both those things
- from test deployment

Resolve "Serve GeoJSON alongside API requests"

Closes #34

See merge request !23

- we meet again my old nemesis

- (x,y) point where the Facility is located
- Pretty map added to admin interface

- modify the db engine
- new package req's
- Modify the Docker build process

Resolve "Add tags for various types of food"

Closes #40

See merge request !22

- named product_tags so that it can scale to non food related places
- ie. whatever the facility produces to the consumer can be tagged as
such

Closes #40

- using some great libs
- it just works
- needs docs

- oops forgot to remove this one

Closes #36

- optional, enforced with RegexValidator

Resolve "Add the ability to set an alert message to the front page"

Closes #41

See merge request !20

- thanks git merge

- get the list of alerts
	- todo: remove alerts that have expired or
		are no longer in effect

- plus a correction in Alert model doc

- An alert is a message we display to clients in case of some event
- start/stop date and time
- message
- urgency tag for colorization purposes

- HyperLinked is the only different one, include some more words

- really simple since everything is basically ModelSerializers

- did not seperate third part from Django

- also clean up some things that are now defaults

Resolve "Support for facility categories"

Closes #16

See merge request !19

- require a category for every facility

"""
api/<file>

short description

helpful link
"""

- oops that slipped in

- also settings/ added
- also renamed whats_open to whats-open to be consistant with repo name
- updated docker and CI accordingly

- it may come back don't worry but it was severly outdated

- used to ensure that we are running the latest packages when possible

Resolve "Serve physical address of restaurants"

Closes #38

See merge request !18

- starting the commenting process
- cleanup = removing stuff that doesn't actually do anything

- more or less me testing things, will get modified or removed in the future

- this is probably from when we were rolling our own API
- this no longer does anything of use and is in fact, confusing to
new contributers

- before they existed but were not displayed
- apparently the variable names need to be the same and they were not
	- this fixes that

- some things that were bugging me that I think can be agreed
upon as overall good

- get out of here microsoft

- This got really annoying in development to remember to go to /api all the time
- Potentially in the future we will build a test landing page on / to test that
the API works instead of having to rely on third party tools or just manual clicks
	- Until then, this will make life easier (imo)