Posts

Showing posts from January, 2022

Cloning Your App with Git

Image
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 . Firstly, unsurprisingly, we need the codebase on our local machin...

Troubleshooting Your Apps

Image
As you go forth into the wide and exciting world of app development, enjoying all the fruitful satisfaction that it contains, you will no doubt encounter issues (bugs) that you just can't get to the bottom from simply looking at your code. Don't feel embarrassed by this, it happens to the best of us - so much so that by default Rails installs a gem to help squash these bugs; aptly named byebug . Let's use a relevant, non-silly example of something that might catch you out. Say you are building a web app to store particularly excellent photos of cats. Your database is populated, your MVC components set up and you try to navigate to one of your lovely pictures on your app but see the following depressingly cat-free page instead: Now, some / most of us will have seen what the problem is immediately here. But for the sake of showing you the basics of byebug, let's pretend we're none the wiser. ...

Popular posts from this blog

[ToDoList] Basic Pages

New Rails Apps with Docker Compose

[ToDoList] Building the App