Ninja Space Content Blog

To find all git files in your machine type the following in the terminal: find . -name .git -type d -prune

Shortcut: Click F2 and then change the variable name and click 'enter' to change all variables that is the same as what you selected before hitting F2.

Things I didn't remember to do when trying to create my server and database from memory:

1. Install nodemon by: npm install nodemon --save-dev
2. To pull variable from .env after configing is process.env
3. After creating the database name in psql. \c [database name] to make sure you're in that database to create new tables.
4. Type \d [table name] to see schema that you've just created.
5. PSQL is very strict. Must have a space after the table name like so for inserting data: INSERT INTO people (firstname, lastname) VALUES ('firstTest', 'lastTest');
6. When updating PSQL database, make sure to use single quotes. Double quotes won't work. Example: UPDATE people SET firstname='James', lastname='Taylor' WHERE id=1;

I haven't finished my Angular tutorial yet but I'm going to have to shift gears here and start learning GraphQL. It's been said that it's a great alternative to Rest API as you only need one end point to get data for a group of tables in your database. You implement GraphQL in the back-end of your project. I haven't started coding in it but what I always do is watch a lot of YouTube videos and documents to narrow down the resource(s) that I need to look back to. Here are my notes.

PROS for GraphQL from watching Pedro Youtube:

• You only need one end point to get data from a group of tables which is /graphql
• You can query to receive only the data you need.
• GraphQL is strongly-typed.
• You can utilize the GraphiQL to test a query in the browser and try the end point
• If using PostgreSQL, you will need to use pg-promise library so there is familiarity if you're used to PostgreSQL.
• You won't need a body parser?!
• Gets rid of REST
• You don't have to make many calls. Just 1 for data you're looking for even if it's nested information

CONS for GraphQL:

I found something interesting this past week.

Last month, I bought a domain name via Netlify because I've been deploying my front end React apps there during bootcamp and decided to do something different with domain buying. Earlier this year in January 2021, I also bought another domain name but this was through Godaddy. I didn't think much of it. I buy almost all of my domains through Godaddy because that's what I've been doing for over a decade as I'm comfortable with their interface.

Even though my January 2021 domain that I bought through Godaddy has been live for 8 months and the Netifly domain has only been live for 1 month, my Netifly domain has been properly indexed already and showing up in Google search queries way faster than my other domain from Godaddy. The cost for me was actually cheaper through Netlify too!

I have a few theories on why this is happening.

First off, I built my own database for the Netifly domain, whereas I was pulling data from a public API for the Godaddy domain. Right there, was very key. I have unique content displaying for my Netlify website.

Secondly, any domain that I buy through Netlify, if I'm hosting it there, comes automatically with a secure socket layer. I didn't have to buy extra for SSL. Therefore, my Netlify site is secure from the get-go via https whereas the January domain purchase is not. Godaddy charges me extra for SSL certs so I usually avoid buying one unless my revenue justifies it.

Lastly, I was hosting through Godaddy's shared hosting which could be a very bad thing if I'm sharing the same IP address with another site that belongs to someone else that was marked as spam. That could affect my rankings and the way Google indexes my website.

I'm very happy with how my newer site is indexing in Google's search engine and can't wait to share any new findings. I highly recommend trying Netlify out if you're torn between using Godaddy or Netlify to buy your domain and plan on deploying a React app.

For several years, I've been embedding Google Adsense on my websites to earn revenue. Part of the process is when I'm adding ads to a new site that I've just launched, I would need to add that site under settings for my Google Adsense account and wait for a review.

My Steps

1. Go to your Google Adsense account and on the left side, select "Sites." 
2. Go ahead and add a site here. Embed your code with your publisher ID in the head section of your website.
3. Then, request Google Adsense to review it. 
4. You will see this message: "Getting your site ready to show ads Please bear with us! This usually takes a few days, but in some cases can take up to 2 weeks. We'll notify you as soon as we've run some checks on your site. Make sure you don't remove your site and resubmit it because this can delay the process. In the meantime, place the code on every page you want ads to appear. After our checks are complete, your site will be ready to show ads. Remember to go to Ads and choose the ad formats you want to show"
5. Now, this is the part that you'll need to be patient for awhile. When you check the console of your React App, you'll see this red error in the console "Failed to load resource: the server responded with a status of 403 ()" but don't fret, just be patient. It's because Google Adsense hasn't approved your request yet. When it has approved it, it will go away.