DEV Community: Maya Sheriff

The importance of making your "Workspace" folder on your root path😅

Maya Sheriff — Wed, 28 Aug 2024 23:39:11 +0000

I've been deep into my personal project, BuiltBetter, and hit a couple of snags while redeploying. I’ve already shared how I tackled the first issue – you can check out that post here. The fix involved adding x86_64-linux to my lock file so that Render could use it instead of arm64-darwin-21. But that wasn’t the end of my adventure – oh no!

On the same day, I stumbled into another problem.

My Workspace folder wasn’t on my root path... it was nestled in my iCloud 😅.

Upon starting my project, I wanted quick and easy access, so I created a folder on my desktop, thinking it would be smooth sailing. Turns out, I was wrong! Fast forward a month, and while trying to redeploy my site to Render, I ran into all sorts of problems.

Here’s the lowdown:

Bundler and Ruby versions seemed inconsistent between local and global environments.
Bundler was having a tantrum – it wasn’t reading from the Gemfile but from somewhere else entirely.

My troubleshooting attempts were a comedy of errors:

bundle didn’t work.
gem install bundler didn’t work.
bundle clean didn’t work.
Uninstalling and reinstalling Ruby? Nope, still no luck. It seemed like any Bundler commands were completely off the table.

My lovely mentor @heratyian, finally ran the command.
'sudo bundle'
And just like that, Bundler started working! 🚀

But wait, there was more. He highlighted this red flag 🚩 to me, then went searching in my files and found that my desktop folder (where my project was located) was nested in my iCloud.

Run code from your iCloud is crazy and I should probably be in developer prison 😂.

Takeaways:

Even if my desktop was in iCloud or not, it's ALWASYS best practice to keep your Workspace on your root path. It saves you from a world of confusion and problems down the line.

I hope this story helps you in your coding escapades or was just interesting to read. Feel free to share your own lessons learned or ask questions. Happy coding!

Render Error: arm64-darwin-21 vs x86_64-linux

Maya Sheriff — Wed, 28 Aug 2024 22:23:43 +0000

This week, while working on a personal project, I ran into an error that ended up teaching me a bit more about computer processors, so I figured I’d share my findings!

Problem:

While redeploying my web app to Render.com, I encountered the following error:
"Your bundle only supports platforms ["arm64-darwin-21"] but your local platform is x86_64-linux."

Explanation:

This error occurred because the platform my development machine is running on is different from the platform required by Render. Here’s a breakdown:

"arm64-darwin-21":

"arm64": Refers to the ARM 64-bit architecture used in Macs with M1 or M2 chips.
"darwin": Refers to the operating system, which is macOS in this case.
"21": Indicates the version of macOS, specifically macOS 12 (Monterey).

"x86_64-linux":

"x86_64": Refers to the 64-bit extension of the original x86 architecture, which is widely used in Intel and AMD processors.
"linux": Refers to the Linux operating system.

In other words, Render.com is running Linux on an x86_64 architecture, while my development environment is on a Mac with an ARM64 architecture. The error is occurring because the bundle created for macOS (arm64-darwin-21) is not compatible with the Linux (x86_64) environment on Render.

Solution:

To resolve this, I had to add support for the x86_64-linux platform to my bundle, so I used this command:

bundle lock --add-platform x86_64-linux

This command updates the lock file to include x86_64-linux, allowing Render to use this platform specification instead of trying to use the macOS-specific arm64-darwin-21.

Rails Migration Tips and Examples (not a full step by step)

Maya Sheriff — Wed, 26 Jun 2024 16:21:43 +0000

Generates the model and migration, but also all of the RCAVs for index, show, create, update, and destroy.

The model name must be singular.
Separate column names and datatypes with colons (NO SPACES).
Separate name:datatype pairs with spaces (NO COMMAS).

rails generate draft:resource <MODEL_NAME_SINGULAR> <COLUMN_1_NAME>:<COLUMN_1_DATATYPE> <COLUMN_2_NAME>:<COLUMN_2_DATATYPE> # etc

EX:
rails generate draft:resource board name:string
        OR
rails generate draft:resource post title:string body:text expires_on:date board_id:integer

