moped | Web Client for Mopidy , built with AngularJS | Frontend Framework library

First, make MotoEntity implement Serializable, then you can pass the list.

You can use a simple loop with a zip:

The xtable package doesn't support adding that optional argument, but you could add it yourself by editing the result. For example,

You can use the functions from below to get the correct output. One function will return the HTML for just one officer while the other will return the HTML of all of them. You can test it below.

Sorry, but mongoid 3.1 was released in 2013 and mongodb 3.4 was released 3 years later in 2016... It kinda make sense it will not work... Have you considered upgrading mongoid? or getting older mongodb?

If there's no way you can change the version you can try to only upgrade the mongo driver (bundle update mongo) and see what happens.

Depending on what you're trying to achieve, capped collections might not be suited for your use case. In the Capped Collection Documentation, it says:

Capped collections work in a way similar to circular buffers: once a collection fills its allocated space, it makes room for new documents by overwriting the oldest documents in the collection.

If you use a capped collection and then insert a new document, it would just overwrite the existing document, rather than throwing an error. Of course, you could just insert a new document with the updated information instead of overwriting the existing one, but I'm not sure if that's what you intend to do. (If that is helpful, you can create a capped collection through the Mongo Shell when you're setting up your MongoDB instance.)

Overall, it sounds like enforcing this rule in your application logic is the way to go. I would also spend some time thinking about whether you really need this information to be in the database -- would a Ruby singleton class or some environment variables better suit your needs?

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)

The exception:

Try running bundle update json to force update the json gem. If that doesn't work, you can run gem clean, delete your Gemfile.lock and run everything again.

Edit: It looks like your bundler version isn't compatible with your version of rails. You can try to downgrade bundler by running:

1. gem install bundler --version '1.14.6'
2. gem uninstall bundler --version '2.0.1'

Also, is this a new project? If so, you should consider using rails 5. Rails 3 is close to being three major versions behind with the release of rails 6 not too far away. It would help avoid a lot of these gem issues as well.