MILESTONE -- Registration

[jeturcotte]

Let's get started by building up a CRO service in and around the idea of a user account.

• First, get a CRO service started
  • Make sure it has access to a SQLite database (we'll upgrade to postgres down the road when it is called for)
    • Make sure the database is set up to be persistent between runnings of the service
    • Make sure there is an 'account' table
      • Make sure it has a column for numerical incrementing ID
      • Make sure it has a column for username
      • Make sure it has a column for password
        • BONUS: Find a way to encrypt this password so a download of the database won't compromise people's passwords (not required in early days but would be important to final product)
      • Make sure it has a column for email address
      • Make sure there's a date and time column for when the account was created
  • Make sure it has a get -> function to / (homepage) ...
    • Make sure this homepage has a with:
      • Username
      • Password
      • Email Address
    • And a submit button that'll map to a post -> /account/ endpoint in the CRO service
  • Make sure there is a post -> /account/ endpoint that will receive the form data
    • Establish a connection to the SQLite database and write the contents of the form to the database
    • Make sure it adds a unique ID at the same time the user is created
    • Make sure it adds the DATE and TIME to the table as 'created' (the form would not send this)
    • Package up the details about the new user (including id and created date) and send it back to the browser as JSON
  • Make sure there is a get -> /account// endpoint that will show the full details of a user with the username
    • If the username exists, send the details back as JSON
    • if the username does not exist, send back a 404 not found

[jeturcotte]

There's a lot more to do in and around users, but this is quite a few things just to start with, so we'll worry about all that later.

[jelkner]

Thanks, Josh! This looks like a helpful guide for Peter and Adrian to follow. I'm committed to letting this be their learning path for class, combined with Learning Perl 6 (https://www.learningperl6.com/), which will provide an organized foundation to programming in the language.

[peteryn]

10/7/19
Today we started got a working cro to run. We created a form in HTML to take user data. A simple database was also created. The problem we are currently dealing with is getting the data from the user in the browser to into the database

[ajbuchholz]

10/7/19 Evening Update (After School)
Created two separate links to Sign-In and Register with forms. (Although the links don't work, because we are unsure on how to link them). Database connection has been established and created a table "accounts" with ID, Username, Password, and Email.

TODO

1. Link other HTML Files, currently static page, needs to be dynamic. (We asked the Cro Devs how to do this)

2. Learn how to retrieve inputted info from HTML and input it into the database. (I get the general idea on how to do this) We will try to experiment, a little next class to see what we can do. Otherwise, we may require some help on Thursday afternoon!

Code can be found here: https://gitlab.com/Hermes_/perl6-laboratory/tree/crotest

We are currently just experimenting in our own branch. We will transfer the data later to this branch (ingredient.guru)

[jeturcotte]

Excellent, btw; my own staff aren't updating their tickets this well...

[ajbuchholz]

10/8/19 Update (After School)

I figured out how to create a home page with links to a sign in and register page. We still need to get the information and input it into the database. We will try to work on this tomorrow, although I think we will end up needing help Thursday Night doing this.

TODO

• Input Data from HTML into the Database. Create Register and Sign In.

https://gitlab.com/Hermes_/perl6-laboratory/tree/crotest

[ajbuchholz]

10/9/19 Update (Morning)
https://cro.services/docs/intro/spa-with-cro
This link gives instructions that don't make much sense to me. However, I'm pretty sure this is what we want. Peter & I will keep looking into it, this afternoon in class.

[jeturcotte]

Hmm, it is inevitable; buuuuut, we can go a fair way with dumb forms to wring out our back end. For a single page app, look to react or angular... but that's a whole other level of learning.

[ajbuchholz]

10/9/19 Update (Class)
We did it. We have a post statement that retrieves the info entered in an HTML form and prints them. We are now trying to input those values into the database. I am going to try to figure this out tonight.