It should be in the `vendor/assets/javascripts` folder.

Are you serving the site over SSL? Check the browser's developer tools to see if there are any warnings or errors.

Hello Dede,

I've pulled down the code from github and ran it in production mode.

The only difference that I made in the source app was add a secrets key in the secrets.yml file and run the app with RAILS_ENV=production passenger start as this will mount the rails app under nginx (similar to how it would be on a production environment).

I was able to get the camera showing without any issues.

You may want to check your browser to ensure that the camera was shared.

It really depends on the situation. I wouldn't necessarily jump to converting the signature over to an image and store it separately (more so than it already is). If you will be displaying the signature often, you could look into Fragment Caching as a possible solution for the areas where you're displaying the image. Converting and storing the signature as an image seems like unnecessary overhead as well as an added complication.

However, if this is the route you need, you could create an attr_accessor for the signature and convert it to an image and upload it like you're describing.

You should be able to initialize the calendar with these kind of options to do this. In the header, you would only pass agendaDay and then set the default view to basicDay.

   header: {
    left: 'prev,next today',
    center: 'title',
    right: 'agendaDay'
   },
  defaultView: 'basicDay',