alexeykudinkin / delivr-web Goto Github PK

Thin is assumed as the lightest/fastest/easiest ruby web-server out there. And his SSL facilities are purely sexy comparing to WEBrick's ones!

http://code.macournoyer.com/thin/
https://github.com/macournoyer/thin/

DoorKeeper is the best candidate so far.
https://github.com/doorkeeper-gem/doorkeeper

We need to build solid platform to may have an instant insight at what the actual (courier-wise) situation looks like at any given moment.

Therefore, as a starting point we could devise a platform allowing to track which of the couriers are "active" right now. By "active", i mean having logged in app and pressed "Active" button.

Also need to consider options of devising solid ground for the future platform allowing effectively store all "active" drivers location in real-time.

Therefore, we could state the milestone as the feature-set to-be-done:

• Active/Inactive couriers tracking backend
• Active couriers location tracking backend

Embed feedback form into α-instance to facilitate error reporting.

We need to build a procedure of delivery approval.
Actually it may look like the following way:

1. Customer makes an order denoting phone (contacts?) of the deliveree.
2. Courier arriving at the place denoted, presses "Arrived!".
3. We do send some code (say, 4 digits) as an SMS for the deliveree's phone denoted in order.
4. Deliveree hands it to the courier therefore acknowledging delivery and allowing him to complete the travel (-leg).

Organisationconcept need to be introduced, allowing users binding/management/etc.

Treat travels as 'taggable's allowing more than one tags being attached to the travels.

Pros? Cons?

Need to develop ground for the rich analytical platform. As a baseline:

• Deliveries amount per Courier
• Deliveries distribution per day/week/month, per district, etc.
• Per Courier flaws like delays, excesses, etc.

As an option Google Maps Tracker API may be used.

Google Maps API quotas aren't so sweet as they may seem at first; those are particularly drastic:

Google Maps Geolocation API: 100 requests/day

GGL ar u srs?

Heroku drops filesystem (including sqlite db file) after "dyno" restart (or fail, or application update), so it's required to switch from sqlite.

Maybe, it would convenient to use two different servers one for clients with a permanent storage (postgres?), and another for developers with sqlite.

We need to develop platform for customer feedback tracking.

Having its way like this:

1. Courier delivers item, and press the button "completing" this particular leg of the travel.
2. User receives an SMS about its order, given an option to give a feedback, sending back, say, ":)" if all good, or ":(" otherwise.
3. [OPT] In the case of a problem manager could reach that customer to get a detailed feedback.

https://addons.heroku.com/blowerio

Replace CNAME root-level domain records delivr.ru with page-rules redirecting to (say) www.delivr.ru

http://www.higherorderheroku.com/articles/cloudflare-dns-heroku/

This would be a loooong thread, full of rants and complaints. This is a disclaimer.

So now we know on our own that dynamic typing sucks, lack of syncs sucks, (to be continued).

Decent unit/integratino/... -tests coverage may relax this burning butt-hurt slightly but can it replace it completely?

SIM

SIM.

Actually it may have the form of the dedicated API accepting, say, exception name and some vital details hashed into string.

Implement proper travel routing. Review existing options (Directions API from Google/Yandex Maps) avoiding solving "Travelling Salesman" (again).

Need to push SSL all over the place. Especially inside the authentication chain.
This is a due!

B/C this is crap. It do not fire DOMContentLoaded event after every fetch making all the jQuery.ready() code pretty useless.

BTW, they're crap themselves, just b/c it bears nothing. Except butthurt.

http://staal.io/blog/2013/01/18/dangers-of-turbolinks/

Need to take a look at:

http://goodui.org/index_b.html

Add new layer of client-side validation (thank you Angular), also entails more fine-grained errors reported.

Check whether multiple sessions from multiple workstations are allowed.

Localize delivr.ru

Unfortunately Google Maps aren't good enough at this. Looking forward towards this option (as a temporal solution) https://code.google.com/p/google-maps-tsp-solver.

Route compositing, including fare accounting (Angular vs React and Google Maps)

With approaching new TSP solver, we would break first 1k line of JS code.

It's time to get serious!