*Sent:* Monday, 2 April 2012 5:43 PM
*To:* ozDotNet
*Subject:* Re: The cost of putting small websites online
** **
*The TC on the MSDN credits for Azure, don't they state that you can't
put production sites on it, only development sites?*
** **
Looking around, I can't find any
On Mon, Apr 2, 2012 at 3:41 PM, David Burela david.bur...@gmail.com wrote:
Are my calculations correct?
You're focussing on the smallest possible element of the cost of launching
one of these sites.
You also need to consider the ones that are going to make up 99% of the
cost:
-
Godaddy has .com registration for about US$6/year, and free DNS
Agreed with David that this is probably a fraction of the cost.
Cheers
Ken
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of David Burela
Sent: Monday, 2 April 2012 1:42 PM
To: ozDotNet
All the production quality issues are non-issues.
The goal here is a website to support hobby projects. Trying to get the
yearly costs down to support the hobby project is the #1 priority here.
The best way I've been linked to so far is hosting a site on GitHub and
using a mark down generator
Bitbucket supports basic website hosting, too:
http://confluence.atlassian.com/display/BITBUCKET/Publishing+a+Website+on+bitbucket
On Mon, Apr 2, 2012 at 4:20 PM, David Burela david.bur...@gmail.com wrote:
All the production quality issues are non-issues.
The goal here is a website to support
plug
If you're an MSDN subscriber, then you get Azure usage as part of that
subscription.
You can host multiple web sites on a singe Azure instance. In fact, what you
might want to do is have 2 extra small instances running multiple web sites so
you've got the umpteen 9's SLA.
/plug
:
@MitchDennyhttp://twitter.com/MitchDenny
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Andrew Coates (DPE AUSTRALIA)
Sent: Monday, 2 April 2012 4:58 PM
To: ozDotNet
Subject: RE: The cost of putting small websites online
plug
If you're an MSDN subscriber
*The TC on the MSDN credits for Azure, don't they state that you can't
put production sites on it, only development sites?*
*
*
Looking around, I can't find any specific details on if you can use the
MSDN credits for production use.
David,
Why not start with shared host first? Usually much cheaper than vps!
If your needs expand you can ramp up in future.
Places like mochahost have reasonable costs, plus allow multiple domains,
multiple database types and number for any future expansion. They even
offer free domain names on
2012 5:43 PM
To: ozDotNet
Subject: Re: The cost of putting small websites online
The TC on the MSDN credits for Azure, don't they state that you can't put
production sites on it, only development sites?
Looking around, I can't find any specific details on if you can use the MSDN
credits
993 • Fax: +61 (2) 9870 2400 •
http://blogs.msdn.com/acoat
** **
*From:* ozdotnet-boun...@ozdotnet.com [mailto:
ozdotnet-boun...@ozdotnet.com] *On Behalf Of *David Burela
*Sent:* Monday, 2 April 2012 5:43 PM
*To:* ozDotNet
*Subject:* Re: The cost of putting small websites online
-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Stephen Price
Sent: Tuesday, 3 April 2012 2:26 PM
To: ozDotNet
Subject: Re: The cost of putting small websites online
Damn it. Now I can't use cost as an excuse for not getting off my arse and
learning more about Azure. Ok
: The cost of putting small websites online
The TC on the MSDN credits for Azure, don't they state that you can't
put production sites on it, only development sites?
Looking around, I can't find any specific details on if you can use the
MSDN credits for production use.
https
just a thought, have you considered EC2?
If you're hosting multiple websites you can have them in the same place
which *may* make it easier for you - obviously the cost savings get
'better' the more websites you add.
I know you said you didnt want to be a system admin but really you get a
14 matches
Mail list logo
