Hot answers tagged git
I know this isn't what you asked about, but I have to fully agree with Su' in the comments: if your hosting provider doesn't give you SSH access, you should seriously start looking for a new provider. It's not so much about the lack of SSH as such, but about the fact that your current provider apparently isn't giving you what's nowadays considered a very ...
I personally use Git for web development, and have adopted a method similar to this with our development server. I used Joe Maller's Web-Focused Git Workflow as a model, and it's been fairly successful. Joe's approach uses an intermediary "hub" repository that's been set up as a "bare" repository (git --bare init), because it's very tricky pushing into a ...
You'll probably want to branch your code or at the very least start using tags. I prefer the branch method so I can keep 2 copies of the site. One being my trunk version ( dev ) and another being the live production copy. Then I can just merge the changes to the production branch when I'm ready to publish and if something goes wrong on production I have a ...
Yes, the workflow makes sense. The only thing I don’t quite get is the need for a separate testing platform. I mean yeah, it’s useful if you have a testing team to give them their own platform, but if it's just you? Not so much. IMHO, for small-scale development teams, this sort of thing is unnecessary and becomes a hassle. I’m going to suggest the obvious ...
With a little searching of various questions on Google, I found a way. It may not be the best way and it may be over complicated, but it should work and that's the main thing. Though, if you know a better way or can find one, please do let me know! I found that you can deploy your code to your servers via Git hooks. All you need to do is SSH into your ...
I think most sites use a simple cron job to copy the files to a backup server. However, git is becoming the norm as it allows you to easily branch development and revert to earlier versions. I think what you are doing is fine. Regarding the database, why not back it up directly? At least, if it's MySQL you can simply back up the folder containing the ...
There isn't a canonical backup process any more than there's a canonical web structure/organization. But you mention that the repo's gotten bloated due to temporary files. Add the files/directories involved to .gitignore and they should no longer be a factor. There's obviously no reason to save them.
Shameless self promotion, but I asked this question over at StackOverflow a couple of years ago "Does anyone know of a decent free online bug tracker for web development purposes?"
As stated by @Jacob Hume I'd have an intermediary repository, setup your own, use Github or Bitbucket. You are likely going to run into difficulty synchronizing your branches between multiple developers if you don't use a hub. I usually pull updates into a staging/testing server to make sure everything is working, then do the same for production.
Your can add into httpd.conf container for Location (or Directory - TBT by you, I'm too lazy) with Allow Override None and affected htaccess will be effectively ignored
Only top voted, non community-wiki answers of a minimum length are eligible