Grr this took hours to figure out. I was trying to install MJPG-streamer and running VLC command lines and all this crap but nothing worked.
First install motion:
~> sudo apt-get install motion
Then create a config file:
~> mkdir ~/.motion
~> nano ~/.motion/motion.conf
| #!/bin/bash | |
| # Sometimes you need to move your existing git repository | |
| # to a new remote repository (/new remote origin). | |
| # Here are a simple and quick steps that does exactly this. | |
| # | |
| # Let's assume we call "old repo" the repository you wish | |
| # to move, and "new repo" the one you wish to move to. | |
| # | |
| ### Step 1. Make sure you have a local copy of all "old repo" | |
| ### branches and tags. |
| {# style 1 - long form #} | |
| {% if filepath == '/var/opt/tomcat_1' %} | |
| {% set tomcat_value = tomcat_1_value %} | |
| {% else %} | |
| {% set tomcat_value = tomcat_2_value %} | |
| {% endif %} | |
| {# style 2 - short form #} | |
| {% set tomcat_value = tomcat_1_value if (filepath == '/var/opt/tomcat_1') else tomcat_2_value %} |
| sudo pip install awscli | |
| aws configure | |
| aws ses send-email \ | |
| --from "[email protected]" \ | |
| --destination "[email protected]" \ | |
| --message "Subject={Data=from ses,Charset=utf8},Body={Text={Data=ses says hi,Charset=utf8},Html={Data=,Charset=utf8}}" |
| """ | |
| Given a dictionary, transform it to a string. Then byte encode that string. Then base64 encode it and since this will go | |
| on a url, use the urlsafe version. Then decode the byte string so that it can be else where. | |
| """ | |
| data = base64.urlsafe_b64encode(json.dumps({'a': 123}).encode()).decode() | |
| # And the decode is just as simple... | |
| data = json.loads(base64.urlsafe_b64decode(query_param.encode()).decode()) | |
| # Byte encode the string, base64 decode that, then byte decode, finally transform it to a dictionary |
Q: Shouldn't we name it like Cloud Agnostic Object Storage Interface
The Object Storage is one of the fundamental services provided by the cloud provides. The objects are generally stored in the tree directory structure similary like on the file system. The objects are consumed either by API or in most cases by their unique HTTP URL or by cloud specific internal URI (See Appendix 1).
The initiative addresses a growing need to support the hybrid cloud applications by allowing the developers to transparently access and manipulate the objects from within applications running in various cloud environments.