coreyhyllested / ht.src Goto Github PK

We need to do this at the server level.

It affects everything involving the DB. Shaun used [email protected],
which was stored in the DB. When he tried to search for [email protected] didn't match.

So, what I think is the best solution is to capture both [login, signup]
and before putting them into the DB we call email.lower() on them.

• Corey

Easy peasy...

Users can signup and login with Facebook.

Are there research already done?

• promptness
• professionalism
• communication
• expertise
• quality (bang per buck)

Users are currently required to be logged in to view profiles

Enable browser caching. May require adding flags to images, text.

As a user glances over a Hero's profile. This has a large impact in how a user can be found via search.

How will their industry be useful? We could have fewer larger lists (Art, Architecture, and Design). Which more holistically point to the nature of the job. However, there is still a lot of grey area, such as sales. We want people to say they are a painter, or furniture design. But there are salespeople in the art world, and a salesperson in 'art' is a mismatch.

Being in Art is fairly broad and problematic from a search point. What comes back when art sales people say they are in art... their skill for trade is sales (or communication).

More directly. We want to use this field to help facilitate a better search. It would be great if users 'got' how to use it. But if they don't it could create a bad UX.

Requires Stripe API.

• We should have already created Credit Card token.
• Must be saved with Proposal and Appointment, perhaps part of Account / Profile.

Similarly, once the credit card is captured we can queue an email request to be sent after the appointment ends. There is no check necessary for this, because the credit card was captured.

Users should be able to know their password's strength. We're not requiring any specific characters, capitalization, and minimal requirements on length. Users would benefit from knowing they've picked a poor password.

This is creating a spot in the ht_header bar's dropdown. Along with Settings, Logout, and Profile, should be a 'Event List'. 2 notifications. (1 Proposal sent, 1 negotiation responded to).

If agreed to by both parties -- no reviews -- no money mentioned in either profile. Solves the unwanted attention. We take a cut. But there is no trace in their public profiles.

To allow the edit page to provide uploads, the directory /tmp/ht_upload must exist and be writeable.

Make sure this exists at startup time.
./run should create this directory if it doesn't exist. rw (no exec permissions, just in case).

https://sqlalchemy-migrate.readthedocs.org/en/latest/

From this tutorial.
http://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-iv-database

Something is wrong with the tutorial or our version or some infrastructure.

Requires a DB table where we maintain events.
Table must allow event to be acknowledged / seen.
Should be cacheable in some way.

Opened by Tine.

We need a filter for ordering the search results. A - Z, Z - A, Low price, high price, location/proximity to you, etc.

Basically, it would be a feature in Profile, where a browser could find other similar people. Helps browsers explore the other skills and people on the site.

The first event that should be added to future queues is a credit card capture. When the event moves from a future queue to the hourly, today queue. All events can be checked immediately if the event has been canceled between the timelines.

This is alright.

If the event has not been canceled. It is processed. i.e we contact stripe, capture the charge, and deposit value if possible.

Users can signup, login with Google account.

I've done this on Harbinger; download source code from http://www.postgresql.org/ftp/source/
$ ./configure --prefix=pwd --with-openssl

$ make clean && make && make install
$ cd bin
$ export PGSSLMODE=require
$ export PGPASSWORD=lM5sTTQ8mMRM7CPM0JrSb50vDJ
$ ./pg_dump -U user:ezjlivdbtrqwgx -h host:ec2-54-235-70-146.compute-1.amazonaws.com database:d673en78hg143l > HT_backup_DATE.sql
CoreyHyllested

CoreyHyllested commented 2 months ago
The HT_backup_date.sql file is written by user ezjlivdbtrqwgx.

That means we must replace that user with the user for the new database.

I created a new database..
psql "dbname=de3jroup18ut67 host=ec2-54-197-241-67.compute-1.amazonaws.com user=hyeyhmziftbibd password=oJlVUQqJS589L8shuzu34-vI2- port=5432 sslmode=require"

OLDUSER = ezjlivdbtrqwgx
NEWUSER = hyeyhmziftbibd
From vim...

%s/ezjlivdbtrqwgx/hyeyhmziftbibd/g

