If you manage one or more Joomla websites, eventually you’ll have to move them elsewhere. It’s pretty much fact. Performance requirements will change, you’ll find better pricing elsewhere, your dedicated server died, etc.

There are a few options most people have to choose from:

• FTP client and phpMyAdmin method (aka the long, boring method)
• SSH/Shell method (aka the cool, quick method)
• PHP system() method (aka middle of the road and kind of fun method)
• Joomla “clone” component (your mom could do it)

pfizer's viagra

1. Download the entire Joomla website via FTP client (you’re using S-FTP to connect, right?)
2. Use phpMyAdmin to export a SQL dump of your database
3. Upload the entire Joomla website via FTP client
4. Use phpMyAdmin on the new server to import the SQL dump from the old website
5. Update configuration.php:
   1. Update the MySQL database credentials
   2. Update the tmp/logs path
   3. If you use FTP Layer, update the credentials
6. Update .htaccess to match any changed server requirements

Easy and straightforward. Long, slow process, but any Jr. Network Admin  could handle this for you if you don’t want to get your hands dirty.

pfizer's viagra

1. Login to your server via SSH
2. Browse to your Joomla website root
3. Run these commands:
   [code lang="bash"]tar -czf ../backup-example-com-20090619.tar.gz .

   mv ../backup-example-com-20090619.tar.gz ./

   mysqldump -u yourUsername -p -h yourMySQLHostname yourDatabaseName > backup-example-com-20090619.sql[/code]

4. Do you need to move this to a remote server or another location on the same server?
   1. Local Path
      1. Copy both backup files to the new website root
      2. Browse to the new Joomla website root
   2. Remote Path
      1. Login to remote server via SSH
      2. Browse to the new Joomla website root
      3. Use wget to download the archive and SQL dump to this server:
         [code lang="bash"]wget http://www.example.com/backup-example-com-20090619.tar.gz
         wget http://www.example.com/backup-example-com-20090619.sql[/code]
5. Run this command:
   [code lang="bash"]tar -xzf backup-example-com-20090619.tar.gz[/code]
6. Run this command (assuming you have made a new, blank database)
   [code lang="bash"]mysql -u yourNewUsername -p -h yourNewMySQLHost yourNewDatabase  < backup-example-com-20090619.sql[/code]
7. Update configuration.php & .htaccess as shown in the first example

More complicated (obviously), but if you like doing things the hard fun way, then it's a great way to go.

pfizer's viagra

I wasn't made aware of this method until after I started managing a whole slew of websites in a platform (). Cloud hosting (and many shared hosting platforms) do not provide access to SSH because it's simply not feasible. Cloud hosting in particular due to your website running across hundreds of different server nodes. You can perform the same functions as the SSH procedure above using system execution commands in PHP.

1. Create a new file called pfizer's viagrapfizer's viagra
2. Write the following code into this file:
   [code lang="php"]echo `tar -czf ../backup-example-com-20090619.tar.gz . && mv ../backup-example-com-20090619.tar.gz ./`;
   echo `mysqldump -u yourUsername -p -h yourMySQLHostname yourDatabaseName > backup-example-com-20090619.sql`;[/code]
3. Execute the PHP file by accessing it from a browser:
   pfizer's viagra
4. Create a new file on the destination website called pfizer's viagrapfizer's viagra
5. Write the following code into this file:
   [code lang="php"]echo `wget http://www.example.com/backup-example-com-20090619.tar.gz`;
   echo `wget http://www.example.com/backup-example-com-20090619.sql`;
   echo `tar -xzf backup-example-com-20090619.tar.gz`;
   echo `mysql -u yourNewUsername -p -h yourNewMySQLHost yourNewDatabase  < backup-example-com-20090619.sql`;[/code]
6. pfizer's viagra
7. Update the configuration.php and .htaccess files as needed

Cool, huh?

pfizer's viagra

If you prefer not to do anything yourself, and want to keep it as simple as possible, then a backup component from the JED is the way to go:

I have only used one of those components before, and I found that there were a few bugs needing to be worked out, and it ended up taking more time to do the backup, move, and clone that I needed to do than when I did so manually.

pfizer's viagra

There are shortcuts you can take here depending on your environment. For instance, you never need to create archives at all, as you can pipe the mysqldump output directly to another mysql command (with the new database's credentials). However, I prefer to use archives and solid files especially when using PHP-based method, because you could end up accidentaly accessing the cloner file and wiping an existing MySQL database (if you aren't careful). So, on top of all this, I'd recommend removing the update-me and copy-me files after using them.

The article covers the following topics:
• Optimizing the ASP.NET pipeline system
• ASP.NET, AJAX caching, and what you need to know
• Deploying ASP.NET from a staging to a production environment
• Optimizing the ASP.NET process configuration
• Using a Content Delivery Network (CDN) with your ASP.NET apps
• ASP.NET 2.0 Membership tables
• Progressive UI loading for a smoother, end-user, browser experience
• Optimizing ASP.NET 2.0 Profile provider

Original article:

