You get a few zeroes wrong there? Looks like you forget some of the magnitude differences in the units.

Yes, he was using the wrong units. Consumer electricity rates are about 15 cents per kilowatt-hour, not 0.15 cents. The final answer of almosdt 30 USD per month was correct.

Note that this is entirely based upon location as well, as the average rate in the United States is only 9.84 cents, with a few states hitting 15, and poor Hawaii at 34 While this data is from 2013, for my state it is still much higher than the rate we are charged. This is due to possibly different regions inside a state having varying costs as well. During winter I start at 5.5 and decrease to 4.6, and summer is 5.5 to 9.5.

Taking the average of all three power rates per month for me it comes out to about $130.. so basically the same price as paying a $10 service.

Since there is a computer running as a simple network drive for easy file sharing that won't suck up data usage it made sense for me to shove svn onto that computer. Sure I could get a free private repository someplace, or even pay for one, but for me this seemed like the best option with what I had. Plus at the time I wanted to learn how to do it just on the off chance I needed to do something similar later on.

My biggest gripes deal with the web interface for CollabNet. Sometimes it doesn't load properly so I have to manually start it, or do a quick reboot every now and then. Adding user permissions is tedious as well. Not that this process takes more than a few minutes, it just requires me to manually find the entry, write their name ect. Paying a service that does this all automagically would definitely be alot easier.

Other than that the remaining annoyances for me are just small things. Storms are of an equal concern as any other electronic device in the house. Gotta remember to turn it off/back on, just in case. General maintenance to make sure everything seems alright and the drives are running ok, and so on.

When I change locations here in about a year and a half though I am definitely going to just pay someone to host. There are features that I want but don't want to spend hours setting them up. Or some I just weren't able to get working at all. Sending a commit email I see as beneficial when working in a team, but I wasn't able to properly setup SMTP. It's just easier to have someone else handle that for me

Deveo (https://deveo.com) offers 1GB free disk space from cloud, after which the exceeding storage is priced relatively cheaply (1€/GB/month). There's issue tracker and Wiki in addition to plain SVN hosting. It might be better to spend 4€ / month and avoid all the configuration hassle.

Disclaimer: I work at Deveo.

Instead of a PC you can use a NAS too [...]
If the NAS is not able to handle SVN (either it does not allow installation of SVN or the processor is not powerful enough), you can still use it as simple data storage for your repository (much like a cloud-storage) and install SVN on your dev-machine. Thought this will not be really useful in a multi-user environment.

Why not use tortoise svn in that case. Free and space is limited to your hard drive capacity.

Those two, definitively. There is really no sane reason to do anything different if you do not need to share your code with people you don't know. Which, as you said, is explicitly not desired.

1. Local harddisk with TortoiseSVN is 15 seconds setup, and as fast and easy as you can get. Note that it's also as easy as you can get to accidentially delete the repo, so be sure to make backups.
2. NAS with TortoiseSVN via simple SMB shares or iSCSI is practically the same speed (SMB is somewhat slower, no noticeable difference with iSCSI due to its excellent caching), and it's 2 minutes of setup. Cost for a reasonably good (not stellar) NAS with reasonable storage is very manageable, although I'll admit it can get expensive if you feel like having the biggest, best thing.
3. Running SVN on the NAS is possible, but I find it actually inferior because the management interfaces are rather spartanic, and at least on Synology the SVN server is noticeably slower than using file protocol over iSCSI (probably due to the ARM CPU being on the weakish side?). Still, if you need to share your code with other people who access your NAS via VPN, that's the way to go. DynDNS, VPN, and SVN ready-to-go is like 5 minutes of setup, no skills required. With scheduled backup plan, it's like 6 minutes.

While I do see the merits of having data on a public server (if the situation demands for it) and while I do see the temptations of the almighty cloud, I find it stunning how the first thought most people nowadays seem to have for any kind of problem is "remote server", and "cloud". It is not automatically an invalid option, but in my opinion it should be the last, not the first consideration.

Maybe I'm just getting too old. I recently talked with someone who has one of these fitness trackers that monitors him 24/7, and you guessed it, the data goes right into the cloud. Heck, not only do I not see the merit of that or the technical reason, but I wouldn't even want to have a company with an obscure privacy policy (which they'll likely break anyway) plus in principle the entire world being able to access my vital parameters every day of my life, like when am I sleeping or when is my heartbeat so-and-so-fast... not everything needs to be accessible online, or should be. I don't see the merit of being able open my window shades or turn the lights on, or unlock the front door via the internet either (yep, no joke, this is something one of those smart home guys actually tried to sell to me, stunningly ingenious idea that, remotely unlocking the front door).