3 ms·
Since I have web hosting and use GitHub, here's my method: cp file_name ~/Projects/2012/ajf.me/ajf.me/imagedump/ && cd ~/Projects/2012/ajf.me/ajf.me/ && gi
by TazeTSchnitzel 14y ago
Since I have web hosting and use GitHub, here's my method:
cp file_name ~/Projects/2012/ajf.me/ajf.me/imagedump/ && cd ~/Projects/2012/ajf.me/ajf.me/ && git add imagedump && git commit -m 'new file' && cd .. && ./update.sh
Elaborate, sure, but it does the job. update.sh runs git push and then does an SSH into my server and a git pull. (Because I'm too lazy to actually set up git on my own server)
- hk_kh 14y agoSetting up your own git server is pretty easy, in fact, trivial with ssh + authorized_keys I could refer you to any tutorial, but I am feeling lazy too, so here, an easy guide: -- On the server -- 1. create an account, call it "git", or "dog" 2. disable shell access for that account in /etc/passwd - /bin/false 3. enter that account, and set up a bare git repo: - mkdir myrepo.git - git init --bare myrepo.git 4. add your public key(s) to ~/.ssh/authorized_keys on "git" or "dog" account -- On your client(s) -- 1. Clone the repo - git clone git@your_server:myrepo.git - dog@... Ready to go. You can even use git hooks to automate the pull.
- SoftwareMaven 14y agoYou don't need to set up a git server on your own sever. Just create a git repo, add it as a remote revenue to your local repo, and use ssh+git to push changes directly. But if you have your own server, why don't you just scp it directly there? That's the piece most people are missing.
- xxbondsxx 14y agoSCP is really the solution here. But to be fair, I only discovered scp after a year or two of CLI work. I might have been tempted to hack something together like Taze's solution in my earlier days