pfizer's viagra You want to get the best deal possible. Shared hosting probably comes to mind first. In the classic sense, shared hosting means a company has a server, and they load as many websites onto this server in order to make the most profit from one server. Sometimes, this can mean hundreds of websites on one box. One box… susceptible to the same physical hardware limitations as any other server. Sure, they might even include RAID, redundant power supplies, and a lot of disk space.

However, what happens when your website actually starts getting traffic? I had an experience where my company put their trust in a shared hosting company (*cough* Dreamhost *cough*). When it came down to it, one of our websites had a lot of visitors one evening, and after battling to keep things running smoothly, the host ultimately disabled our website via renaming the index file to index.php_disabled_by_host. Seriously? So much for saving money and “unlimited” space and bandwidth… which brings me to my next point.

pfizer's viagra If you have a website that has outgrown shared hosting, what is your next move? Many people consider purchasing dedicated equipment for their website. A dedicated server is usually the first move. Not enough? Scaling out from this point then usually requires the purchase of another dedicated server and a load balancer, then it just gets pricier from there with a dedicated database server, file servers, caching servers, and more to handle growing traffic and load. We’re talking a significant amount of expenses just to get the ability to scale.

is the answer. The concept of a cloud host is that it takes the best of the scalable, dedicated world and lets you just pay for what you use. You put your website in the cloud and instantly your application is scaled across multiple webservers. Your files are stored on a redundant SAN mirrored across many physical drives. Database queries are performed on powerful, multi-node database clusters. You don’t have to think about “how am I going to handle all of that traffic?” because it just happens automatically. You no longer have to think about “do I need a Windows or Linux based account?”. It doesn’t matter. You can run ASP.NET applications side-by-side PHP web sites. It’s the cloud that doesn’t mind – it’s cool with whatever you want to do. I highly recommend checking out Ninja Systems, the company, if you are serious about scaling your website, and if you don’t want to waste your time recreating another scalable infrastructure that you need to manage yourself.

We all know backups are important. I’ve found what I consider a pretty good backup solution using Amazon S3. It’s super cheap, your backups are in a secure location, and you can get to them from anywhere. For my backup solution, I’m using Debian Linux (Etch), but this whole setup is not dependent on your current favorite flavor of Linux because it uses Java.

1. Signup for Amazon S3: http://aws.amazon.com/s3/
2. Install the latest Java Runtime Environment: http://java.sun.com/javase/downloads/index.jsp
3. Download Jets3t: http://jets3t.s3.amazonaws.com/downloads.html
4. Extract Jets3t installation to a location on your server.Example: /usr/local/jets3t/
5. Add your AWS account key and private key to the “synchronize” tool configuration file:Example: /usr/local/jets3t/configs/synchronize.properties
6. Use an S3 browser tool like Firefox S3 Organizer to add two buckets: one for file backups and one for MySQL backups.
7. Add a MySQL user whose primary function is dumping data. Let’s call it ‘dump’ with the password ‘dump’:
   [code lang="bash"]mysql>GRANT SELECT, LOCK TABLES ON exampleDB.* to 'dump' identified by 'dump';[/code]
8. Build your backup script (replace paths with your own) called s3backup.sh:
   [code lang="bash"]JAVA_HOME=/usr/local/j2re1.4.2_17
   export JAVA_HOME
   JETS3T_HOME=/usr/local/j3ts3t
   export JETS3T_HOME
   SYNC=/usr/local/jets3t/bin/synchronize.sh
   WWWROOT=/var/www/fakeuser/
   MYSQLBUCKET=example-bucket-mysql
   WWWBUCKET=example-bucket-www
   MYSQLDUMPDIR=/usr/local/mysql-dumps
   WWWDUMPDIR=/usr/local/www-dumps
   # Perform backup logic
   dayOfWeek = `date +%a`
   dumpSQL="backup-www-example-com-${dayOfWeek}.sql.gz"
   dumpWWW="backup-www-example-com-${dayOfWeek}.tar.gz"
   mysqldump -u dump -pdump exampleDB | gzip > "${MYSQLDUMPDIR}/${dumpSQL}"
   # Compress the website into an archive
   cd ${WWWROOT}
   tar -czf "${WWWDUMPDIR}/${dumpWWW}" .
   # Perform Jets3t synchronize with Amazon S3
   $SYNC --quiet --nodelete UP "${WWWBUCKET}" "${WWWDUMPDIR}/${dumpWWW}"
   rm -f "${WWWDUMPDIR}/${dumpWWW}"
   $SYNC --quiet --nodelete UP "${MYSQLBUCKET}" "${MYSQLDUMPDIR}/${dumpSQL}"
   rm -f "${MYSQLDUMPDIR}/${dumpSQL}"[/code]
9. Make sure your script has execute permission
10. Add a cron job to perform daily backups:
    [code lang="bash"]$>crontab -e
    0 0 * * * /root/s3backup.sh[/code]

That’s it. Good luck!

…or so we thought.

We moved our most important project of the day from it’s ol’ reliable hosting to the Dreamhost hosting (because that’s where we had been developing the new website). The new site looked amazing, and up to that point all testing had returned positive results.

