Click on the extension tab and search for ESlint. click on the application install button to install in VS Code.
Refresh VS Code for ESlint to load.
In terminal application, go to your development folder and run the following commands.
$ npm install eslint. // to install eslint
$ npx eslint --init // to initialise eslint
# follow the prompts.
Only one member of the team requires to complete the following steps.
git clone command.At this stage, I would assume you already have Heroku app setup. So I will drive straight into adding the build script.
In this example, I want to generate css files from scss files. So, I will be using that too.
Open your package.json file in your editor.
Under script object: add the following
"scripts": {
"build": "sass public/assets/scss:public/assets/css",
Save the file and commit to Heroku.
Reference:
This post is more focus on MySQL database with Sequelize.js ORM. Last time, I have already talked about how to deploy node.js app with MySQL database to Heroku. So, I will run through those similar steps. If you need detail instruction, please visit the previous post.
First of all, open your command line application. You will find me referring Command-line application as terminal since I feel more comfortable with this term.
In your terminal, run the following command to setup a Heroku app
# go to your development folder. Here, I am assuming you already have # a git repo with your application code. $ heroku login # follow the prompts to login to Heroku $ heroku create <<your_app_name>> # if success, Creating <your_app_name>.. done message will be shown
After your have created your app, in your web browser, go to your Heroku Dashboard.
In your Heroku Dashboard, add JAWSDB under resources tab
Open your model/index.js file in your code editor and change your database connection statement to the following.
// DB setup
const db = {};
let sequelize;
if (process.env.JAWSDB_URL) {
// for Heroku
sequelize = new Sequelize(process.env.JAWSDB_URL, {});
} else {
const env = process.env.NODE_ENV || "development";
const config = path.resolve(__dirname, "..", "config", "config.json")[env];
sequelize = new Sequelize(config.database, config.username, config.password, config);
}
Normally, you can just added Heroku’s database credentials to “production” object in config.json file. But I do not like to commit such information to GitHub, Heroku or any Open Environment for security purposes. Hence, normally config.json file is in my .gitignore file and never commit to git at all.
If you have sequelize migration files like I do, modify “production” object your config.json file with JAWSDB settings.
In your terminal,
# Go to your project folder # run the following commands $ npx sequelize db:migrate --env=production $ npx sequelize-cli db:seed:all --env=production
References:
If you are reading this, we’ll assume that you have created a node.js application with MySQL database and commit your code to GitHub but not to Heroku. So, let’s start from creating an app for your application in Heroku.
$ heroku create <<app_name>>$ git remote -vlet connectionInfo;
if(process.env.JAWSDB_URL) {
connectionInfo = process.env.JAWSDB_URL;
} else {
connectionInfo = {
host:process.env.DB_HOST,
port: process.env.DB_PORT,
user: process.env.DB_USER,
password:process.env.DB_PASSWORD,
database: process.env.DB_NAME
};
}
const connection = mysql.createConnection(connectionInfo);In terminal window, push the code to Heroku server by the following command.
$ git push heroku master
Or if you are committing from a branch
$ git push heroku <<my_branch>>:master
Happy New Year, everyone. Hope year 2020 is a great year.
Sadly, Australia has lost so many during this new year season. All my condolences to all who lost lives, loved ones, houses or livelihoods to those fires and my respects to all those heroes out there fighting those fires and protecting the communities.
I like to setup .gitignore file at the very start (when I set up my repos and first clone it). So, most of the time, I get away with git caching the file problem. But most of my friends had that problem and another friend of ours shared this post by Imcneel. I would like to make a note here so that I can comeback to it later if I need it. Who knows right?
NOTE: if you are using VS Code editor, your VS Code may prompt that you have too many action in your repository. Mine does but it can be because I am using VS Code extensions for the git.
If not, you can follow Imcneel‘s instruction as following:
The following steps are command line commands so you will need your command prompt, terminal or similar command line application. Here are the steps.
1. Navigate to git repository folder.
2. Create a .gitnore file if not exists by the following command:
$ touch .gitignore3. Add node_modules in .gitignore by opening and adding “node_modules” in the .gitignore file. Or you can run the following command.
$ echo node_modules >> .gitignore4. remove cached node_modules from the repo by running this command:
$ git rm -r --cached node_modules5. run git add and git commit commands for the git to make notes of the node_modules folder removal.
$ git add . // This will add both .gitignore file and node_module removal (and any other change you made to the repo).
$ git commit -m "Remove node_modules folder from repo"This topic is not hard and there are a lot answers already out there.
The logic is not hard but I kept forgetting and messing up the formula. Thus, I am posting this post so that I can make quick reference to the formula instead of skimming all the information all over again. I put my reference sites at the end of this page so please feel free to visit the original sites for detail explanations.
Math.floor(Math.random() * (max - min)) + min
e.g.
Math.floor(Math.random() * 11) // for random integer from 0 to 10
Math.floor(Math.random() * (max - min + 1)) + min;
Branching a git is needed to collaborate with others using Git system. Here, I will talk about how to branch off a git repository.
1. Clone the project repository onto your computer if you haven’t done so.
2. Go to project repository folder in your command line terminal.
3. Run the following command to create and checkout a new branch. Remember to replace [branch_name] suitable to your task such as “create-html-skeleton” or “add-create-new-function”
$ git checkout -b [brance_name]4. Verify if branching works by:
$ git branchYou should see at least 2 branches: master and your new branch.
5. You can do the git add and git commit commands as usual.
6. The only difference will be git push. In git push command, instead of origin master, use origin your branch name like the following command
$ git push origin my_branch7. Once you are done with the command line, go to your GitHub account in your browser.
8. In the repository page, you should be able to see “Compare & pull request”. Click on it and follow the prompts to create a pull request to your team.
I am now using Git on MacBook. Whenever I make changes to my Git folder, MacBook will add .DS_Store. Normally, it is fine since it is the way it was configured. BUT, it is super annoying sometimes to remove accidentally committed .DS_Store files from Git. So, as usual, I did a google search on this issue.
I found the solution on Stackoverflow. I found I can actually set up gitignore setting for .DS_Store files. Thank you, Benzado and Chris Redford, for the solution. Here are the steps.
$ find . -name .DS_Store -print0 | xargs -0 git rm -f --ignore-unmatch
$ echo .DS_Store >> .gitignore
$ git add .gitignore
After that, commit your git as usual
$ git commit -m "remove .DS_Store files from git"
$ git push
Cyn's 