I know its not best practice, but i know we are alot of frontenders doing it. Editing a live site through FTP.
I get that github is the way to go, but if your main development environment is the dev site, and not a local install, it would be nice to have ftp access to the dev site. Pushing changes from github every time you change a bit of css, template or javascript seems like overkill...
Just my personal comment about this - I think that even for a single developer it's beneficial to use a source version control system to keep track of code changes etc. It's easy to test stuff and it's easy to rollback to previous working versions if you for some reason fucked something up and don't want to waste time removing the stuff you can just rollback to the latest working commit etc.
I know it can seem like overkill to get started using GitHub or Mercurial but I think that once you have climbed the mountain there is no way back and it just makes your life easier. I use mercurial or github for my own pet projects where it's only me who develop. It's also nice that the code is backed up somewhere else than just locally and on the live site.
Im just starting out on the whole github thing, and during my reading up on things i got a sense that its bad "github practice" to push little changes (saves).
Good practice is to do something likes a days work locally and then commit.
The problem for me as a lone developer working on a Mac, is i dont have a local install of the site, and have no desire to have one. So i have to commit every small change to the dev site, to see my changes... And as far as i understand github that totally defeats the purpose of source control...
But maybe im missing something, that wouldn't be the first time :)
Remember that Umbraco as a Service is powered by Git, not Github (I know it's a bit confusing :-))
FTP won't happen and it's definitely better practice to commit often than to upload via FTP and once you're into the workflow, it's easier and less timeconsuming than FTP'ing. Also, there's no reason to fear the size of your repo or number of commits. After all - Git is - among other - powering the Linux kernel with more commits and a bigger repo than all projects you'll ever do in your life together.
Trust me that once you've gotten used to this, you'll never, ever want to go back.
For convenience, we're working on a Windows and OSX client that'll automatically push changes as you make them locally which ideal when you're the only developer (or you're in a team where you don't work on the same files). Think Dropbox for Umbraco and you'll get the idea :-)
FTP Access to dev site
I know its not best practice, but i know we are alot of frontenders doing it. Editing a live site through FTP.
I get that github is the way to go, but if your main development environment is the dev site, and not a local install, it would be nice to have ftp access to the dev site. Pushing changes from github every time you change a bit of css, template or javascript seems like overkill...
Is this going to be a possibillity?
Hi Claus
Just my personal comment about this - I think that even for a single developer it's beneficial to use a source version control system to keep track of code changes etc. It's easy to test stuff and it's easy to rollback to previous working versions if you for some reason fucked something up and don't want to waste time removing the stuff you can just rollback to the latest working commit etc.
I know it can seem like overkill to get started using GitHub or Mercurial but I think that once you have climbed the mountain there is no way back and it just makes your life easier. I use mercurial or github for my own pet projects where it's only me who develop. It's also nice that the code is backed up somewhere else than just locally and on the live site.
Just my 2 cents on the matter :)
/Jan
I totally agree on the backup issue.
Im just starting out on the whole github thing, and during my reading up on things i got a sense that its bad "github practice" to push little changes (saves).
Good practice is to do something likes a days work locally and then commit.
The problem for me as a lone developer working on a Mac, is i dont have a local install of the site, and have no desire to have one.
So i have to commit every small change to the dev site, to see my changes... And as far as i understand github that totally defeats the purpose of source control...
But maybe im missing something, that wouldn't be the first time :)
Remember that Umbraco as a Service is powered by Git, not Github (I know it's a bit confusing :-))
FTP won't happen and it's definitely better practice to commit often than to upload via FTP and once you're into the workflow, it's easier and less timeconsuming than FTP'ing. Also, there's no reason to fear the size of your repo or number of commits. After all - Git is - among other - powering the Linux kernel with more commits and a bigger repo than all projects you'll ever do in your life together.
Trust me that once you've gotten used to this, you'll never, ever want to go back.
For convenience, we're working on a Windows and OSX client that'll automatically push changes as you make them locally which ideal when you're the only developer (or you're in a team where you don't work on the same files). Think Dropbox for Umbraco and you'll get the idea :-)
Hope this helps!
Best,
Niels...
is working on a reply...