Right, so you want the root filesystem to be larger than 10GBs.
Unfortunately, the way Amazon EC2 works that is easier said than done.
You'd have to create an entirely new image. We could program the Hub
to do that but then you'd have to wait much longer for your machine to
come up. Much longer.
Instead I propose you create an EBS volume and mount --bind it to
wherever you want on your system. See this tutorial on how to move data
to instance storage. Moving
parts of your filesystem off to an EBS volume is similar in principle.
I must admit I tried that and ended up with /mnt on my joomla folder, could you be more specific with your instructions for a Joomla install, if you can do that I'll rack up an install and I'm yours
I'm going for an S3 rather than an EBS backed malarkey because we don't need to be switching anything on and off
And AFAIK (for the purposes of this) it is irrelevant whether you have an S3 or EBS backed instance.
Basically you should be able to use almost exactly the same commands as are used in the example Liraz linked to, but substitute /path/to/big/Joomla/folder (where ever that is) for /home in the example.
Thanks for the replies,
If you're configuring a mount bind via Webmin, make sure you select the
right type of device: loopback.
I had an exptra VAR where it shouldn't have been, all seems to be working well now except except for the fact that I can get the site by using the IP, but not the tklapp.com address :0)
As for updating the DNS with your new IP, try:
IIRC it should auto run every hour as a cron job, but perhaps not?
More information about formatting options