The code9000 from osoc17

When tindering birds, your vote-buttons should be accesable, should send your vote to the api and the next bird will be showing, so you can vote the next one.

update root README.md files

Huawei USB 3G stick

Huawei USB 3G stick on Linux seems to be pitty

Update testHardware.py to the latest version

Update it

Create clean code from testHardware.py

testHardware.py contains demo code for the hardware. Use that to create clean code for production.

Interact with the Thunderbird API

Pack collected data into a JSON string
Authenticate with the Thunderbird API
Ship it to the Thunderbird API

Create hardware folder and add some information

Create hardware folder and add some information for the hackathon.

Auto fetch again if there are no more observations left

Or if there are only 5 observations left.

Swiping

Add eslint

Provide logout functionallity

Blacklist the token through the API
Remove the token from localStorage
Show a Logout page, with button to go back to login (or show immediately the login page)

Add controllers in API

Set-up Laravel project

Add Models

Model for observations, votes and users

Add authorization via JWT

https://github.com/tymondesigns/jwt-auth

Provide:

Login
Logout
Refresh
an endpoint to fetch the logged in user (e.g. to fetch his e-mailadress, username and more)

Install Raspbian & setup screen

Set up initial API (endpoints handling + return JSON)

POST
/api/observations (upload image with metadata) 🔒
/api/observations/vote (upvote/downvote) 🔒

GET
/api/observations (limited by pagination)
/api/observations/{id} (metadata)
/api/observations/{id}/picture (full picture)

see https://docs.google.com/document/d/1nDretUIrXzD86Wt2fOnsMBwyUKZG2T2ZFDmxr1IGJLg/edit

Backup battery

Do we really need a separate battery as backup or not?
A warning can be submitted to the Thunderbird API to say that the IOT node is almost dead.

Backup battery should keep the device online for a certain amount of time and needs to be charged while the main battery is alive.

Add a data repository

Implementation of Repository Pattern in Laravel means separations of the data access logic from the business logic.
When fetching all, and we are logged in, give all the photos back that haven't been validated for the user.
When nog logged in, return all (default)

Not yet pagination

Add a seeder with some Dummy data

Sample data (observations (pictures and metadata) and user data)

a sample user
maybe all users of oSoc (can be handy for a demo)?

Preparing Pitch (3min)

Short intro of project
What happen to day and what will happen:
Hardware
WebApi
WebApp
-Short demo

Use Form Request Validation instead

At this moment we have following code:

    public function store(Request $request)
    {
        if ($request->hasFile('image') && $request->has('longitude') && $request->has('latitude') && $request->has('captured_at')) {
            $file = $request->file('image');
            if ($file->extension() == 'jpeg') {
                $picture_storage = Storage::putFile('observation', $file);
                $request['picture_storage'] = $picture_storage;
            }
            Observation::create($request->all());
        }
    }