dreammelter / agfzb-cloudappdevelopment_capstone Goto Github PK

This will wrap up the week 1 tasks + associated milestone.

• Create dealer details/reviews template
• Update dealership detail view

Gonna just... make one issue for it.

Set it up, then test it out.
Comment your progress here for reference.

See #39 for details on status/research.
I imagine the filtering/querying steps would be the same.

So one interpretation of the provided instructions is to use a Cloud function to query the database by state.
(Another option would be to filter all the results with Django... so fine for a small project/database)

Create index in database

I've made two for testing: state-index and single-state-index

• state-index includes the multiple fields needed
• single-state-index just looks for the state code

Went back to just a single index: dealersByState - will try using the use_index option in another test query.

{
   "index": {
      "fields": [
         "st"
      ]
   },
   "name": "dealersByState",
   "type": "json"
}

Create Cloud Function to Query Database

Running the public Cloudant function "List-query-indexes" lists all of them there.
Running the exec-query-find one, however, runs into an error stating there aren't any queries.

Because of this, I'm not sure if the "create index" step was done right. I have 3 or 4 different IBM API docs open to add to the confusion.

Custom Cloud Function Suggestion

The following has been suggested for the state query filter:

if(params.state){
    return { 
            query: {fields : ['id','city','state','st','address','zip','lat','long','short_name','full_name'], 
            "selector":{st:{"eq":params.state}}}, include_docs: true}
}

The include_docs bit means I can throw away the pass-the-docs step. Or would this be part of it?

Others have reported not passing the parameter as a string (just with CA, for ex.) causes trouble. (This is while manually testing the API. We could easily account for that with toString() or something.)

Somebody make it make sense please...

Create Bootstrap table to display it all neatly uwu.

Create Django view to handle logout request

Switch from M2M to one-to-one. We're gonna need PKs for this, neither of which have one.

as mentioned in in #20 (comment)

If there's anything to really add...

The table filters dealers by state, but... it doesn't implement the "get dealers by state" feature at all.
Could maybe add a link to that somewhere?

Step 2/3 for creating static pages

Probably gonna run through this last as it'll need a new API link and extra fiddling.

• Create route in API
• Create method in restapis module (mirror get_dealer_reviews_from_cf)
• Update views to use new API function
• Add new URL/Template? (or just add a button to homepage? sounds like extra js)

TIP:

"The only diff from the CF version is adding a URL parameter arg:
get_request(url, **kwargs) → e.g get_request(url, dealerId=dealerId)

See also: #14 (comment)

Create the following Cloud Function Endpoints and APIs:

• Get all dealerships
• #39
• #40
• Post review for a dealership

Create APIs:

• Get All Dealerships
• ?? Get state Dealerships
• Get reviews for dealership
• Post review

(If you run into an issue, maybe convert the task into one.)

• Add Dockerfile
• Push built image to IBM registry

Yeah the first one just failed due to login issue (group names are case-sensitive)

Now the staging step of the second is failing and states it has trouble finding my key file. (Which makes sense. However we're gonna expose a new secret key in the mean time.)

On the live instance... (do we have the wrong path?)
Might have to switch to an alternative at this stage.

Step 1/3 for creating static pages

Task 4/4 to create the proxy services for the Cloud functions.
Create add_review view to post dealer review

This should wrap up the general implementation of the backend features.

Create Django view to handle signup request.

This should complete the (initial) User Management tasks.

Clean-up/polish task (which may be in the "dynamic pages" milestone but eh.)

• Update reviews on dealership page
• update review form itself

As mentioned in #17 (comment)

Add user login/logout and sign up menu items.

Their content is barebones:

• Add flavor text
• Make it pretty.

• Add the models to models.py
• Make migrations.
• Register them with admin site
• Create new CarMake/CarModel objects

May be a "wontfix" thing depending on time constraints.
But they seem like simple enough revisions to some settings.

Run through the Deployment checklist, but I mostly want to

• turn off debug mode
• #60

It'd be nice to have the name of the dealer on their detail/review page. Easiest way to do that would be to pass it along with the dealer ID, instead of calling the API again.

Create Django view to handle login request

We'll have to try accessing user-provided env vars some other time...

Task 3/4 to create the proxy services for the Cloud functions.
Incorporate Watson NLU in get_dealer_details view for analyzing review sentiment

The forms for the login and registration pages work, however they display in a single line.

Update:

• Login Form Layout
• Sign Up Form Layout

Originally noted in: #8 (comment)

Create two databases:

• dealerships
• reviews

Then use npm couchimport for JSON data

Wasn't gonna go with this at first but I may as well.

I only updated the navbar links on one template page, so when the About/Contact started working, they were still using the placeholder.

We'll start with refactoring those two pages to extend a base template before we deploy to cloud or tamper with the others.

• Create Base.html
• Refactor About page
• Refactor Contact page
• Verify the links and pages still load.

As it does not exist yet ofc.

Step 3/3 for creating static pages

"Add deployment artifacts for the app so it can be managed by Kubernetes"

• Create deployment.yaml
• deploy with IBM k8s

• Create template for submitting reviews
• Update add_review view

This should complete the Dynamic Pages milestone.

Task 1/4 to create the proxy services for the Cloud functions.
Create the get_dealerships view to get the list of dealers.

Task 2/4 to create the proxy services for the Cloud functions.
Create the get_dealer_details view to get the all the reviews for a dealer.

PLACEHOLDER UPDATES

• Show actual name/username
• update href/action links:
  • navbar title
  • navbar login/logout/sign up
  • About and Contact (#5 has this listed?)

FIX / CLEANUP

NAVBAR: Spacing on login items
NAVBAR: Styling for links to about/contact

Originally mentioned: #1 (comment)

Looks like I only imported the partial version.

This should help clear up any of the broken reviews I submitted for testing, too.
(We will have to update our randint() method used to give reviews an ID in the add_dealer_review method.)

The view/URLConf code seems to be working, Django just can't locate the templates to load.
Gonna hold off on the deploy step (#4) and test outside Theia lab.
Might have to work outside of it again.

Originally mentioned in #2 (comment)

URLs to Gather:

• This repo: https://github.com/dreammelter/agfzb-CloudAppDevelopment_Capstone
• App's public Cloud Foundry URL: https://tac-x0-dealerapp.us-south.cf.appdomain.cloud
  • Contact Us link: https://tac-x0-dealerapp.us-south.cf.appdomain.cloud/djangoapp/contact/
  • About Us link: https://tac-x0-dealerapp.us-south.cf.appdomain.cloud/djangoapp/about/
  • Dealerships page: (index?)
• Public Cloud Function Endpoint URLs:
  • GET dealer action: https://1984d932.us-south.apigw.appdomain.cloud/api/dealership
  • GET/POST review action: https://1984d932.us-south.apigw.appdomain.cloud/api/review

That should do it for Tasks 1-7

User Functionality

Ensure the user can...:

• filter dealerships by state
• click a dealership and see all reviews
• sign up using "sign up" button
• login if they're already registered
• logout if they're logged in
• submit a review if they're registered

That should take care of Tasks 8-13

Admin Functionality

Ensure a registered admin can...:

• login into the app/admin site
• can logout of app
• can add new car make and model
• can see newly added cars in admin view form

That should handle remaining Tasks 14-17

General Functionality

• "Use Bootstrap to make application more intuitive"

"ValueError at /djangoapp/review/4/Solarbreeze
Field 'mdid' expected a number but got 'Signal - Twice - 2017'."

Great. Something about L176 in views.py?