buzypi.in Report : Visit Site

Technical data of the buzypi.in

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host buzypi.in. Currently, hosted in Singapore and its service provider is DigitalOcean Cloud .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4.7 (Ubuntu) containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

skip to content travel photography and technology «buzypi.in» technology, travelogues, photography, photo editing and more – from the abode of gautham pai menu and widgets jnaapti corporate training and corporate e-learning solutions by jnaapti subscribe topics ananya around-bangalore blog browser bullsncows coorg delicious digital-photography-guide digital-photography-tips eclifox eclipse extensions firefox game gimp-editing google google-reader greasemonkey humor ibm ibm-internship information-overload isl javascript jnaapti jobless khoj lalbagh lalbagh-bangalore orkut places-near-bangalore privacy rss search security semantic-web startup tagging twitter ubuntu ubuntu-hack web 2.0 web2.0 weread yahoo a docker based development environment at jnaapti , we have been using containerization technologies since almost the very early days. in 2011, when i was evaluating a solution to provide light-weight containers to our learners in the virtual coach , i was told that the only mature solution was to use virtualization solutions. but virtualization was too slow (in terms of boot up time) and i didn’t have enough resources to keep stand-by nodes running all the time. so after some evaluation, i decided to use lxc and it served its purpose. however, there were several features missing and i was in the verge of building a few of them myself. so it’s not surprising that when i discovered docker , i just fell in love with it. one of the first things we did was we moved our lxc based learner containers to docker. we then slowly started to migrate portions of our infrastructure to docker. we achieved full docker migration last november, and then also moved our staging/testing systems in the cloud to docker. the last in the list was to migrate our development environments. the initial migration wasn’t too hard, because of 2 things: we already had docker in production – so it was a matter of working off our production dockerfiles we were already using kvm in our development – so we already had a clear idea about what containers our system should be running. why the move away from kvm based development environments? simple! kvm’s disk usage is too much to suit our requirements. we had our development images of 5g each and you have 10’s of such images and are soon out of disk space. i am not sure how many docker fans will approve some of the things i discuss here but i believe that this is a much leaner solution than using virtualization and i don’t see any issues in the way i am doing it. so with the migration from kvm to docker, there were a few additional things that i wanted to handle: can we use desktop tools like text-editors with data in docker? imagine i am writing a nodejs application. i want to use atom installed in my host to write code. however, i want to run nodejs inside the container. it is very easy to work with command line utilities (which don’t need x ) in containers, but how about desktop utilities like eclipse? can we run this in a docker container and still have the same user experience as a regular app? what are some best practices to do so? is it possible to expose devices into docker containers – this is required for eg, if we are doing android development and want to debug our app in an actual android device the first 2 were rather easy and i sailed through it. the third one, i struggled a little, but i finally made some head-way. this post attempts to capture some of my learnings in this entire process in case you want to build a similar environment. so let me answer these questions: using desktop tools with docker containers this one is easy. a practice we follow is all the code that we write is inside a mounted volume. containers are used to run processes in a contained fashion, but the processes are manipulating files that are in our host (and not in the underlying diff file system). we can as well remove our containers and we don’t lose anything. here is a sample run to demonstrate this: start a docker container that has nodejs installed in it. make sure that this container has access to a local host directory (in this case /home/gautham/desktop/node-data): gautham@ananya:~|? docker run -d -p -v /home/gautham/desktop/node-data:/data --name "node-example" ananya-nodejs:0.0.1 820e105db5061b380e6117e42a0cabad5f00c54e54f5016aefc18399e2a2eb25 check if the container is running gautham@ananya:~|? docker ps container id image command created status ports names 820e105db506 ananya-nodejs:0.0.1 "/usr/sbin/sshd -d" 9 seconds ago up 8 seconds 0.0.0.0:49155->22/tcp node-example inside the container (which is accessible via ssh): gautham@ananya:~|? ssh -p 49155 ubuntu@localhost ubuntu@localhost's password: last login: tue apr 14 14:13:12 2015 from 172.17.42.1 ubuntu@820e105db506:~$ cd /data/ ubuntu@820e105db506:/data$ ls hello.js ubuntu@820e105db506:/data$ node hello.js hello world! using desktop tools inside docker containers this one initially seemed a little difficult, but i figured out soon. create an image that has lxde-core package installed in it. now, there are 2 options: connect to lxde running inside the docker container run these commands in host: docker run -d -p ananya-desktop:0.0.1 sudo su xinit -- :1 & this will now switch you to a different terminal (accessible at ctrl+alt+f8). you will also see a white terminal. type the following in this terminal to start lxde: docker ps container id image command created status ports names 38280dd66b98 ananya-android:0.0.1 "/usr/sbin/sshd -d" 4 minutes ago up 4 minutes 0.0.0.0:49156->22/tcp, 0.0.0.0:49157->5901/tcp hopeful_lumiere ssh -x -p 49156 ubuntu@localhost in the docker container run startlxde you should now see a full fledged desktop running like this! so your host is running at ctrl+alt+f7 and your docker container is at ctrl+alt+f8. use this option in case you are running many desktop applications and you want to be totally isolated from the host when working with the applications in the container (i.e you are not using any host applications in conjunction with the applications in the docker container). only run the application that you are interested in i found this option to be better in some ways. i have my android studio setup using this option now. gautham@ananya:~|? docker run -d -p ananya-desktop:0.0.1 gautham@ananya:~|? ssh -x -p 49156 ubuntu@localhost ubuntu@localhost's password: welcome to ubuntu 14.04.2 lts (gnu/linux 3.16.0-34-generic x86_64) * documentation: https://help.ubuntu.com/ last login: tue apr 14 14:25:47 2015 from 172.17.42.1 ubuntu@38280dd66b98:~$ cd android-studio/ ubuntu@38280dd66b98:~/android-studio$ ls ubuntu@38280dd66b98:~/android-studio$ bin/studio.sh and lo and behold! accessing devices within docker container a final requirement was whether we can get docker to detect usb devices. i found that if you pass a –privileged flag and mount the /dev/ device appropriately, you can then access it in the docker container. i was able to successfully use adb along with my docker container. docker run --privileged -v /data:/data -v /dev/bus/usb:/dev/bus/usb -d -p ananya-android:0.0.1 docker has been a boon and although there are several area of improvement, i see that it has a future. it has become an indispensable tool in our software tools arsenal in jnaapti. cross-posted here: http://jnaapti.com/blog/2015/04/14/a-docker-based-development-environment/ posted on april 14, 2015 february 10, 2017 categories technology tags android-studio , docker , kvm , lxc , lxde , virtualization 2 comments on a docker based development environment the bullsncows application in angularjs about 5 years back, when i was still dabbling with client-side technologies for the first time, i had written the bullsncows game in pure javascript . my knowledge of javascript and client side technologies has evolved quite a bit since then. so, recently when i was looking at this code i thought, “this code could be better if we use angularjs “. so today i thought of rewriting this in

