5 ms·
Maybe dirty, hackish code for personal use only shouldn't make it out into the public ;-)
by ygra 13y ago
Maybe dirty, hackish code for personal use only shouldn't make it out into the public ;-)
- spoiler 13y agoWhat if op doesn't want to pay for private repositories to store his hackywhackys or wants to share them with others?
- krapp 13y agoBitbucket lets you have free private repositories. That's where i'm storing my dirty laundry at least...
- seandougall 13y agoLots of generic hosting providers can be used for it too, if you have a hosting account somewhere. As long as the server has git and you have SSH access, you can do this on the server side: $ mkdir project_name.git; cd project_name.git; git init --bare Then locally, from the repo directory: $ git remote add origin username@server.com:~/path/to/project_name.git That's what I do (on Webfaction). Of course, then you don't get all the fancy issue tracking and all that from github, but it works if all you need is a few kb of storage for a remote. That also makes it easy to deploy PHP projects with a single post-receive hook, since it's all in the same box.
- cgore 13y agoOr type slightly less: $ git init --bare project_name.git It will make the directory for you.
- freehunter 13y agoI would expect any code marked "quick hack to solve [obscure problem], not for production!" to be pretty clear. If someone is encountering the same problem, the code is there for them to use. If they happen to use it in production, that's hardly my fault.
- mesozoic 13y agoTechnically if the code doesn't have an open source license attached then it is still their copyright and isn't up for you to use even if on Github.
- Killswitch 13y agoJust because it's dirty doesn't mean someone else can't use it and make it clean.