The admin interface should have at least feature parity with the PriceyBot 1.0 admin page
User auth
Pending Quotes list
Current Quotes list
Log of actions performed
Things we want
Send raw text
Card support (with embedded images)
The admin interface should have at least feature parity with the PriceyBot 1.0 admin page
* User auth
* Pending Quotes list
* Current Quotes list
* Log of actions performed
Things we want
* Send raw text
* Card support (with embedded images)
Database:
User Table
id
gsuite_id
email
password
type - admin/staff
Quote Table
id
quote
usage?
created_at ?
updated_at/last_used?
Credit Table
id
user_id
credit/amount
Quote Transactions
id
user_id
quote_id
Idea's for some database structure:
Database:
User Table
id
gsuite_id
email
password
type - admin/staff
Quote Table
id
quote
usage?
created_at ?
updated_at/last_used?
Credit Table
id
user_id
credit/amount
Quote Transactions
id
user_id
quote_id
If we want to support cards (text/image combo) we will need to figure out how we store images, I.e flat files with DB entries or do we base64 the cunts and store them in the DB (I hate this)
Otherwise we would just need the type added to the quotes table so we can say if its basic/card
Thoughts?
If we want to support cards (text/image combo) we will need to figure out how we store images, I.e flat files with DB entries or do we base64 the cunts and store them in the DB (I hate this)
Otherwise we would just need the type added to the quotes table so we can say if its basic/card
Thoughts?
I do like the idea of adding a type of the quote and storing a link.
we can either do this on the same table or we can have a linking table with Quotes and QuoteLinks
If we wanted it to be more lose we could be something like a QuoteMeta and just have identifer keys and w/e data we wanted
I do like the idea of adding a type of the quote and storing a link.
we can either do this on the same table or we can have a linking table with Quotes and QuoteLinks
If we wanted it to be more lose we could be something like a QuoteMeta and just have identifer keys and w/e data we wanted
This repo is archived. You cannot comment on issues.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The admin interface should have at least feature parity with the PriceyBot 1.0 admin page
Things we want
Idea's for some database structure:
Database:
User Table
id
gsuite_id
email
password
type - admin/staff
Quote Table
id
quote
usage?
created_at ?
updated_at/last_used?
Credit Table
id
user_id
credit/amount
Quote Transactions
id
user_id
quote_id
If we want to support cards (text/image combo) we will need to figure out how we store images, I.e flat files with DB entries or do we base64 the cunts and store them in the DB (I hate this)
Otherwise we would just need the type added to the quotes table so we can say if its basic/card
Thoughts?
I do like the idea of adding a type of the quote and storing a link.
we can either do this on the same table or we can have a linking table with Quotes and QuoteLinks
If we wanted it to be more lose we could be something like a QuoteMeta and just have identifer keys and w/e data we wanted