[ToDoList] Version Control 2: Electric Boogaloo

  1. Pushing to GitHub

 

 

With the skeleton of our app built and tested, let’s take the opportunity to make this the initial commit to our code repository. Hopefully you followed the previous instructions to install git, create your new GitHub repository and add your SSH key to it (do this now if not) - navigating to this blank repo will display instructions on how to initialise the app directory and push it to GitHub.

GitHub repo default

For posterity, this is also below, with a few extra bits: 

$ git config --global user.name "{{YOUR NAME}}"                  ## set name
$ git config --global user.email "{{YOUR EMAIL ADDRESS}}"        ## set email
$ git init                                                       ## initialise the repo
$ git add -A                                                     ## stage all files
$ git commit -m "{{COMMIT MESSAGE}}"                             ## commit files
$ git branch -M main                                             ## create main repo branch
$ git remote add origin git@github.com:{{USER}}/{{PROJECT}}.git  ## point to the repo
$ git push -u origin main                                        ## push files to GitHub!

And it’s as simple as that - now check your repo in GitHub via the browser and you will see the same files you just added and pushed! Note that this will automatically ignore all database files, in the hope of saving a bit of server space.

This is the only time you should need to set up all of this config for this project - when pushing future changes to our app, we will only need to add the files, commit the changes and push them up to GitHub. Swish.

 
 

< [ToDoList] Building the App | [ToDoList] Intro to Routing >
Back

Comments

Post a Comment

Popular posts from this blog

New Rails Apps with Docker Compose

Image
Following on from the Docker & docker-compose guides, it is possible to use docker-compose to build a Rails application that uses a PostgreSQL database without even installing Ruby on your local machine by instead using containers ! This becomes a very useful option to have if you work from many different workstations and don't want to ensure they are all equipped with the correct Ruby and Rails dependencies, or if you wish to use a version of Ruby / Rails not supported by your operating system (for example, Ubuntu 20.04 only allows provides up to Ruby 2.7 in its apt cache). In fact, Rails 7 added native support for Docker, such that it generates almost all of the default files we need for us! This comes with its problems and, I won't lie, updating this post to work with Rails 7 (it was previously written for Rails 6) has been a colossal pain and features a bit of hackery. However it is ultimately a good thing, and having
Read more

[ToDoList] Basic Pages

Image
Well that was fun. However all we’ve really done is spooked someone called Bob, without actually creating anything remotely resembling a web application. Let’s rectify this and create some pages one would normally find on a website; a Home page and an About page. Home & Away About Helpful Links [Insert Beatles Reference]     Because we already learned a bit about MVC, we know that we will need a controller and at least one view to display these pages (we won’t need to worry about models until we’re handling real data). As before, we’ll need to add a route configuration so Rails knows where to go, too. Rails provides a fair bit of magic to streamline this process in the form of generators . However, because we’re learning, we’re going to do this manually for now and learn what this magic entails, so we can appreciate it more later. We already created a PagesController in the last sec
Read more

[ToDoList] Docker Compose

Image
We learned in the previous section how Docker is a fantastic tool with which to build and deploy applications, however has some inconveniences with developing these apps such as having to rebuild the image every time there is a code change as well as any development database entries being wiped. This section will offer some relief against these two issues by using Docker Compose to build our application and make live code changes, as well as using a separate container to host our development database in PostgreSQL - this will encompass three main tasks: Back up and edit the Dockerfile we made in the previous section so our image can be built. Create our docker-compose.yml in the app's root directory to create our web & postgresql database containers. Back up and edit some our app's configuration (namely the database.yml & Gemfile ) to use the new postgresql container . After all this, we can set about
Read more