Cloning Your App with Git

  1. Cloning Your App to a New Development Environment

 

 

Cloning to a New Dev Env

There may come a time when you want to work on your app from another workstation. However, of course, this isn't just a simple case of copying the code to another machine and picking up where you left off!
Rails demonstrates various levels of helpfulness in this regard - it will tell you if it simply needs a database migration to work, however if your webpacker assets aren't there then it will provide decidedly little assistance!

However, following the list of instructions below will almost certainly get you into a place where you can run your local Rails development server and console, and continue working on your lovely app.
Bear in mind that this section will not go into development environment setup, which can be found earlier in this guide here.

  1. Firstly, unsurprisingly, we need the codebase on our local machine. This is made as easy as possible using our friendly neighbourhood version control utility: git.
    Navigating to your project's GitHub page and hit the Code button, which will open a dropdown with various cloning options. All we need to do is copy the address under the SSH tab:

    GitHub clone options

    and then, on our new developmemt environment, pass the address to the git clone command: 
    $ git clone git@github.com:Not-Another-Script-Kiddie/my_lovely_project..git
    If this errors out this may be due to a lack of SSH key that authenticates your environment with the app - see the previous GitHub section for instructions on how to resolve this.

  2. When the clone finishes, we can change into the project's directory in preparation for the bits we need to run inside it: 

    $ cd my_lovely_project
    • Remember that, if you are developing on a branch of your repository, you will need to switch to this branch: 
      $ git checkout branch_of_loveliness

  3. We now need to make sure all of our application's Ruby dependencies are present on the environment we are working on. For this, we use the Gemfile that is built and updated with our Rails app, and run the following to install the gems inside it (passing the argument to not install the production gems): 

    $ bundle install --without production
    This may ask for a your password a few times in order to access the various areas of the filesystem it needs to.

  4. Next up we need to install the node dependencies needed for our webpack assets: 

    $ npm install
    This may take a little while, so be patient!

  5. With the dependencies in place, we can actually install webpacker in our app: 

    $ rails webpacker:install

  6. Finally, with all of our assets in place, we can set up our database tables using the migration files in our app: 

    $ rails db:migrate

With all this done, we can now access the Rails console to check our code and peruse the backend: 

$ rails c
and, when we are ready, can activate our development server to test our application in the browser: 
$ rails s

 
 

Back

Comments

Post a Comment

Popular posts from this blog

[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...
Read more

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] Building the App

Image
The new Generator The Rails Development Server     So we have now learned some theory about Rails and set up our development environment with the required packages and version control prerequisites. I think that’s enough preamble, let’s get developing! The next few sections will involve creating a funky little web app that contains a To-Do list that we can add, remove and edit entries from. We saw a very small snippet of the extensive file structure that Rails uses in the first section. If you thought you’d be constructing the longest mkdir -p command in the observable universe to get all of this set up, you will be pleased to know (as I was) that our first utilisation of Rails magic will be to get Rails to generate all of this for us! Feel free to set up a projects directory on your dev machine, or you can just use your home dir if you’d prefer. Whatever you choose, change into this dir n...
Read more