V1 Starter Guide

V2

This document relates to the CacheFly V1 platform. For documentation relating to the CacheFly V2 platform please see our new Help Guides.

V1

Hello and Welcome to CacheFly!

In this article, we will walk you through getting started using CacheFly's CDN. 

By default, your CacheFly account is setup for you to FTP your static files to our origin. 

Let's begin by signing into the customer portal located at https://portal.cachefly.com .

Once logged in, you'll be greeted by a landing page that contains Account Details. These details include your username, subdomain, FTP password and FTP server;

You'll begin by uploading your static files to ftp.cachefly.com.  (If you require SFTP, SCP or RSYNC, please contact support through your customer portal and we can work with you to get that enabled.)

Start by opening your FTP client on your local machine. For more information about selecting an appropriate FTP client, please refer to a client comparison. 

In your client enter in your username, host (ftp.cachefly.com), password, port (default port is 21) and then click on connect. 

Once connected you can begin uploading your objects. We support the creation of subdirectories so that you can build your file hierarchy as you see fit. 

Using the example details form the above screenshots, say we connected to ftp.cachefly.com and created a directory called "images". We then upload a picture into the /images directory called test.jpeg. After you've disconnected from ftp.cachefly.com, your uploaded object will be available at http://demo.cachefly.net/images/test.jpeg . This is the URL that you'll use in your HTML source. 

Some items to note are;  

• Once you're finished uploading your objects, please use your FTP client's disconnect (instead of just closing the client). Not doing so can leave "stale" FTP sessions.
• Mind special characters and spaces in filenames. Special character will need to be URL encoded when accessing them via a URL. 
• Refrain from linking to a CacheFly served object until it has completely been uploaded. We don't want you end-users getting 1/2 of a file ;)