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)

canadian pharmacy online 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.

canadian pharmacy online 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.

canadian pharmacy online 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 canadian pharmacy online viagracanadian pharmacy online 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:
   canadian pharmacy online viagra
4. Create a new file on the destination website called canadian pharmacy online viagracanadian pharmacy online 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. canadian pharmacy online viagra
7. Update the configuration.php and .htaccess files as needed

Cool, huh?

canadian pharmacy online 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.

canadian pharmacy online 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:

# Deny all search bots, web spiders
User-agent: *
Disallow: /

The website hailed by Obama and driven by the motivation to have a “transparent” government is attempting to hide the content on it’s website? Seems kind of fishy to me.

Personally, I believe it’s a simple mistake on the part of the developers, and that disallowing search engine traffic via robots.txt is a common practice. However, I think it’s a topic worthy of discussion.

Original CNET article .

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!

What do you do?

To build your own Joomla video community from the ground up, you will need to:

1. Create your own video player – most likely it would be in built in Flash
2. Convert raw videos to an Internet-appropriate size & quality
3. Upload your converted videos to your server (or hosting provider’s server)
4. Keep a close eye on your server resources: disk space and bandwidth in particular. Videos will fill up your free space much more quickly than images, web pages, or any other type of file.
5. Install a Joomla video gallery component that provides support for using your own files.
6. Optional: If you want to allow users to “stream” videos (meaning they can jump around different parts of the video without downloading the entire thing), it will usually require a separate streaming server, and someone with the technical know-how to get things running smoothly.

For those who don’t have the opportunity, time, know-how, or resources to do the above, then what other option do you have if you don’t want to have low-quality videos with another business’ branding?

The answer:

JVideo is a component – with it you can upload videos, organize videos, stream videos, and more. You don’t need to purchase additional hardware or worry about your videos directing your customers elsewhere. JVideo uses an API powered by Infinovision, so all you need to do is setup an account, install the component, and you’re good to go. It’s a new way to think about video hosting. In fact, you pretty much don’t have to think about it.

Check out the video below from the JVideo demo site and compare it to the YouTube equivalent (try full-screen for a real eye-opener):