(Answered) Uploading your Axure prototype to a domain (www.example.com)


#1

I would like to put the prototype in that domain root so when the customer goes to wwwDOTexampleDOTcom I want the prototype to come upp without the sitemap.

Sounds like a plan. Here are the basic steps for uploading your Axure prototype to a domain.

Buying the domain

This is a one time purchase, usually you buy the domain for a month. If you get a domain at a reasonable price, it’s usually under $20 for the year. Make sure you get domain privacy, otherwise you will get calls from solicitors. Popular places to get domains include Godaddy, Fat Cow, Bluehost, and Netfirms.

When you buy just the domain, it just exists as blank, or with ads that you get money from if people click the ads (called a “parked” domain).

Getting a host

Hosting is a monthly service (they want you for the year obviously), where you pay for access to upload files to one or multiple domains. You often get the host and domain at once - sometimes the domain is free when you sign up for the host.

Setting up FTP

It’s easy to set up FTP access from your host, just find the link from the host’s control panel and it’s easy to set up. You will receive an ftp domain like ftp.example.com and then a user name and password. You then download an FTP software like Cyberduck or Filezilla. Sometimes the host will have a built in FTP client, but we recommend using Cyberduck.

Log into the FTP

Log into the FTP via Cyberduck. This root folder is essentially www (dot) example (dot) com and any files you place now will be www (dot) example (dot) com / filename.ext .

Upload the generated prototype

At this point you are in your FTP client (Cyberduck), looking at your root folder. Now, in Cyberduck, right-click and select ‘Upload…’ Navigate to the generated prototype folder, which is almost always in Documents/Axure/Prototypes/ProjectName. If you can’t find this folder, open up the RP file of your project and select Generate > Prototype. That first text field contains the file path to where the generated prototype exists. In the Upload dialog, navigate till you are in the ProjectName folder. Select all of the contents (folders, files, everything), and then click Upload.

Specify which file is the default when you browse to the root domain

Now, at this point you should be able to go to www (dot) example (dot) com and your prototype will display. If you see the sitemap, and this isn’t what you want, then you will have to specify the default file which will be viewed when you reach the domain. To do this you will have to create a text document (anyname.txt) which contains this text…

DirectoryIndex Home.html index.html index.php

(This assumes your homepage is called Home, it might be something different. If it is then replace Home.html with yourrootpagename.html). Upload that text file to your root, and then rename the text file to .htaccess - not anyname.htaccess but just plain .htaccess.

OK! You should be there. Navigate in your browser to www (dot) example (dot) com and your prototype should be there. I would recommend giving it a few minutes as sometimes there is a delay between uploading and everything settling correctly. Sometimes when you navigate to the domain, everything will be jumbled. Don’t worry, check back in a few minutes, or even in an hour and it should straighten itself out.


Custom Domain - Access for Clients
#2

This works brilliantly with my home page. Thank you. Although, now all of my other pages do not work. I get an error message reading

[b]Forbidden

You don’t have permission to access /.html on this server.[/b]

Do you have any reason why this happened? What should I do next?

Thank you Paul!


#3

Hi kpolsie - Sorry I don’t have a better answer here. I would contact your web host/server as it’s likely a server permissions/apache type of issue (something I know barely anything about). :frowning:

Here is a thread on a godaddy forum of someone with a similar issue. http://support.godaddy.com/groups/web-hosting/forum/topic/403-forbidden-you-dont-have-permission-to-access-on-this-server/ If you get on a live-chat with the hosting company they’re usually pretty good about helping you fix these kind of issues.


#4

thank you very much.


#5

any one can plz provide video on how to get the work done to hide sitemap.


#6

Hello, I had some problems hiding the sitemap too. When creating the .htaccess try to use only LOWER case names.

Example:

Instead of DirectoryIndex Home.html index.html index.php
use
DirectoryIndex home.html index.html index.php

that solved my problem.


#7

I think I have done everything listed above, but the site map is still showing up.

I created the .htaccess with content of: DirectoryIndex home.html index.html index.php
I located the .htaccess file in the same location as the home.html and index.html files are located

www.domain-name\index.html displays the sitemap
www.domain-name\ displays the sitemap
www.domain-name\home.html DOES NOT display the sitemap

Can anyone see what I am doing wrong? Thanks!


#8

We helped LogCastle out via the email support channel, and it turned out that something was preventing his .htaccess file from working properly.

He was able to use a simpler trick to get rid of the sitemap–changing his main page’s name to “index”. When you generate HTML files, the sitemap is included in “index.html”, which is typically the default page a domain will point to unless otherwise specified. Since specifying a different start page through the .htaccess file wasn’t working, the rename did the trick by matching his main page to the standard default page.

If anyone else chooses to use this method of renaming their main page to “index”, make sure to have “Without sitemap” selected in your Generate HTML dialog. This will overwrite Axure’s default “index.html” file so that it no longer includes the sitemap.


closed #9

unlisted #10