I can push my changes to the _origin_ (github or bitbucket) but I can't push them to the web server that site was running on. That server didn't even have git installed and I did not have SSH access to it either. My employer at the time was a big fan of editing files on the live server. If a file used in multiple projects on the server had a bug he'd do a mass find & replace on all copies of that file across the whole server and forget to notify me. If I didn't do a check with the sync feature of Transmit to spot differences like that before uploading my own changes I'd inevitably overwrite something important and be in big trouble :( But mainly I've never learned how to setup whatever git-hook / ssh things that need to be set up in order to just push straight to the server. The best I can manage is to push to origin then ssh into the server and do a pull from origin. But when you're dealing with some old ass php servers and cooperating with people who like to edit the live server it's sadly often best to ftp your changes regularly to see if they even work as expected on the live server and when they don't you often have to do all your trial and error coding on the live server until it works. Then you download the working code and commit it locally, then push to github or bitbucket. The rest of the web dev world is not as advanced as the latest node js tutorial videos make it seem.
Now that makes perfect sense; I was just wondering. That must have been fun having a boss modifying your files. I've been using Pantheon for our servers where I need git control, but for those servers we only use for Wordpress and Drupal. Not sure if you do mostly CMS stuff, but on Pantheon and I think some similar companies (i.e. WP Engine, Acquia) all the server side git stuff is already set up so it's mostly plug and play. Enjoy.
I´m new to sourcetree, an this video is just confusing. It´s not fit to be a tutorial at all.
Thanks for the video. Just wondering why you would use an SFTP client (Transmit) when you could simply push your changes using SourceTree?
I can push my changes to the _origin_ (github or bitbucket) but I can't push them to the web server that site was running on. That server didn't even have git installed and I did not have SSH access to it either. My employer at the time was a big fan of editing files on the live server. If a file used in multiple projects on the server had a bug he'd do a mass find & replace on all copies of that file across the whole server and forget to notify me. If I didn't do a check with the sync feature of Transmit to spot differences like that before uploading my own changes I'd inevitably overwrite something important and be in big trouble :(
But mainly I've never learned how to setup whatever git-hook / ssh things that need to be set up in order to just push straight to the server. The best I can manage is to push to origin then ssh into the server and do a pull from origin. But when you're dealing with some old ass php servers and cooperating with people who like to edit the live server it's sadly often best to ftp your changes regularly to see if they even work as expected on the live server and when they don't you often have to do all your trial and error coding on the live server until it works. Then you download the working code and commit it locally, then push to github or bitbucket.
The rest of the web dev world is not as advanced as the latest node js tutorial videos make it seem.
Now that makes perfect sense; I was just wondering. That must have been fun having a boss modifying your files. I've been using Pantheon for our servers where I need git control, but for those servers we only use for Wordpress and Drupal. Not sure if you do mostly CMS stuff, but on Pantheon and I think some similar companies (i.e. WP Engine, Acquia) all the server side git stuff is already set up so it's mostly plug and play. Enjoy.