Decided on url design for now, added super basic skeleton for celery, tasks, and testing frameworks.
implemented new alarm --> add to db.
Updated register form to show the phone in shadowed input box.
Got rid of double Twilio imports (imports now all handled in aa_comm).
Got rid of all apscheduler references. Hasnt been used in a while, shouldve been done already.
hacked around with/then deleted scheduling. Cleaned up a bit more.
redid UI, deleted a ton of everything, GAMETIME
Few more UI tweaks, starting to work on code. Login works, removed verifcation code entry from any registration screens, and added it to user's home page (albeit very minimally added). Added phone number unique-ness check right from home page.
Added basic admin template. Handled registration process and split pages.
just checking in some work, more as a backup to UI changed about to try. Added a bit of functionality also, the user home page is alot more dynamic, mainly alarms section.
Set/unset/add new alarm added with minimal functionality. Just read/write from db really. updated a bit more UI, deleted old css files. Wrapping up major UI dev for now. Attemptint to start with some sort of scheduling/backend.
Big commit. Pretty much full working skeleton in place.
Finally all comes together decently. Glad I spent the time on the UI, minimal
as it is. Glad I waited and restarted with Celery and took my time planning out
the scheduler idea and workflow.

Feels good! Coming along well! Summary follows.

Added:
 - scheduler and job tasks. basic implementation of Celery and alarm task handling.
 - process_phone_verification. sends user verification code through both registration paths,
by adding the message sending to the scheduler job queue. Also verify and update user's
phone property upon verification code input validation.
 - User Set and Unset alarm. Makes the whole process work.

Fixed:
 - After successful user registration user is now redirected to their own personal
home page. Was previously redirecting users to the main home page.
 - Successfully sets alarm in scheduler and avoids conflicts when adding a new alarm vs
setting a pre-existing inactive alarm.

I know I'm missing a ton of little things but I am exhausted and will be pushing this a ton
tommorow, so hopefully this is just part of an amend!
Added new formatting functions and corresponding Jinja filters.
Added Update-alarm page and function skeleton for update alarm implementation.
Added verify_alarm_ownership to check for a valid user to alarm relationship.
Added remove alarm function.
Added functionality to user_home page 'Account' tab, all info is live now.

Rewrote mostly all of set/unset alarm views. Manage everything in global functions.

TODO:
Make user_home alarms show acive/inactive state based on current alarm_event(s) status.
Fixed Set/Unset alarm functionality
corrected remove_alarm to be a GET request instead of previous POST
user alarm display now correctly represents alarm state based on new 'alarm_status'
	variable, which represents whether the alarm currently has an active event or not
made delete alarm link LIVE on update alarm page
Update base html template to allow override of entire meta-nav-bar or just it's content. Updated second reg page to go along with UI scheme and made a few other tweaks to (*hopefully) increase the user's experience
Add add/remove user_phones. also manages verifying, deleting corresponding alarms, etc.
Added user_properties table to db, updated alarms to save in utc. format to/from works well, all internals are to be handled by utc in near future. Having issue with my hard-coded us eastern timezone calculations being off by 1 hour with utc time... would guess that this is related to dst but only because of the obvious factors, no knowledge at all here. will inbestigate tonight and tomorrow.
Fixed local/utc conversion functions, now handle timezones/DST well... i think!
Added basic framework for handling user responses. The app isnt accessible from the web yet, so twilio cant forward responses. Therefore responses are temporarily handled by a simple get request including the phone number. The response handler is very basic for now, only searching for and deactivating or resetting alarms that have been active in the last hour. It does however lay a good workflow out for handling response forwarding (as I call it?) from Twilio, alarm schedule management, and alarm identifying.
Starting to clean up and get ready to move to testing server!