search

KatrinaHoffert / EatSafe

An app for finding safe places to eat
Other
2 stars 2 forks source link

Admin Interface #144

Closed garmu closed 9 years ago

garmu commented 9 years ago

CRUD

KatrinaHoffert commented 9 years ago

Is this something we want to put back on the table? I think it'd be doable if I devote time to it. The actual ability to add and update locations I'd straightforward, but I'm not sure how I'd want to handle access to this section.

The simplest approach is a password check with a single password in the conf file. A more difficult alternative is a file of user names and passwords that is manually created.

The best, but hardest approach would be a Web interface to created and edit user accounts. Not sure if there's time for this.

If we do take this approach, I could quickly throw together a start so that other people could start contributing and there's be a clear path for them.

Being a totally optional time investment, there's no loss of this isn't completed.

Main concern is whether or not this would be useful. If csvs will continue to be used, this is mostly useless since the current approach recreates the DB from scratch. If csvs are abandoned, this may be a necessity. On Mar 24, 2015 5:28 PM, "J Lys" notifications@github.com wrote:

CRUD

— Reply to this email directly or view it on GitHub https://github.com/MikeHoffert/EatSafe/issues/144.

KatrinaHoffert commented 9 years ago

This is underway in the admin-interface branch. The authentication system is already done, as is a page that lists all locations with options to add, edit, and delete. Deletion is done. Adding is next and editing is mostly going to be a variation of adding (since most of the work is the form).

KatrinaHoffert commented 9 years ago

This has been done. Coordinates are not yet supported, but can be setup the same way as before (by running the coordinate auxiliary program). Propose coordinates be mapped to location IDs instead of address + city tuples, first.

That change is pretty much necessary for a hack-free implementation, since we can't handle the case of a location without an address that has coordinates.