I am just a beginner in HTML (and soon JS), and I was wondering, once my website is complete (an html file made in either Sublime or Notepad), how do I get that website to other people? If I wanted to make a website eventually with my online portfolio of videos and images, how would I get it out to people?
Uploading website files are one of the very first steps users have to take in order to publish their creation on the Internet. This tutorial will provide a generalized example on how to upload a website using one of three basic tools:
What you’ll need?
Before you begin this guide you’ll need the following:
Access to the control panel of your hosting account
Your website’s files (preferably compressed in a .zip or .tar.gz
format archive)
(Optional) An FTP client and FTP login details of your hosting
account
Option 1 – Upload Your Website via Hosting's File Manager
Navigate to your control panel’s Files category and open File
Manager
After that, go to the public_html directory, which is the root
directory of your domain (for example http://www.domainname.com/).
Your files should be uploaded there. The directory may also be changed depending on what URL you want it to be accessed from. In case
you want the content to show up on
http://www.domainname.com/something/ your content would need to be
located in public_html/something directory.
To start uploading, right-click with your mouse and select Upload
Files option.
To unzip your archive, right-click it and press Extract.
Once the content is located in your desired location, you will be able to access it using any browser.
Option 2 – Uploading Your Website via FTP
Some users prefer using an FTP client, such as FileZilla, SmartFTP, CoreFTP, or any other in order to upload their website. In this example, we will use Filezilla.
Firstly, you will need to get your FTP details.they
are located in your control panel’s FTP Access section. If you are not sure what your FTP password is, you can easily reset it by pressing Change account password section.
Open FileZilla and input your FTP connection details into the fields
at the top of the program, then click Quickconnect.
Once you are connected to the FTP server, use the file browser on
the LEFT side of the program to find your website’s files on your computer. After you have found your website’s files, use the file the browser on the RIGHT side to open your public_html directory on the hosting server. Once you have done this, you can simply drag-and-drop files from left to right and they will be uploaded to the server.(OPTIONAL) Similarly, you can upload a compressed archive via FTP by dragging-and-dropping from left to right. You will also need to extract it via File Manager. Refer to the “Option 1 — Uploading your website via File Manager” part of the tutorial above for instructions on how to extract archives via File Manager.
Option 3 – Uploading Your Website via cPanel’s File Manager
Click on the File Manager icon, located under the Files category.
Once inside the File Manager, open the public_html directory.
Click Upload after entering the public_html directory.
You can click “Select File” to select a singular file, or simply
drag-and-drop your file to the outlined area.
Once the upload is complete, return to the File Manager and you will
see the uploaded archive in your public_html directory. Right, click
the archive and select Extract to extract the archive.
If you receive a prompt asking to specify the location the archive
should be extracted to, make sure to specify /public_html.
The archive is now extracted, all files should now be located inside
public_html. Navigate back to public_html and see if the files were moved successfully.
Your website should now be fully uploaded and accessible via your
website’s URL. All that remains is to access your website and check if everything works correctly. Simply type in your domain name in
your browser, such as http://www.domainname.com/, and check if your
website works to your satisfaction
you have just learned how to upload a website. As you may see, you can upload a lot of files at once via an FTP program more easily, however, each file will be uploaded one-by-one. As a result, it may take a long time for each file to be uploaded separately, so it is still strongly advised to create a compressed archive of your files before uploading them.
On the other hand, the File manager is useful for uploading one or two files quickly, since you do not need a separate program for the File manager to work and can update your website on-the-fly, while working on other tasks inside your hosting control panel.
Related
I want a user to be able to download a file after entering their credentials on the webpage.
Currently I'm able to allow them download the file only if their browser has access to the hosting servers file systems. I saw this How to trigger a file download when clicking an HTML button or JavaScript.
This is what I'm doing currently:
Download
Excuse my naivety. My question is this: how do I change the path to file in:
Download
such that the user can directly download to their local machine when they don't have access to the hosting servers.
I want to make a local file editor. To open some files edit them and save them back. It's ok if it only works in Chrome. Using
<input type="file" id="filepicker" name="fileList" webkitdirectory multiple />
I can read all the files and draw the file tree but I want to also be able to edit and save to these files. Even create new files and folders.
Is there any way to do it. I'm also ok with hacks that use Java or Flash or simply any other hack if HTML5 does not offer any solution.
Thanks
I do not believe what you are suggesting is possible; however, there is a different approach that should solve your problem.
If you take Microsoft's Online Word for example... They have it setup so you save document to the cloud and then can edit them with an online copy of Microsoft Word.
In otherwords, the user would upload a file. Your server would then take the file, display it and allow the user to edit the file. The user would then save the changes to the file. You can then provide an option to re-download the file.
To more closely emulate editing a file on the local file system, you can also setup a "temporarily" save on the server.
Essentially, the user uploads a file. The server would allow the user to view and edit the file. When the user wishes to save it, instead of saving the file on the server, give it back as a download to the user.
After the user leaves your site you can delete the copy of the file that is saved on your server.
I'm going to create a web app that's going to run locally on the user's computer.
First off, the user has downloaded a JSON file that ended up on "my download files" locally on their computer.
So they are going to browse to e.g myportal.local and there they are going to select the downloaded JSON file and also they need to choose a local location (directory).
To simply the workflow
Go to myportal.local in the browser
Choose in the form the JSON file
Choose a local path on the machine
Press submit and other scripts will parse and download things to the chosen folder.
Steps 1,2 and 4 is not a problem, it’s step 3 on how to choose a local destination.
It isn't possible to do this directly in the browser.
Since the HTTP server is running on the same computer, you could use server side code to examine the structure of the computer's file system and generate a user interface in HTML for the user to pick directories with.
I am planning to create an app using html5 file api and javascript to take directory path as input and be able to process (search for a text) all files in that directory and sub directories.
currently I am doing it using batchscript, What are constraints/obstacles doing it using HTML/javascript.
In short: You can't to that automatically.
Access the local filesystem from any browser is blocked for security reasons. Reason: Imagine any website being able to access the files on your filesystem.
Read this: Local file access with javascript
Maybe you want to rephrase your question and say what you actually want to acheive.
You can access simple file information using the user's input and using <input type=file>. But the user would require to do the following steps:
Click the "Browse button" (a file dialogue appears).
Navigate to the requested folder.
Select 1 or many files.
Click "Open".
Mozilla has documented this well with an example: https://developer.mozilla.org/en/docs/Using_files_from_web_applications#Example_Showing_file(s)_size
I have a web page containing a list of pictures urls (can be more then 1000 items) and I want to enable a button for the user to click and download all of the files to the local hard drive.
The download process should ask the user for a directory to save the files in and then go ahead and download all files to that directory (if possible, creating sub directories inside). This should be done with a single user confirmation for the whole download process and avoid display the browser save dialog for each file.
Is there a way doing that? I am aware I can't use the standard HTTP protocol for the downloads and have to write some kind of control to do the job. The page is written in asp.net.
Downloading to the server, packing and sending to the user is not possible. The download has to be originated from the client machine.
You should update your question to include the requirements from your comment, because they make a huge difference. If the server cannot retrieve the files, because he doesn't have the right permissions, your only option is to run the code on the client side. There are several options how to do this, mostly depending on the clients and your coding skill:
Flash (Not sure about the security aspect of writing to the local file system, though)
Java Webstart (Disadvantage: Clients need to have the Java runtime installed)
Browser plugin/extension (Disadvantage: You can only support a subset of browsers and the page will not be immediately usable, as the plugin or extension needs to be installed first)
In all cases, you will have to write a tool, that retrieves the URL list from your server and starts downloading it.