Linux Basic: 2015

Reverse Proxy for ssl (https)

Below is the VirtualHost conf example, Just change ServerName to yours And also change path of cert and key.
Check ssl module is enabled or not

<VirtualHost *:443>
    ServerName example.com

    <Proxy *>
        Order deny,allow
        Allow from all
    </Proxy>

    SSLEngine on
    SSLProxyEngine On
    SSLCertificateFile path/to/example.crt
    SSLCertificateKeyFile path/to/example.key
    ProxyRequests Off
    ProxyPreserveHost On
    ProxyPass / https://localhost:3026/
    ProxyPassReverse / https://localhost:3026/
</VirtualHost>

How to Install s3cmd in Linux and Manage Amazon s3 Buckets on ubuntu

On Ubuntu/Dabian:

$ sudo apt-get install s3cmd

Configure s3cmd Environment

# s3cmd --configure
Enter new values or accept defaults in brackets with Enter. Refer to user manual for detailed description of all options. Access key and Secret key are your identifiers for Amazon S3
Access Key: xxxxxxxxxxxxxxxxxxxxxx
Secret Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Encryption password is used to protect your files from reading by unauthorized persons while in transfer to S3 Encryption
password: xxxxxxxxxx
Path to GPG program [/usr/bin/gpg]:
When using secure HTTPS protocol all communication with Amazon S3 servers is protected from 3rd party eavesdropping. This method is slower than plain HTTP and can't be used if you're behind a proxy Use HTTPS protocol [No]: Yes New settings:
Access Key: xxxxxxxxxxxxxxxxxxxxxx
Secret Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Encryption password: xxxxxxxxxx
Path to GPG program: /usr/bin/gpg Use HTTPS protocol: True
HTTP Proxy server name: HTTP Proxy server port: 0
Test access with supplied credentials? [Y/n] Y
Please wait, attempting to list all buckets... Success. Your access key and secret key worked fine :-) Now verifying that encryption works... Success. Encryption and decryption worked fine :-) Save settings? [y/N] y
Configuration saved to '/root/.s3cfg'

Importing and Exporting MongoDB Databases

Exporting from MongoDB

To export the database, simply tell mongodump which database (or collection) you want to export, and where to export it to. Mine was the pets database, so my command looks like this:

mongodump -d pets -o petsbackup

This dumps the pets database into the petsbackup directory. Take a look at what we have in that directory now:

pets
├── animals.bson
└── system.indexes.bson

0 directories, 2 files

The only collection in my pets database is the animals collection, however you'll see a .bson file for each collection in your database, plus the system indexes collection. It is up to you whether you want to take individual collections, or a whole database, but bear in mind that your choice will dictate whether you get information about indexes etc when you import the data elsewhere.

Importing to MongoDB

To import, simply use the mongorestore command, which accepts either a single .bson file representing a collection, or a directory containing multiple files. Here's my example:

mongorestore -d pets /path/to/pets

You can specify any database name and path to files you like, so for taking backups or restoring additional copies of a database, this can be really handy. The mongo commands are well-documented and I found them easy to work with - hopefully this helps you work with them too!