The evening of the first day after moving to Dreamhost, I get a call around 10 PM about the site being down. Investigating, I found out that our MySQL database was being hosed. I open a ticket with the company (the only way to contact them), expressing the urgency of the issue, and asked that a tech investigate what was happening to our database.

A short time later, with no word from support, our database clears up. Sweet! We’re back in business. In about 6 hours, we receive a response from a Dreamhost tech, and he mentions that they don’t see the issue, but offered a helpful suggestion with a few MySQL commands: show processlist -and- kill <processid>. I think to myself, “Cool! If this happens again, I’ll have the tools to fix it.” With this strange event behind us, I put faith in them again. I even convinced the CEO that we have the tools to fix the problem if it happens again, which was entirely true, and that we didn’t need to look elsewhere for another hosting company.

Big mistake.

Two days later, we receive a support message from a different tech – a complete polar opposite of the last guy that helped us out. Here is what he said:

Hello,

I was investigating the high load on your MySQL server when I discovered
that your sql user was running the following query more than 100
times on the website database (here’s the beginning of that command):

select u.id, u.name, c.avatar, c.showOnline from jos_users u,jos_fb_users
c where u.id = c.userid AN

In consideration of the other customers using that server I have disabled
SELECT privileges for your database user. This has dropped the load on
your MySQL server from 180 down to around 15. Please optimize
your sites to run those queries much less frequently. Let me know if you
have any questions.

Thanks!
Craig

Awesome! I had been up until 3 AM that morning working on non-related stuff at home, and this guy decides to throw this at us at 6:45 AM on Saturday morning. The calls/emails start swarming in, and I’m up trying to figure out why the hell the site went down again. Disable SELECT permission on our main SQL user? Are you kidding?

Being the obstinate users that we are who like to be able to read data from their database, we re-enable SELECT permission for our main user. At the same time, I activated the built-in Joomla caching feature, bringing the load down to a minimum. Then I also removed code with the Joomla core that prevents browser-side caching, further improving the performance of our website. Take that! The website moves faster than ever!

Exactly one day later, we receive yet another message from our friendly neighborhood Dreamhost technicians saying that they have renamed our index.php file to index.php.Disabled_by_Dreamhost, citing too many connections on that specific file (Joomla is run off the main index.php file — go figure), and then “suggested” that we should look into Dreamhost Private Server. The kicker is that we already contacted them about DreamhostPS earlier, but were rejected because it’s invite only, and was still in the development phase. Whatever.

So the day this happened was a Monday, and I was supposed to have a day off because of overnight maintenance that needed to be done Monday evening/Tuesday morning. So I get the call that Dreamhost did this at around 9 AM, and so at that point we decide the screw Dreamhost and move. We move it back to a server in-house while we acquire a dedicated server elsewhere, and I spent most of my day off moving the website once more.

Happily, we now have a super fast dedicated server far away from the mingling hands of the Dreamhost techs.

With all this being said, I wanted to make some public apologies:
- I apologize to Dreamhost for putting a website on your servers that needed to use one of our unlimited number of databases.
- I apologize to Dreamhost for renaming index.php.Disabled_by_Dreamhost to index.php because our website was down.
- I apologize to Dreamhost for using an instance of Joomla byway of their built-in ONE CLICK INSTALL.
- I apologize to my company for ever considering using them for a website that has any interest in being nothing more than a stick in the mud.

I will admit that we had a lot of users, and that Joomla isn’t the most efficient engine out there, but the way Dreamhost handled the situation was very unprofessional, and we’ll be closing our account with them soon.

On the other hand, if you have a bunch of websites that don’t get any traffic, but need a place for all your domains, DH isn’t bad. I have my own account with them, and so far the 2 or 3 people that visit those websites on my account, haven’t had to deal with any down time. I’ll just have to make sure to move before any of them become popular…

pfizer's viagra

The first step is to tell IIS what system you would like the extension to map to.

1. Open your existing website in IIS
2. Browse to the Home Directory tab
3. Open the Application Settings Configuration (you should see a list of existing application mappings)
4. Click “Add”
5. Browse for the .NET Framework you want to use (e.g.: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll)
6. Enter the extension (such as .htm)
7. Limit the mapping to specific verbs (e.g. GET,HEAD,POST,DEBUG)
8. Check Script Engine
9. Uncheck Check that File Exists
10. Click OK and close IIS

pfizer's viagra

pfizer's viagra

The last step is to update the Web.config for your website so that ASP.NET knows how you want to manage these new extensions. You will first need to add in a new HttpHandler inside of the System.Web node:

<httpHandlers>
<add verb=”*” path=”*.htm” type=”System.Web.UI.PageHandlerFactory”/>
</httpHandlers>

Finally, we will need to add a buildProvider:

<buildProviders>
<add extension=”.htm” type=”System.Web.Compilation.PageBuildProvider”/>
</buildProviders>

Now save the Web.config file and run your ASP.NET -powered, non-standard-extension page!

For more information on BuildProviders,

Good luck!

Matt pfizer's viagra