Skip to main content

MongDB 27017 vs 27018


Setting up a MongoDB server on a separate ec2 instance and then accessing it from the application and web interface.

The default port used is 27017 by various MongoDB drivers while 28017 is used to handle HTTP requests and provides some general monitoring.
In case you are interested to start mongod on a separate port for say security reasons, take it as 6565,
then the monitor port will always be 7575.

You can also query via web browser, sudo /etc/init.d/mongod --rest. Now simple
queries can be executed like http://localhost:7575/database/collection/?filter_a=1.

I often use mongoid to access mongodb in my rails application and access the rails console using
rails c production, which links me to the mongo database present on different ec2 instance.
Use "connection strings" of the form mongodb://user:pwd@host:port/.

Refer MongoDB - HTTP Interfaces



Comments

Popular posts from this blog

Cannot allocate memory error while computing files - Setup Swap space

ActionView::Template::Error (Cannot allocate memory - nodejs /tmp/execjs20131021-26716-fckzo3.js 2>&1
Nodejs is used to compile javascript at runtime. In RoR applications, this error comes when server is started in production mode which compiles the assets or while running rake assets:precompile.
check for swap space and allocate

Fresh server start after instance degraded

So the issue was, amazon issued an warning regarding the server to be terminated, before i could think of making an backup the instance stopped.

The troubleshoot operations like reboot, stop and start didn't worked.
Simple Steps to start a fresh instance with the previous content on server.

upload images to AWS::S3 in ruby using aws sdk gem

Using gem aws-sdk for a ROR application for uploading images to s3
Uploading images to a fixed bucket with different folders for each object or application. The s3 keeps a limitation on the number of buckets creation whereas there is no limitation for content inside a bucket. This code will upload image for a user to s3 using aws-sdk gem. The bucket and the image uploaded are made public, so that the images uploaded are directly accessible. The input is takes is the image complete path where it is present, folder in which it should be uploaded and user_id for whom it should be uploaded. def save_screenshot_to_s3(image_location, folder_name,user_id) service = AWS::S3.new(:access_key_id => ACCESS_KEY_ID, :secret_access_key => SECRET_ACCESS_KEY) bucket_name = "app-images" if(service.buckets.include?(bucket_name)) bucket = service.buckets[bucket_name] else bucket = service.buckets.create(bucket_name) …