FTP software and FileZilla


#1

Well, I got the website ready to load up and bought space on GoDaddy. They put me with FileZilla to load the code up. Problem is, GoDaddy did NOTHING when I had questions about FileZilla. Who has experience with this software? its a bit confusing how to do. Help, please?


#2

What exactly are you finding confusing?


#3

FileZilla is a standard FTP client. As long as GoDaddy gave you the login/password, you should be able to go into SERVERS, set up a connection using said login/password, if you like you can set a default local folder and a default remote folder, and then it’s just a matter of drag n drop.

V/r,

^ _ ^


#4

Hi there lombardy160,

perhaps one of these links will help…

  1. https://www.godaddy.com/help/filezilla-ftp-settings-to-upload-your-website-104
  2. https://uk.godaddy.com/help/ftp-upload-my-files-to-cpanel-hosting-96

coothead


#6

I use godaddy and ftp without a problem. The first thing you have to do though is go and create the ftp account. Just log into your account and go to cpanel and ftp.

Once you have that stick those details in filezilla and away you go.


#7

The problem is having files ready to load up, but NOT being able to tell EXACTLY which folder they should go in. Seems like it should be clear, but it isn’t.


#8

The online file structure I use is identical to my localhost.

FileZilla allows complete directories to be uploaded and when an identical online folder is recognised a pop-up box shows with options to overwrite all files and directories or only upload changed files. The latter I use frequently and is very fast.

The only very slow operation is to delete a folder which contains numerous files and sub-directories. This can take minutes!!!


#9

As @John_Betong says, you would normally upload everything with the exact same structure as you used on your local site when developing it.

There should be a folder on your site called www or public_html, and you just upload everything into that.


#10

There is one site I manage which is on GoDaddy, it uses public_html as the root directory which is a common name for the root.
Other sites may use other names for the root like httpdocs, .htdocs, wwwroot, Etc…

One feature of FileZilla which is very useful is the Synchonised Browsing, so when you change the view to one directory on one side, the other switches to the corresponding directory on the other.

If your server has nothing on it yet, you will start by copying all files and directories from your local root to the server root to build a mirrored directory structure.

If you have files/directories below the root, such as PHP includes for example, you would have to copy those too, to the same relative location on the server.


#11

I forgot to mention that and yes it is very handy.

Another useful feature available from the top drop-down menu is Bookmarks. Make sure you select Use Synchonised Browsing.

Yo may also try in the same drop-down menu Directory Comparison.


#12

So, T bear, just add my files to whatever is already there, in www instead of html public?


#13

I’ve never used GoDaddy hosting, so you should check with them if you’re in doubt. If there is a folder called public_html, that’s where I would upload the files.


#14

GoDaddy acts like this is NONE of their business. They just rented the space, have NOTHING to do with how its set up, or operated. Not a very helpful bunch.


#15

I’m surprised they didn’t at least give you an auto-reply pointing you to the “help” pages eg.
https://www.godaddy.com/help/ftp-upload-my-files-to-cpanel-hosting-96
https://www.godaddy.com/help/filezilla-ftp-settings-to-upload-your-website-104
https://www.godaddy.com/help/find-your-ftp-loginusername-4881
https://www.godaddy.com/help/what-is-my-ftp-host-or-address-19303

@coothead pointed in that direction a couple of days ago. You were able to get everything set up so you can get Filezilla to open your sites filesystem?

If you are confused about how to structure the filesystem that’s not really something the host should help with. How it is structured, for better or worse, is up to the sites admin. As others have mentioned, the typical way is to have it replicate the development structure. eg.

localhost

OS/ 
.. server/ 
.. .. htdocs/ # equates to live host domain 
.. .. .. includes/ # outside the "root" 
.. .. .. development_site/ # the "root" 
.. .. .. .. index.php 

live host

domain/ 
.. includes/ # outside the "root" sensitive files 
.. public_html/ # the "root" 
.. .. index.php