URL analysis for buzypi.in

https://buzypi.in/tag/blog/
https://buzypi.in/tag/docker/
https://buzypi.in/tag/google/
https://buzypi.in/tag/bangalore-startup/
https://buzypi.in/2011/12/01/jnaapti-a-6-month-report/
https://buzypi.in/tag/ananya/
https://buzypi.in/tag/security/
https://buzypi.in/tag/humor/
https://buzypi.in/page/2/
http://buzypi.in/2010/10/04/trip-to-mandagadde-kuppalli-mattur-sakrebailu-and-shimoga/
https://buzypi.in/tag/search/
https://buzypi.in/tag/coorg/
https://buzypi.in/2015/04/14/by-htm/#comments
https://buzypi.in/tag/intuition/
https://buzypi.in/#content

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: BUZYPI.IN
Registry Domain ID: D2850839-AFIN
Registrar WHOIS Server:
Registrar URL: www.godaddy.com
Updated Date: 2018-01-15T12:19:40Z
Creation Date: 2008-02-25T23:46:16Z
Registry Expiry Date: 2023-02-25T23:46:16Z
Registrar Registration Expiration Date:
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4806242505
Reseller:
Domain Status: clientDeleteProhibited
Domain Status: clientRenewProhibited
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Registrant Organization:
Registrant State/Province: Karnataka
Registrant Country: IN
Name Server: NS63.DOMAINCONTROL.COM
Name Server: NS64.DOMAINCONTROL.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2018-07-28T05:30:19Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Access to .IN WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the .IN registry database. The data in this record is provided by .IN Registry for informational purposes only, and .IN does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. .IN reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

  REFERRER http://whois.registry.in

  REGISTRAR INRegistry

SERVERS

  SERVER in.whois-servers.net

  ARGS buzypi.in

  PORT 43

  TYPE domain

DOMAIN

  NAME buzypi.in

  HANDLE D2850839-AFIN

  CREATED 2008-02-25

STATUS
clientDeleteProhibited
clientRenewProhibited
clientTransferProhibited
clientUpdateProhibited

NSERVER

  NS63.DOMAINCONTROL.COM 216.69.185.42

  NS64.DOMAINCONTROL.COM 173.201.69.42

OWNER

ADDRESS

  STATE Karnataka

  COUNTRY IN

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .