A cursory look at the database schema shows that it looks like it's handling two things:
logging who accesses Demo Arigato
importing info from the csv files to populate the remote site
1 shouldn't matter because there's no back-end to DA, so any transactions are logged on the authenticated Canvas site
2 shouldn't be necessary because we can pull straight from the csv using read file and the Canvas API.
This will make #5 much easier and reduce the server cost of the app, though read file is probably slower than a database read.
A cursory look at the database schema shows that it looks like it's handling two things:
csvfiles to populate the remote site1 shouldn't matter because there's no back-end to DA, so any transactions are logged on the authenticated Canvas site 2 shouldn't be necessary because we can pull straight from the
csvusing read file and the Canvas API.This will make #5 much easier and reduce the server cost of the app, though read file is probably slower than a database read.