Replies (8)
Size of root filesystem on Amazon EC2 is not easily configured
Reply 1Are you kidding me
Reply 2I 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
Oh and...
Reply 3I'm going for an S3 rather than an EBS backed malarkey because we don't need to be switching anything on and off
The instructions are pretty clear
Reply 4And 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.
If you're configuring a mount
Reply 5If you're configuring a mount bind via Webmin, make sure you select the right type of device: loopback.
Still having Issues
Reply 6Thanks for the replies,


Glad you got it working
Reply 7As for updating the DNS with your new IP, try:
hubdns-update
IIRC it should auto run every hour as a cron job, but perhaps not?
Nearly there
Reply 8I 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)
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.