Hot answers tagged git
9
That depends on your exact way of doing it. Right now it seems to me you have a git repo in your httpdocs that you deploy to, basically using HEAD as your actual website - that is NOT the correct way. I'm not sure how you are able to push to this configuration at all?
What you want to do is use a bare repo somewhere outside the httpdocs-folder, and checkout ...
4
Take a look at some code quality and code indexing tools.
FishEye
For starters, you could use FishEye, which would index your code and allow you to quickly query for code from all the repositories so you can keep a bird's eye view of the whole codebase.
For instance, you could search for a given file (but also for a file's content, including a method ...
4
I suspect I may get downvoted for this, but I wanted to throw this out there anyway.
I think including the DLLs themselves is really not a bad idea.
Sure, they aren't text; but that is true of plenty of asset types that commonly are included in source repositories (e.g., images).
Sure, you can't really diff them; but that is true of other compiled ...
2
I think using git to manage the set of files needed to run your site is a clever idea.. as a matter of fact there are several services already doing this (as far as I know): microsoft's azure and some node.js hosting sites like nodester.com, just to name a couple..
As also @phi said, I'd not place the repository on the very same folders you publish through ...
2
If nuget is not available, the cleanest way may be to provide an export script which pulls the source code of the needed library from their external repository (of the library vendor) into your working directory. This will work even if the SCC system of the external libs is different from Git (as long as it has a command-line interface). EDIT: this will work ...
2
Bitbucket allows for private repositories. As the repository owner, you can add people to the repository and set whether they have read or write access. They'll need accounts on Bitbucket, but signing up is free.
I actually prefer Bitbucket to Github; the UI is (in my opinion) a little nicer.
2
Did you consider Dropbox? It does not require registration if you send out the public link, it can show you the source code (albeit not very nice), and people can simply download all they need.
This obviously only works if your colleagues do not contribute to your code. To simplify the process, set up a new branch 'Dropbox' or 'Final', and add a post-commit ...
1
You have 2 options:
1. by git way: use submodules. Here is a documentation how git manage submodules git submodules. I personally didn't use it but it looks to fit your problem.
2. by maven way: in maven it is not mandatory that your root project (configuration) to be hierarchically the parent directory of all your projects. You can have a structure like ...
1
What you might want to look at is multiple repositories here forked off of a main development template line. This lets you keep some centralized templating while letting the downstream projects keep a bit more in control of their own destiny -- including holding patches to the core if you need to roll that way.
We used a strategy like this for a half-dozen ...
1
I think you're confusing the role of source control with the role of software architecture and proper dependency management.
If you've got a templating system, or just a template, that you want to be able to roll out to multiple sites, then you design it as a standalone framework which can be customized in certain predictable ways. This is how CMSes like ...
1
GitHub Gists allow a URL-only 'secret' access but I don't believe you can clone a repository to it; you'd have to add the files by hand. This is OK for a small number of files but if you have a lot then it probably won't work for you.
However, as gists are git repos, you may be able to push changes to it.
1
Assembla offers a free git repository that is private and an integrated bug tracking system - you can change ticket statuses or track time directly through your commit messages. They also offer custom server-side hooks - which allow you to write your own logic and then use it - anything from rejecting commits that do not match certain rules of yours, to ...
Only top voted, non community-wiki answers of a minimum length are eligible
