BrowserSync Grunt configuration - Multi browswer Live Reload

How to configure BrowserSync's Live Reload feature with Grunt tasks :

BrowserSync is capable of live reloading and syncing the changes across all your test browsers. This will launch a mini web server by using your current working directory as the base, watch your files for changes & auto-inject those changes into all connected browsers.

See my earlier blog post for the pros/cons of BrowserSync over LiveReload.

In this tutorial, I will demonstrate how to configure the BrowserSync with Grunt tasks "grunt-contrib-watch" and "grunt-browser-sync" in a basic web page setup. You can easily configure your bigger projects on you follow the following steps:

Setup Steps:

The link to github project is given at the end of this article.

1) Web App/Site setup :

I've a basic web site with the following files / directories in my working folder:

  index.html
  css/
      main.css
  js/
      app.js

BrowserSync vs LiveReload productivity boosters comparison

BrowserSync and LiveReload both are the cool tools that are aimed to improve the development workflow i.e., productivity of front-end development team. In summary, they both reload your browser automatically when you change some css or javascript or HTML - let's say any resource.

The main feature that we get from BrowserSync is : it has capacity of live reloading all your test browsers. It doesn't has constraint to one browser, meaning : it can reflect your code changes on every browser/device/emulator. The new devices/browsers can be added/tested with no additional configurations.

 

Pros and Cons of BrowserSync with LiveReload:

Pros :

• Works across multiple devices at the same time
• Works with all browsers and devices
• No configuration/plugin needed in each browser
• Synchronized actions across all browsers
• form input, page scroll, navigation all gets synchronized across the browsers
• Works with all browsers and devices

Con :

• Initial configuration might be a little tricky
• npm, grunt or gulp etc needs to be configured and the dependencies might give some problems to configure

 

Configuring Lombok on IntelliJ - Installation of Lombok plugin

How to install/configure Lombok plugin on IntelliJ IDEA :

Steps :

1) Installation 
Using IDE built-in plugin system on Windows:

• File > Settings > Plugins > Browse repositories... > Search for "lombok" > Install Plugin

Using IDE built-in plugin system on MacOs:

• Preferences > Settings > Plugins > Browse repositories... > Search for "lombok" > Install Plugin

Manually:

• Download the latest release from https://github.com/mplushnikov/lombok-intellij-plugin 
• Install it manually using Preferences > Plugins > Install plugin from disk...

2) Restart IDE.
3) Enable Annotation Processing
 In your project: Click Preferences, "Build, Execution, Deployment", Compiler, Annotation Processors. Click Enable Annotation Processing

Enabling Annotation Processing on IntelliJ IDEA

Optional) IntelliJ and Eclipse compiler
If you're using Eclipse compiler with lombok, try this setup:

• install plugin (above process)
• change compiler setting:
•  > Compiler > Java Compiler > Use Compiler: Eclipse
•  > Compiler > Annotation Processors > Enable annotation processing: checked (default configuration)
•  > Compiler > Additional build process VM options: -javaagent:lombok.jar

References :

• https://github.com/mplushnikov/lombok-intellij-plugin
• http://stackoverflow.com/questions/24006937/lombok-annotations-do-not-compile-under-intellij-idea
• http://stackoverflow.com/questions/9424364/cant-compile-project-when-im-using-lombok-under-intellij-idea
• https://projectlombok.org/index.html
• https://projectlombok.org/mavenrepo/

MongoException$DuplicateKey: E11000 duplicate key error index - @Version

Obviously, we get this exception when we try to update/insert a document(record) with duplicate key field in MongoDB collection(table). There exists several explanation on this:

• http://stackoverflow.com/questions/24430220/e11000-duplicate-key-error-index-in-mongodb-mongoose
• http://stackoverflow.com/questions/16465416/mongodb-upsert-throwing-duplicatekeyexception
• https://www.youtube.com/watch?v=7SLerprHiG8

But, I was getting this error in a different scenario:

1) I already had a model User and data in it. Sample data were being created using mongeez change log file
2) Later, I added a new auditing field @Version to the entity definition.
3) When updating a User record, I got the above exception ( MongoException$DuplicateKey: E11000 duplicate key error index )

User entity :

@Document(collection = "user")
public class User implements Serializable {

    @NotNull    @Size(min = 5, max = 100)
    @Id    private String id;

    @Version    Long version; // THIS WAS ADDED LATER
    
    @Size(max = 50)
    @Field("first_name")
    private String firstName;

    @Field("last_name")
    private String lastName;

    @Email
    private String email;

 

Solution :

I added a property version and initialized to 1 in all documents

Mongo Change Log  : Using mongeez

<mongoChangeLog>
    <changeSet changeId="ChangeSet-2" author="gtiwari">
        <script>
            db.user.insert(
            {
                "_id" : "user1",
                "first_name": "",
                "last_name": "User 1",
                "email": "user1@localhost",
                "version":1  --> I UPDATED ALL user RECORDS'S VERSION = 1 TO SOLVE THIS
            });

Spring MongoDB _id field mapping conventions

Java Spring MongoDB  : '_id' field mapping :

MongoDB requires that you have an '_id' field for all documents. If you don’t provide one the driver will assign a ObjectId with a generated value. The "_id" field can be of any type the, other than arrays.

The following outlines what field will be mapped to the '_id' document field:

• A field annotated with @Id (org.springframework.data.annotation.Id) will be mapped to the '_id' field.
  
• A field without an annotation but named 'id' will be mapped to the '_id' field.
  
• The default field name for identifiers is '_id' and can be customized via the @Field annotation.
  

Examples for the translation of '_id'-field definitions

Field definition	Resulting Id-Fieldname in MongoDB
String id	_id
@Field String id	_id
@Field('x') String id	x
@Id String x	_id
@Field('x') @Id String x	_id

Source :  How the '_id' field is handled in the mapping layer

MongoDB Multiple insert at once

We can insert multiple documents (bulk insert) to a collection using a single insert command :

Syntax :
   db.[COLLECTION].insert( [ { DOC1 }, {DOC2} ] ) ;

Example :
   db.people.insert( [ {name: "Ganesh", age: 24, country : "Nepal"}, {name: "John", age : 20} ]);

In Java  ( Using Spring Data JPA Repository )

   personRepository.insert( personList);
   --> It follows org.springframework.data.mongodb.repository.MongoRepository#insert(Iterable<S> entities) method's syntax

MongoDB rename a database

As of now, there is not a straight forward way to rename a MongoDB database. But you can use the following steps to achieve so :

Here, we are trying to rename OLD_DB to NEW_DB

Steps :
1) copy old database to new one using db.CopyDatabase( OLD_DB, NEW_DB )
2) switching to OLD_DB and dropping the database

Mongo Command :

  #Step 1 : Copy database to new name
     db.copyDatabase("OLD_DB","NEW_DB") 

  #Step 2 and 3, drop OLD_DB
     use OLD_DB
     db.dropDatabase()

MongoDB Drop Database

We can use the following query to drop ( DELETE EVERYTHING) from a MongoDB database

( please be careful on running the query, it deletes everything )

   use [database]
   db.dropDatabase() 

MongoDB Like Query

We can do the following to achieve SQL's LIKE equivalent on a Query :

MongoDB :  db.users.find({"name": /jo/})

MYSQL Equivalent:   select * from users where name like '%jo%' 

MongoDB - show all database in server

We can use following commands to view all databases in the server
   show dbs
OR
   show databases