How to push git code into a repository with out all node packages

As am trying to learn node JS, I've learnt that we need a lot of packages to run a web application. Like any web app we would want to push (store) this code in Github. No one wants to have all the projects present in our local machine. Storing data in Github applications will help us to access the code from any where any system. Also we get to choose if we want this application to be public/private

In a simple application we would be requiring so many packages

As we can see they are so many packages and ideally we don't require all this code to be uploaded in Github. As long we have uploaded package.json we can always download these files by using the following command i.e. npm -i install once we download the project from github

While uploading the project to github we need to create .gitignore file and enter the filenames which we want not to be uploaded ".gitignore" file is a hidden file

For ignoring the node modules enter the following directory

Then next steps are similar github upload

Creating repository in github
Then in local machine enter the following commands git init
git add .
git commit -m "version name"
git remote add origin https://github.com/githubusername/projectname.git
git push -u origin master

Once the upload is successful, we can check in github that all the files except the nodemodules are uploaded

This is a standard practices while uploading projects in github

Comments

Comparing Objects in Informatica

We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out ...

Finding Duplicate records and Deleting Duplicate records in TERADATA

Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',...

Updating Target Table in Informatica

Generally, in every project we will see at least one requirement to update target based on some conditions. Case1: When we have primary key defined on table in Database Case2: When we do not have primary key defined on table in Database Case3: When we want to update target based on non-primary key field. Let’s discuss it in detail. Case1: When we have primary key defined on table in Database After creating table in DB, import table as target along with primary key constraints. After done with importing, we can check the primary key details by editing target in target definition. In this case, we can use update strategy to update target table. Suppose, we have a table called RETURN_CD and primary key ROW_WID defined on that table. Now, we can update target table using update strategy based on primary key. In mapping, we should connect primary key port and the ports which we want to update in target table. Please check the below screenshot. And ...

IT Pandora (ETL,DB,UNIX,AWS,NodeJS,Github etc.)

Search This Blog