Learn how to use a VPS? Static pages with NearlyFreeSpeech? I've got a zillion ideas (and after seeing this, will be building them soon) but they need to be on separate domains. Paying $5/month or whatever for each is obviously not optimal.
http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosti...
Quick guide:
- Create a bucket for each website, named after the domain (e.g. "myproject.mysite.com")
- Turn on static website hosting for the bucket (through the AWS Console)
- Go to your DNS provider and create a "CNAME" record pointing "myproject.mysite.com" to "myproject.mysite.com.s3-website-us-west-1.amazonaws.com" (The AWS Console will give you the exact domain to use here)
- For super-easy deployment, use s3cmd's sync utility (http://s3tools.org/s3cmd-sync) to upload all changed files in your project:
$ s3cmd -v sync ./ s3://myproject.mysite.com/ --acl-public- Needs to be versioned with git to be deployed
- Space limitation (I assume, not sure what it is)
- Deploying new content to S3 is a lot faster - github pages has some sort of build process with a substantial delay
TLDR is "create a separate directory for each site with the directory being called the URL of the site" e.g. /var/htdocs/www.domain1.com has the web pages for http://www.domain1.com/ .
The minor downside is that you'll be responsible for keeping your server up to date, but with a bit of upfront work you can mostly automate it.
If you are really interested in learning, pick up a VPS. Running one is as easy as you WANT it to be. Configuring and managing your VPS optimally is dependent on your projects and your goals. It can get complex pretty fast, especially when you don't know what you are doing. After studying about them in my spare time I have learned how severely insecure most people allow themselves to be. Fair warning to you!