Meteor.js CodeMash Staff Application

Scott ZischerkNote: If you have interest in checking out the project, you can find it here:


If you’re not familiar with CodeMash, it’s a technology conference hosted at the Kalahari Resort & Indoor Water Park in Sandusky, OH:

CodeMash is a unique event that will educate developers on current practices, methodologies, and technology trends in a variety of platforms and development languages such as Java, .NET, Ruby, Python and PHP.

Continue reading “Meteor.js CodeMash Staff Application”

This Week with Meteor: Project Structure

8This week with Meteor we restructured the application.  After developing on this project for the last month or so, we have decided on some best practices for our team.  Drawing on other experiences that we have had with .Net, Backbone.js and Angular, we decided to go with a feature based approach.

Continue reading “This Week with Meteor: Project Structure”

Bringing an External REST Feed into a Meteor Project

Scott ZischerkThis week with Meteor we attempted to bring in an external REST feed into the project. We were looking to bring the CodeMash session feed into the application. In order to do this, we needed to use import a Meteor package. We decided to use the http ( ) package to do this since it was referenced in the Meteor documentation and looked to be the standard way to accomplish the task.

Continue reading “Bringing an External REST Feed into a Meteor Project”

A Tutorial in Meteor

8As I have been learning Meteor, I have found some great resources for the initial set up.

This is the official meteor tutorial– it’ll get you started with how to use Meteor. However there are a few things missing.

Unfortunately, this tutorial does not show you how to pass a parameter through a helper, which is incredibly important. The tutorial does not show you how, so I will!

Continue reading “A Tutorial in Meteor”

Meteor App for CodeMash Staff

Scott ZischerkWe are currently working on an application in meteor.js for CodeMash. The purpose of this application is to provide all members of the CodeMash crew (including staff, volunteers, admin, speakers, etc.) a way to stay in communication about CodeMash related information. The application will automatically create a list of the 40 users, give them a default password, and (after initial login) allow the user to change their information. The application will also include a messenger/chat feature to allow users to interact with each other.

As of last week, we created a user interface mockup. We have a functional login method, and a functional top navigation bar. We also have a page where admins can edit users. Today, we set up data retrieval for the “Schedule Admin” page. We tested to see what would show up if a user didn’t have permissions. During this test, we found out that the admin permissions were being cached. We will be fixing this in the next phase. We will also refine some of our requirements for the next steps.  


CodeMash v2.0.1.4

Scott ZischerkBackstory

This year at CodeMash, I volunteered to take over the sign creation from Jeff Blankenburg.  Shortly after, Darrell Hawley asked if I wanted to be a CodeMash volunteer also, and I said that I would.  It turned out that Darrell wasn’t going to be able to make it to the conference and he asked if I would take over his volunteer coordinator duties this year as well.  I said sure and he passed the torch and all of knowledge of the position on December 26th.  The volunteers consist of students from local universities, speakers that are not speaking and spouses of speakers.  Darrell had already put together the team of volunteers and I just had to lead them.  The volunteer duties include room proctor, mealtime proctor, registration desk, information desk, and any other task that needs to be done for the conference.  The central location that the volunteers hung out at was the registration booth.

Continue reading “CodeMash v2.0.1.4”

“The root of the certificate chain is not a trusted root authority”

Scott ZischerkI recently ran into an issue where a web service that I had set up through SharePoint was throwing the error: “The root of the certificate chain is not a trusted root authority”  The web service ultimately sent out an email with an attachment that is retrieved from a SharePoint document library.  The error was occurring when I created a HttpWebRequest and called the GetResponse method.  Initially, I tried to reassign the ServicePointManager.ServerCertificateValidationCallback property to a method that just returns true, but that didn’t seem to work.

Eventually, I found this blog post: that had me download all the certificates in the SSL certificate chain and add them into SharePoint.  After adding the root, intermediate and SSL certificate the web service started working properly.