Say My Name(1): What is a right path to start a new project through github?
“Say my name” is a brand new series for my chapters to allow myself having a space to deliberate issues in programmings of what I’ve been quite unfamiliar with, a process to make an operation, or maybe just a simple definition for a nifty noun in computing science.
My first question on series, SMN, is how to start a new project from remote end? What is a right path to start a new project through github? Here are my 7 steps to successfully reach the specific project we need from our github platform. Before we kickstart a path, make sure we have signed up a personal account on github.
While receiving a fresh assignment from my fellows,
step 1, Open up your github account: make sure you have already laid out your foundation on this website. Github seemly be a must-have in coding world, and it’s indeed a handy access to bridge among both local and remote end. Once you fork this new project from your team, we need to directly open up of those repository contained with this new filed, click the right-sided green button, “Code”and git clone its remote url link as below:
The following steps would be continuing on our Terminal.
step 2, Input “git clone” and the url copied from HTTPS of the field forked from your team in order to download it on local Terminal.
step 3, A “check! README.md” is necessary to browse contained information from this field. Make sure this field is being set as a mode of README.md.
step 4, “bundle install” it, shortly after checkin’ the field, IMMEDIATELY. In reason of avoiding some extending inconveniences from its compatibility and interdependency, a.k.a. BUG Problems. To bundle install is the sincere first step as long as we receive a RUBY project. What the functions made by just to bundle install ? Well, bundle install is an action to read/fetch Gems based on this receiving project; soon afterwards download automatically these Gems from its default link, https://rubygems.org and generate a field named “Gemfile.lock” within inside of our project.
step 5, “yarn install” is the next essential order to be made. Yarn is a already-set package to do two major things: (1) to parallelize the package installation itself, (2) to make the package manager faster in our project. Just image this move could help us facilitate those managements like JS and CSS library into our project. Yes, yarn install is to upgrade those functionalities used in the front-end, it could be more complete and make us more welcome once we code CSS and JS.
step 6, Input “rails db:migrate” on our project. According to handful reference, “Learn Ruby on Rails for your own” ( 為你自己學 Ruby on Rails/ 博客來：https://bit.ly/3mJ9TlG), written by our major mentor, Long-Ge, quoted a further definition of Migration and its verb tern, migrate. In general, Migration is to describe ‘How does the structure of database look like?’ and would being gradually increased in the developing process of our project. One additional advantage of Migration itself is to supportively control our project through Git version, therefore the procedure of designing holistic database could be understood fully at a glance; Migration here, is to do as well. Once we make an input, “rails db:migrate”, could operate those bland codes into a real data table.
step 7, to finalize our download is to input “rails s”/ “rails server”. Rails server itself is a command to activate a small web server called ‘WEBrick’, of which is also a built-in server inside of RUBY. In brief, “rails server” could help us open a browser to access RUBY programmings.
Here we go, a proper download has been completed!