Using git to push and pull repositories.

I’ve been trying to get more proficient with git and figured the only way to do that is to get my hands dirty and write some simple app(s) and push them to a production server. There are my notes, mainly for me to help me remember how this stuff works.

The very first time you do a git init to initialize your repository.

git init

You do this every time you want to add new changes to your reposiotry.

git add .

To see the status of things which are going to be added, removed.

git status

Once you’re happy with what you want to commit, leave your future self a little love note.

git commit –m “Doing something”

You only do this the first time to setup your remote repository destination.

git remote add origin git@github.com:dmaciasSS/myrepo.git

Then you do this every time you want to push your commit.

git push –u origin master

--

Now, let’s say I want to pull my repository to a new host e.g. production. If you’re using Laravel make sure you’re setting up your environment name in your vhost file first.

sudo git clone https://github.com/dmaciasSS/myrepo.git locaton/in/my/server

Laravel specific commands.

chown -R :www-data app/storage chmod –R 777 app/storage ‘composer install’ php artisan cache:clear

--

Now, once you’ve cloned your repository you need to updated it every time you want to pull down any new commits.

sudo git pull origin master composer update php artisan cache:clear

~david

No comments yet

On Bluesky

@dmacias.bsky.social on Bluesky

David Macias@dmacias.bsky.social

Anyone actually seen an outcome-based contract from a BPO or a CCaaS vendor? Those documents must run to encyclopedia length, no room for error on what an outcome is or how it's measured. Maybe the only ones winning this AI race are the lawyers.

1 reply · View on Bluesky

David Macias@dmacias.bsky.social

Magic Quadrant poll results: 23 votes, 15 leaned disagree, 8 agreed. The 2026 quadrant does not match the reality most of my network sees.

1 reply · View on Bluesky

David Macias@dmacias.bsky.social

New Five9 survey: 46% of customers rated their last chatbot experience positively, vs about two-thirds for a human. The top reason people bail on the bot? It repeatedly misunderstood them. Turns out the human exit isn't the failure mode, it's the feature.

1 reply · 1 like · View on Bluesky

David Macias@dmacias.bsky.social

Remember when every vendor said AI's focus was not to reduce agent count? Well how about it reducing your agent license count? Zoom CX is moving to one spend pool for seats, apps, and AI. A seat you can count. A draw-down pool is their meter, and renewals just got harder to justify.

1 reply · View on Bluesky

David Macias@dmacias.bsky.social

A VC firm read 67 SaaS earnings calls and concluded AI is great for SaaS valuations. Anyway, the underlying numbers on outcome pricing and MCP growth are worth your time if you read past the pitch.

1 reply · View on Bluesky