Execute the generated migrations with:

rake db:migrate

This will remove all the files that rails generate draft:resource post ... had previously added. You can then correct your error and re-generate from scratch.

rails destroy draft:resource post

If you made a mistake when generating your draft:resource AND you’ve already run rake db:migrate, then first you have to run the command:

rake db:rollback

Adding and Removing columns

Ex:
rails g migration AddImageToPosts
    OR
rails g migration RemoveExpiresOnFromPosts

If your database gets into a weird state (usually caused by deleting old migration files), your ultimate last resort is
This will destroy your entire database and all the data within it. Then, you can fix your migrations and re-run all from scratch with rake db:migrate, then rake sample_data to recover the sample data.

rake db:drop

How to Install Devise

Maya Sheriff — Wed, 26 Jun 2024 16:15:20 +0000

Use Devise for Users

Install

rails generate devise:install

Change :delete to :getin devise file

# config/initializers/devise.rb, Line 269

config.sign_out_via = :get

Set a root route in routes

# config/routes.rb

root "boards#index"

Use our new generator supplied by the gem to create the User model and routes

rails generate devise user

Then Migrate

rake  db:migrate

Tips and Tricks for Visual Studio Code

Maya Sheriff — Tue, 04 Jun 2024 13:52:33 +0000

Terminal info:
-Our standard bash prompt environment for entering commands like rake grade or bin/server
-Pry for interacting with a database (we could also run rails console for that)
-Irb for typing in pure Ruby code

Commands:
-Reopen a pane
-Left
Mac OS: ⌘ + B
Windows: Ctrl + B
-Bottom
Mac OS: ⌘ + J
Windows: Ctrl + J

-Clear Terminal
Mac OS: ⌘ + K
Windows: Ctrl + K

-Interrupt command
Mac OS: ⌘ + C
Windows: Ctrl + C

-Quick Open file
Mac OS: ⌘ + P
Windows: Ctrl + P

-Command Palette
Mac OS: ⌘ + Shift + P
Windows: Ctrl + Shift + P

-Jump to end of line
Mac OS: ⌘ + E
Windows: Ctrl + E

-Exit
Mac OS: Q
Windows: Q

-Toggle Code
Mac OS: ⌘ + /
Windows: Ctrl + /

-Find Next Selection
Mac OS: Command + D
Windows: Ctrl + D

-Move line
Mac OS: Option + ⬇
Windows: Alt + ⬇

-Duplicate line
Mac OS: Shift + Option + ⬇
Windows: Shift + Alt + ⬇

Other:
-rails console = opens an interactive Ruby environment with your Rails application's context-loaded
-reload! = reload the application's code without exiting the console

Git Commands

Maya Sheriff — Mon, 03 Jun 2024 21:53:41 +0000

Main Git Commands that are important to know!

-Initialize a Repo

% git init

-Create a Commit

% git add -A
% git commit -m "Title of your snapshot"

-Stage file on at a Time (not using "add -A")

% git add path/to/file1
% git add location/of/file2
% git commit -m "My surgical commit"

-Check your status often

% git status

-See what’s changed with diff

% git diff

-Create a new branch

% git checkout -b fancy-new-version-name

-Switch to a different branch
To list all branches:

    % git branch


To switch to another existing branch:

    % git checkout branch-name

-See the git log
To see the history of your current branch:

    % git log


To see a graph of all your branches at once, try:
    % git log --oneline --decorate --graph --all -30

Jumpback to a Previous Commit

% git checkout [SHA of commit you want to go back to]

-Push

    % git push


The very first time you push to a branch, it may ask you to do something like:

    % git push --set-upstream origin your-branch-name

-Start on a new task
Start on a new task
When you’re ready to start on a new task, the best practice is to first switch back to the main branch, get the freshest version, and then to start a new branch from there:

    % git checkout main
    % git pull
    % git checkout -b my-next-task

First Day With Ruby!

Maya Sheriff — Wed, 06 Mar 2024 22:37:50 +0000

Hello, world!

Today I had my first ruby lesson. I created a webpage with the use of GitHub and Render!

Feel free to check out the site here or for a look at the repository click here!

-Maya