Exciting times. RGVWEBPRO will return to the world of open source. It will no longer provide web hosting or sell domain names.
Author: Jorge Saldivar
-
You ‘memba?
Boy, time flies…
-
Solar Eclipse 2023
One of the real cool effects of a solar eclipse is when the partially blocked sun light shines through branches leaving this crescent light pattern. It’s the same concept as using a Pinhole Projector, except it’s an array. Very cool, indeed.
-
git@github.com: Permission denied (publickey)
Issue:
ubuntu@rgvwebpro:~$ git push git@github.com: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
Resolution:
The error message you’re seeing is typically related to SSH key authentication issues when trying to communicate with a GitHub repository. The steps to resolve this error and prevent it from occurring in the future are as follows:
- Check SSH Keys: Make sure that you have an SSH key generated and added to your GitHub account.
- To check if you have an SSH key, you can run the following command:
ls -al ~/.ssh
- If you don’t see any SSH keys, or if you want to create a new one, you can generate an SSH key using the command:
ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
- To check if you have an SSH key, you can run the following command:
- Add SSH Key to GitHub:
- Run
cat ~/.ssh/id_rsa.pub
to display your public SSH key. - Copy the displayed key.
- Go to your GitHub account settings, navigate to the SSH and GPG keys section, click on “New SSH key”, paste your public key into the text field, and save it.
- Run
- Check SSH Agent:
- Ensure that the ssh-agent is running by executing
eval "$(ssh-agent -s)"
. - Add your private SSH key to the ssh-agent using the command:
ssh-add ~/.ssh/id_rsa
- Ensure that the ssh-agent is running by executing
- Test the Connection:
- Test your SSH connection to GitHub using the following command:
ssh -T git@github.com
- You should receive a message indicating that you’ve successfully authenticated, but that GitHub does not provide shell access.
- Test your SSH connection to GitHub using the following command:
- Update Remote URL (Optional):
- If your repository is still configured to use HTTPS, you might want to switch to SSH. You can check the remote URL using:
git remote -v
- If needed, change the remote URL to use the SSH protocol:
git remote set-url origin git@github.com:username/repo.git
- If your repository is still configured to use HTTPS, you might want to switch to SSH. You can check the remote URL using:
- Retry the Push:
- Now try pushing to GitHub again:
git push
- Now try pushing to GitHub again:
- Check Repository Permissions:
- Ensure that your GitHub account has the necessary permissions to access the repository you’re trying to push to.
By following these steps, you should be able to resolve the “Permission denied (publickey)” error when pushing to GitHub.
- Check SSH Keys: Make sure that you have an SSH key generated and added to your GitHub account.
-
Enhancing my VS Code theme
Vibing with this Atom One Dark theme.
What’s your theme of choice?
-
Enhancing Your macOS Terminal Workflow: Creating an Alias for ‘ll’ to ‘ls -als’
To list files and directories with detailed information using the
ll
command in the macOS terminal, you can create an alias forls -als
. Here’s how you can do it:-
Open your terminal.
-
Run the following command to open your shell profile configuration file in a text editor. This file is usually
.bashrc
or.bash_profile
.
nano ~/.bashrc
- Add the following line to create an alias for
ll
to executels -als
.
alias ll='ls -als'
-
Save and exit the text editor by pressing
Ctrl + O
to write the changes and thenEnter
, followed byCtrl + X
to exit. -
Source your profile to apply the changes without having to restart the terminal.
source ~/.bashrc
Now you can use the
ll
command to list files and directories with detailed information, just like you would withls -als
. The alias will make your terminal experience more efficient and convenient.Possible Issue: If the source has to be updated after each new terminal window.
Run
echo $SHELL
to check if bash or zsh.If you’re using the
zsh
shell, the steps to create an alias forll
will be slightly different than for thebash
shell. Here’s what you should do:-
Open Configuration File: Open your
zsh
configuration file, which is usually~/.zshrc
, in a text editor. You can do this using the following command:nano ~/.zshrc
-
Add Alias: Add the alias for
ll
by including the following line in your~/.zshrc
file:alias ll='ls -als'
-
Save and Exit: Save the changes and exit the text editor (Nano) by pressing
Ctrl + O
to write changes, thenEnter
, andCtrl + X
to exit. -
Apply Changes: To apply the changes to your current terminal session, run:
source ~/.zshrc
Now, whenever you open a new terminal session, the
ll
command should automatically be aliased tols -als
without needing to runsource ~/.zshrc
each time.Title and body written by ChatGPT.
-
-
Simplifying My Life
I have uninstalled
saldivar.co
‘s WordPress instance and have 301 redirected tojorge.saldivar.co
‘s domain. At first, the purpose of the two sites was to separate concerns, web design business and personal use. However, that’s no longer necessary since I’ve been employed full-time. -
Getting a little fed up: I cannot easily share on WP
With the “death of Twitter,” and social media in general, I’d like to take back my content. It’s just not currently easy to share content to my blog.
-
Going to try Copilot chat
This is… nice.