## Personal notes on first time

## First-Time Setup Notes
### Getting SSH to Work with Nest

From my estimation, the problem was my ssh agent wasn't consistently loaded on my terminal sessions. However, it really smells to me like a red herring the CLI agent went off on.

From my estimation, the problem was my SSH agent wasn't consistently loaded on my terminal sessions. However, it really smells to me like a red herring the CLI agent went off on.

One big thing he found was the correct format for identifying the website to use, the username, and the repo name. I had been using the wrong format, which was causing the SSH connection to fail. The Pijul CLI would only say "error 404", so I was lost. Copilot determined some way to find out more error details, apparently from the Pijul docs (I saw a few Pijul website URLs flash by in the terminal).

One big thing it found was the correct format for identifying the website to use, the username, and the repo name. I had been using the wrong format, which was causing the SSH connection to fail. The Pijul CLI would only say "error 404", so I was lost. Copilot determined some way to find out more error details, apparently from the Pijul docs (I saw a few Pijul website URLs flash by in the terminal).

One other difference tonight was, running from a Chromebook instead of my macbook. I remember sommat about macbooks using a different SSH key format, and I know my default key here is called id_rsa whereas on my macbook it's id_ed25519 (maybe - that name is just a Copilot auto-completion).

### SSH Key Differences

A weird thing that happened was, halfway through the process of editing some stuff after my first Pijul push to the Nest, the Chromebook just up and died. Like, as if its battery died. I plugged it in and it came back, but the battery was above halfway still.

One other difference tonight was running from a Chromebook instead of my macbook. I remember something about macbooks using a different SSH key format, and I know my default key here is called `id_rsa` whereas on my macbook it's `id_ed25519` (maybe—that name is just a Copilot auto-completion).

Going forward now, I'd like to make a few repos to test out working from Pijul. VS Code doesn't have a Pijul extension (that I've found yet), so I'll have to do all my Pijul work from the terminal. I can use VS Code for editing, but I'll have to run the Pijul commands in the terminal. It's not bad, though, especially once I figure a nice one-letter alias for Pijul.

### Weird Chromebook Issue
A weird thing that happened was, halfway through the process of editing some stuff after my first Pijul push to the Nest, the Chromebook just up and died. Like, as if its battery died. I plugged it in and it came back, but the battery was still above halfway.

Some consideration that goes into what project is good for Pijul is what frameworks/platforms support it. Laravel Zero _might_ be able to publish to the PHP package thing it uses, but I'm not sure. But it's better chance, I think, than a web app. Although with Laravel Forge, I should be able to just get a server spun up, and use a custom deploy script. Install pijul beforehand.

## Going Forward
### Editor Setup
I'd like to make a few repos to test out working from Pijul. VS Code doesn't have a Pijul extension (that I've found yet), so I'll have to do all my Pijul work from the terminal. I can use VS Code for editing, but I'll have to run the Pijul commands in the terminal. It's not bad, though, especially once I figure out a nice one-letter alias for Pijul.
### Project Considerations
Some consideration that goes into what project is good for Pijul is what frameworks/platforms support it. Laravel Zero _might_ be able to publish to the PHP package thing it uses, but I'm not sure. But it's a better chance, I think, than a web app. Although with Laravel Forge, I should be able to just get a server spun up and use a custom deploy script. Install Pijul beforehand.