Now that we've replaced the username. We need to connect to the new database and run the backed up database file.
$ psql "dbname=de3jroup18ut67 host=ec2-54-197-241-67.compute-1.amazonaws.com user=hyeyhmziftbibd password=oJlVUQqJS589L8shuzu34-vI2- port=5432 sslmode=require" < HT_backup_12.30.2013_rename.sql
CoreyHyllested

CoreyHyllested commented 2 months ago
Before I forget there is also ' --clean --inserts --column-inserts' that may be added to the pg_dump. Not sure if this is necessary.

Another option is to use Amazon's RDS. They do backup for us. We just need to figure out restore.

A user should see the Hero's default rate rather than needing to fill it in.

When a person has just one review, his preview section lists it as "1 reviews" instead of "1 review".

For solr/Postgres.

I believe this is a Cookie / Session timeout.

Questions?

What is the default?
How do I modify the timeout, TTL, (whatever its called)?

If a user has not signed up, i.e. there is no matching email in the DB.

• Create their account.
• We need to keep the user's LinkedIn ID so if they have already joined HeroTime, we can try to merge their LinkedIn information with their account.

My thought was we make an oauth table, where we could have
OAUTH-COMPANY, ID, email
LinkedIn -- linkedin id -- [email protected]
FaceBook -- fb id -- [email protected]
Twitter -- twitter id -- [email protected] <--- not sure how to deal with this.

We need it. Eventually.

TL;DR: The problem is we're copying the full proposal text into the pop-up alert. Reduce the size of the text copied.

Lazar:
The Stripe description (after a purchase from Profile page) is the full description of the slot which is being bought. The Stripe pop-up works well with short descriptions, but long ones introduce a serious problem, as the pop-up gets vertically resized until it's completely unusable.

Therefore, we should change the transaction description to something shorter. (Maybe just "3-hour meeting with X"?)

CoreyHyllested:
You cannot purchase a timeslot from Profile page currently. It was removed to align with proposals only. I like your proposal, but we might be saving the time already. I suggest we cut the first X characters of the meeting because its more descriptive.

Gonna drop PRIO to low. This might not even be needed.

Event system tentatively works as so: For each event, drop it into a queue that decides what future queue it needs to go on.

Future Queues will be made if it does not already exist.

• there is one future queue per day.
• The first event on the future queue is to consume all the events on this queue and create 24 (one per hour) queues for the day when that event is ready.
• All events added to the queue can then be checked the day of if anything has changed.

If a user has already signed up with a Linkedin account.
Check the DB and send the user to his dashboard.

Logging out when not logged in => (Non-helpful) Error message.

If you were to 'level up' -- we scan reviews for keywords.

E.g Kay's P2P Trainer style.
We could get a badge for X number or Y percentage of people calling you a hard-ass trainer. Or a yoga style instructor.

Ideation Session:
Badge for repeat customers. => Shows Trust.
Badge for different customers => Shows values diversity.
Badge for global? Different languages?
Badge for 10+ people saying promptness is a feature. (or 50%)

Users can signup, login with Twitter.

security_question and security_question_answer -- like a challenge to help reset ID. [I preface this with Settings page to limit the scope of what 'missing security Q & A' might mean.]

Anyways, this is spec.

"A user, forgetful Felix, cannot remember his password. Prior to resetting it, HT presents a challenge. If he knows this secret info, then HT can let him A) reset password which will send an email. B) let Felix use his profile on the service.

However, we have recovery, so this is super-low prio.

We have two cases.

The browsing user is the owner of that profile
The browsing user is not the owner of that profile.

The template code can be changed using
{% bp is sameas hp %}

We need to verify every button. image. text. label. etc makes sense for those two different cases.

@capetroz Please take a look and flag each thing wrong.

Investigate using 'South' for making changes to DB and migrating current DB to those changes.

Using Chrome.

• Right click on any page, click inspect element. This will bring up the developer tools.
• On the Dev Tools task-bar, go to the far right, 'Console'.
• For every-page, it will report all problems rendering the page.

I've found several bugs this way today. For Example.
On the Edit Page, we couldn't use AJAX because the library was loaded over HTTP when the Edit Page was loaded over HTTPS. This was also why our fonts looked different. (Cool, huh). Anyways, we need to do a periodic cleanup.

Allow floating points on the backend.