1- use gitx(http://gitx.frim.nl/) and make your git commits selectively from now on.

2- put more db constraints to your database: unique combi index on [completed_lessons. lesson_id, completed_lessons. user_id] more null constraints etc. More constraints you have in your database, better it is. You can also view/analyse your schema via:

$ psql your_database_name

then \q to quit, \d+ to see all your tables, \d+ table_name to see details of a specific table and you can write SQL statements in that psql session then end them with ; and enter to execute.

When I tried to log in the application then I was not been able to authenticate myself and an error popped up.

For more information on the error please see attached screenshot.

should be a route with lesson/{id} and a static page for each lesson

Right now the user can create a lesson, but the completed-lessons needs the current user_id passed in.

If user_id is set to optional => true (required field), it is possible to post a completed_lesson with the lesson_id, but the user_id also needs to be posted.

https://medium.com/@helenflam/how-to-change-your-rails-app-database-from-sqlite-to-postgresql-before-deploying-to-heroku-ae2acc25c7ac

http://guides.railsgirls.com/backend-with-active-admin

https://github.com/turbolinks/turbolinks / react router

https://scimo.herokuapp.com//lessons/dna instead of https://scimo.herokuapp.com//lessons/7

media/images/jerome-b41e2386.png 416 KiB
media/images/katrina-71f953ac.png 597 KiB
media/images/kyle-c10e3f9d.png 306 KiB
media/images/marie-1aa0dbbe.png 561 KiB
media/images/neer-a59861dd.png 544 KiB
media/images/sound-845c936e.gif

https://webpack.js.org/guides/code-splitting/

guide: http://guides.railsgirls.com/testing-rspec