News for hackers. Stuff that matters.
Re:Connecting a Git Repository to Amazon S3 and AWS Services by ge96 on Wednesday September 13, 2017 @01:46AM (#15235860)
Yeah you're right, sorry said the wrong one (t2.micro) it's funny when you look at it, it seems cheap like $0.012/hr but you multiply that by 750 and yeah... I briefly went up to t2.medium and I was like damn $30/mo for a server, that's a lot (to me).

OVH has nicer prices for roughly same specs eg. 2cores 8GB ram at I think $16/mo but that detachable/scalable is really nice without data loss on server configs.

Yeah good point about the year, I was surprised when I was charged the $99.99 for Amazon Prime haha

Re:Connecting a Git Repository to Amazon S3 and AWS Services by isatty on Wednesday September 13, 2017 @02:50AM (#15236069)
Trust me, you don't need scalability. For a personal server, get a VPS (get one from a provider that charges you a fixed monthly, don't get one with a shitty cpu (somewhere like DO/Linode does fine for your use case)).
Re:Connecting a Git Repository to Amazon S3 and AWS Services by ge96 on Wednesday September 13, 2017 @05:03AM (#15236630)
I use OVH right now I like them but I recently came across the free AWS tier as well, just messing around, a client insisted on using AWS so I set one up with CentOS (not regarding the private Git). Migrated their WP site from DO to AWS EC2. I'm messing with Private git because I can't justify the $7/mo cost through GitHub.

yeah I run a vps too, multiple domains but I do like that functions as a service approach.

I unfortunately started with GoDaddy haha hilarious, overpriced that economy $1 thing garbage.

Just my opinions but yeah... had some caching problems too wouldn't replace the content ahhhhh. Saying it was my fault "flush dns" I'm testing with Tor externally in other countries. Also I'm using Ubuntu no flushing required I don't know.

Edit: moving up to t2.medium was because I implemented defuse/php-encryption and it took a toll encrypting decrypting, didn't help I had a dumb mistake where the cloning of data was stacking and not deleting so it was getting longer and longer... I know can use a better language but PHP is what I know at this time. I was able to drop back down to a t2.small but damn MySQL man... uses so much resources... with 2GB RAM it's idling like at 1.4GB or something... it just grows. I know you can tweak the settings. It's built on WordPress, I'm suggesting to strip the function of the site out of WordPress but future improvement.

Edit: not crapping on WordPress the plugins/dynamic aspect is cool and if I thoroughly understood it my shit wouldn't be so janky. I interfaced with an Evernote Sync plugin and was surprised the comments were in chinese haha but it's PHP so I could read the code.

Using memcache(d) was cool, yeah it was a cool job all in all.

Edit: You know what's hilarious is HIPAA compliant servers DAMN! That's expensive, I clearly was not using HIPAA servers as those were $300 - $600/mo at least. But not just that but the architecture of the site, I clearly expressed that I am not a security expert. But AWS goes over a bit on the design of separating interface with the storage of data. At least we've got zero-knowledge design of everything encrypted... that's kind of a problem in a way too, when the key-obj to encrypt is not known and you've got strings that you can't decrypt and you start getting "failed to decrypt" error messages like "oh shit..." I think that was just an initial config though hopefully.

Had a recent never-ending loop problem wow... you can watch the server spike to 100% CPU usage in HTOP and you're like "ah crap something's wrong"

Re:Connecting a Git Repository to Amazon S3 and AWS Services by finspin on Wednesday September 13, 2017 @06:24AM (#15236983)
Regarding private git repo, have you looked into Bitbucket? They offer unlimited free private repos. I've been using them for about half a year, very happy so far.
Re:Connecting a Git Repository to Amazon S3 and AWS Services by ge96 on Wednesday September 13, 2017 @06:49AM (#15237070)
Haha... research right?

That's funny. I'm curious what's the catch besides someone else hosting your data of course that's ridiculous/how do you explain using everything else...

Good point and thanks. Would trust their setup more than mine, speed up the learning process too but it wasn't bad setting it up.

Re:Connecting a Git Repository to Amazon S3 and AWS Services by mikeash on Wednesday September 13, 2017 @09:51AM (#15238218)
I've been using Bitbucket's free private repositories for several years and it works great for me. I think the catch is just that you can only have five users on a team, so you need to convert to a paid account if you bring in more people. If it's just your own stuff, then obviously that's not a concern. I think it's just a loss leader to bring people in and try to convert some of them to a paid offering at some point.
Re:Connecting a Git Repository to Amazon S3 and AWS Services by ge96 on Wednesday September 13, 2017 @03:25PM (#15241696)
Yeah at this time I'm the only developer for where I'd like to apply git to.

Thanks a lot, would speed up the process not worrying about the permissions/setting it up. Still have to read some guides on Git but yeah I appreciate the tip.

I also like that it's not on the same server as the production server just because that one has limited resources at this time. Granted again it's just me.

Re:Connecting a Git Repository to Amazon S3 and AWS Services by guiriduro on Wednesday September 13, 2017 @08:24AM (#15237581)
...or gitlab, very nice (and free) repo hosting, in-house or online.
Re:Connecting a Git Repository to Amazon S3 and AWS Services by AlienTechnology on Sunday September 17, 2017 @05:16PM (#15271744)
+1 for Bitbucket
Re:Connecting a Git Repository to Amazon S3 and AWS Services by isatty on Thursday September 14, 2017 @12:08AM (#15244934)
I've run HIPAA complaint services in AWS normal, dedicated instances with encrypted RDS (Postgres) as the data store. Orchestrated for redundancy and never cost me anywhere near those numbers!
Re:Connecting a Git Repository to Amazon S3 and AWS Services by foepys on Wednesday September 13, 2017 @04:54AM (#15236589)
I am paying 4,63€ for a VPS that would cost me $30 on AWS. If you don't need scalability, always look into traditional (VPS/bare-metal) hosting.
Re:Connecting a Git Repository to Amazon S3 and AWS Services by ge96 on Wednesday September 13, 2017 @05:09AM (#15236653)
Yeah paying in advance helps too I do 1 year for like $40-$50, single core 10GB 2GB ram

edit: the one for $30/mo on AWS is 2 Core, 4GB RAM, like 30GB space, what specs are you getting for that price? For me roughly that (though $ is not as strong) that's what I mentioned above through OVH.

Re:Connecting a Git Repository to Amazon S3 and AWS Services by foepys on Wednesday September 13, 2017 @05:47AM (#15236811)
I'm at Hetzner and I'm using it for some bandwidth-hungry stuff. Hetzner includes 2 TB egress traffic per month which alone would cost me about $60 on AWS. It's easy to forget about the data transfer when looking at AWS/GCP/Azure prices.
Re:Connecting a Git Repository to Amazon S3 and AWS Services by j_s on Wednesday September 13, 2017 @07:14AM (#15237177)
If you genuinely need bandwidth, there are providers that offer unlimited bandwidth that HN users have tested:

https://news.ycombinator.com/item?id=14247795

> notamy: I have an application on OVH (on the USD $3.50/month plan) that pushes/pulls >10TB/month

That entire discussion is recommended for anyone looking for a cheap VPS.

Re:Connecting a Git Repository to Amazon S3 and AWS Services by ge96 on Wednesday September 13, 2017 @06:20AM (#15236969)
Wait is data transfer equivalent to bandwidth? I never even look at bandwidth. Sorry if that's obvious I have seen that "metric" before and didn't click till now.
Re:Connecting a Git Repository to Amazon S3 and AWS Services by vidarh on Wednesday September 13, 2017 @06:40AM (#15237037)
For really low bandwidth stuff (<1GB month) it won't hit you with AWS. But as soon as you're over that, it gets real expensive real quick. E.g. 1TB on AWS (traffic out of AWS) costs you $90 most regions, I believe, while you often get at least that much included elsewhere.

For Hetzner as mentioned, once you exceed the included bandwidth (which for most VPSs and servers is 2-3TB at least per month), it costs less than 2 euro/month extra.

This isn't likely to affect you for a personal git repo, but mentioning it as it's one of the things that often burn people with AWS, as the AWS bandwidth rates are crazily high to the point where for high-bandwidth applications even if you want/need to use AWS it's sometimes cheaper to run your own CDN in front of it to reduce bandwidth charges.

My order of preference if I don't need AWS specific services tends to be Hetzner, OVH and Digital Ocean, depending on what additional geographical regions I need (Hetzner is only in Germany) or other service requirements.

AWS is great for specific use-cases as long as you keep a close eye on costs.

Re:Connecting a Git Repository to Amazon S3 and AWS Services by ge96 on Wednesday September 13, 2017 @07:39AM (#15237282)
Wasn't able to respond to you earlier

Thanks for the tip, I wasn't even considering bandwidth. I think when I first was setting up EC2 I got a "bad batch" if that's a thing, I should say instance. I couldn't figure out why the TTFB was varying from 3-5 seconds I tried so many things eventually I had to switch and since I didn't have elastic IP I think, I switched servers (regions) to whatever I was assigned on restart and it was instant/correct like in the 10s/100s ms range. Anyway I'll keep an eye on that, don't have users yet but something to keep in mind, thankfully not really serving media mostly text.

Re:Connecting a Git Repository to Amazon S3 and AWS Services by foepys on Wednesday September 13, 2017 @07:42AM (#15237300)
For very fresh comments, HN disables the reply link on the comment overview to deter flame wars. You can click on the comment date to see only the single comment and then the reply link will be visible. Or just wait 2 minutes.
Re:Connecting a Git Repository to Amazon S3 and AWS Services by ge96 on Wednesday September 13, 2017 @07:55AM (#15237376)
That is interesting, I like it.

I don't know I am often wrong, just need to learn how to deal with it, the proper thing is to accept/thank/learn move on haha.

Re:Connecting a Git Repository to Amazon S3 and AWS Services by notheguyouthink on Wednesday September 13, 2017 @08:58AM (#15237795)
Where from? Care to plug them?

Assuming you like them, trust them, etc. My home "server" was... "reclaimed" recently and until I buy new hardware I really should get my shit up and running again.

Re:Connecting a Git Repository to Amazon S3 and AWS Services by foepys on Wednesday September 13, 2017 @09:45AM (#15238148)
Hetzner in Germany. If you want international hosting, look into OVH and Scaleway.