Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 11 months ago.
Improve this question
I have learned HTML CSS js but the problem is that when I code, I code over an HTML document and i can't find my website on google BCS it's an HTML document, therefore, I want help from you to make my own website link like https::/loremimpsum.com (.org .tb, etc.) problem
The "website link" is called a domain and you cannot make one. You can search for your desired domain address on many hosting sites and see if it's taken or not. If it's available, you will need to pay for it to be registered. Domains have to be renewed annually in most cases.
Before you can do anything with your domain though, you need to have a server running which hosts your web services (such as a webiste). Typically, this means a separate device (physical or virtual) which has a static public IP address. For experimenting purposes, you can set this up on your personal computer, but this is not advised for long-term hosting for multiple reasons.
There are many types of web server softwares and the right choice comes down to your personal project and needs. Most well known solutions are: Apache, IIS, Node.js...
When you have a server, you must configure your DNS settings (this happens on the website of your domain host) to point at the server's IP address. After this gets registered, your server can be reached over the internet, through your domain address.
Hosting a simple website can be as simple as dragging your site files (your .html, .css, .js files along with necessary assets) to a specific folder on the server - default generated might be: <path>/www/ or <path>/public_html/. When developing simple .html, .css, .js files, there is absolutely no conversion or compilation process. The website is directly displayed from them.
If you use something like Angular however, then you'll want to build your project and move the generated package instead (which is just a collection of the previously mentioned files).
Web browsers try to access port 80 (for HTTP) or 443 (for HTTPS) to display your website. You want your website service to listen to these ports, but this might be already part of your default config files for the web server software. You might need to do additional firewall configuration to allow traffic to reach your services.
You can rent a web server which is ready to host your content for you. Of course this involves a monthly fee if you want to have anything that's useful.
Websites are not converted or complied.
The html document is on your computer but a website is seen and stored on a server.
so the html file will be present in the server.
Now you can get a server but it will not be hosted meaning no other computer would be connected to it.
Also server and website hosting costs much but there are some free website hosters like 000webhost.com
You can literally get your own url.
Related
I'm new to coding, quite obviously. I created a web design using HTML in Adobe brackets. How do I create my own website from here? Like getting a domain or host. Not sure if those are even the right words to use
Welcome to the wonderful world of web development! Congrats on making your first HTML site.
I am not sure how much you know about the topic, so I will try to explain the basics of getting a site "online".
Websites essentially allow you to access other people's HTML documents in a file directory. You have probably noticed some URLs in the form "www.example.com/file.html". This means that to get your site online, you will need a computer to "host" your HTML files from. Since you probably don't want to leave your computer on 24/7, you will need to use a web hosting service. There are loads of web hosting companies that offer similar services, but they all have the same goal essentially - providing the means for people to remotely access your files. My hosting service of choice is Digital Ocean because they offer a decent price on a small web server. Through your web server (which is essentially a computer running Linux in a warehouse somewhere), you can install web server software (like Apache) which will allow you place your html files into a special directory which will can be accessed from a web browser (something like /var/www/html). Once your files are uploaded to your server, you can access your website through your server's IP address (some esoteric number in the form of http://xxx.xxx.xxx.xxx).
Of course, you don't access websites through an IP address (at least most humans don't). This is where a "domain name" comes in. The web provides a nifty feature (DNS) which allows you to map a domain name to an IP address. So you can go to your favorite domain purchasing website (something like GoDaddy, which you have probably heard of) and purchase an open domain name of choice. Once you purchase the domain (something like DragonFire09.com), you can map this domain name to your web server's IP address.
These are the two main steps to getting a site online! I hope this provides some insight. Note that getting a website online costs money because you need to pay for a hosting service and a domain, however its a great experience because along the way you will get your hands dirty with Linux and other parts of the web stack.
Of course, you can always create files locally and test them through your own web browser free of charge.
Good luck!
I have a different set of applications, each having their own war files and they could be deployed in different servers.
Assuming that all application sets may need to interact with each other I am trying to develop them as web services. It may happen that an application 'A' installed on server 'X' needs to launch an application 'B' but B's resources like HTML and js are not present on the server where A is installed.
How can we do this? I have come across a few sites where Viewable is used but then it needs the JSPs to be in the same instance. What if I want to achieve this when the calling application doesn't have HTMLs or JSPs with it.
I hope I have been able to put up my question properly. Thanks for any inputs.
As Pesskillet says, you can use a redirection to resource of server B.
If that resource is an HTML view, you don't need to worry about the loading of static files (CSS, JS, Images etc.) that are bound to the HTML view. Because the browser of the user will load it automatically as soon as it will get the HTML document.
I'm building a website, however the URL for the website is likely to change.
How can I load resources in the front end if the domain and installation directory is likely to change?
Now that I'm starting to get deep into building the backend I have some issues.
The url is about to change, what do I do now?
I can use PHP to get the current domain and have a preset installation directory. Then load it from a variable every time I need to load a resource.
Is there any other solutions, what would you recommend?
I'm talking about resources loaded through the browser, not ones loaded through php.
If the resources are housed under the same domain as your php app, you can simply remove the protocol and hostname from those links and let the browser figure it out.
If the resources are hosted on a different hostname (or via a different protocol - http vs. https for example) then your solution of using a variable is probably the best course.
Presently, we host our java/j2ee web application with a third party hosting company.
Application URL is like abc-xyz.com
This primary domain abc-xyz.com is going to expire in couple of months. Client doesn't want to use this domain anymore and wants to register completely a new domain. In order to accomodate primary domain change, what needs to be done? Thank you.
This is a very broad subject.
If your client is willing to pay for the service why not just let the hosting company move the contents to the new domain. As far as what to do with the web application it really depends on where and how paths have been declared.
Some developers use static paths. I have seen some sites store the domain name in a text file and reference it through out the site, so a path would look like this where
x='new domain name'
<img src="x/images/yourpic.png">
However using static paths can be very frustrating. It is better to use relative paths in respect to the root of the domain. So the above would look like this instead:
<img src="../images/yourpic.png">
Another thing to consider are the paths to the datasources. If you are running something like cold fusion the datasource is set in the cold fusion administrator so moving a site can be as simple as moving the tables and pages then ensuring that the datasources are set correctly. In php developers typically will set a connect function for all database connections in one file.
This may or may not answer your question but the bottom line is that it really depends on how the site is structured and what type of platform is being used.
This question already has an answer here:
Closed 12 years ago.
Possible Duplicate:
What’s the point in having “www” in a URL?
Hello, I have little to no experience owning a website but I am willing to learn all that there is to this process. However I am frustrated because I am constantly blocked by simple problems.
I just uploaded my first index.html page which is basically a background color and a title image. I put my favicon in the public_html directory right next to index.html. I immediately notice that it does not work. I also notice that I have typed http://website.com in the URL bar. I type "www" before "website" and the favicon shows up. I hit back and the favicon is blank again. What is the difference between the non-www version of the site and the www version of the site? Why does the favicon not show up? What other differences are there? Should I disable the non-www site like many professional sites seem to do? How do I do this? What are the advantages and disadvantages, if any?
Thank you.
The www-subdomain is just a convention amongst websites to indicate this address points to a World Wide Web server.
For example,
google.com is the top domainname of
the Google company.
www.google.com indicates this is the
domain name for the World Wide Web,
ftp.google.com indicates this is
probably an ftp-server.
But as it is just a convention, and the average user uses the internet mainly for www, most servers configure their http://domain.com to be aliases to http://www.domain.com.
Why the favicon on your site only shows up for the www-version and not for the topdomain, depends on your html and your server configuration. Can you post some code or link to your site?
The fully qualified domain names are different. So they are different websites.
Usually the two hostnames will point at the same IP address, and the server will be confiured to either serve up the same content for both or redirect from one to the other.
Redirecting from on to the other (and which way round you do it doesn't really matter) is generally considered good practice as it lets you be consistent (and saves you from issues such as XHR requests to a specific hostname breaking when used on the alternative).
The favicon not working is likely caused by your browser having cached that http://www.example.com/favicon.ico didn't exist and it not having yet checked again. http://example.com/favicon.ico, OTOH, is a different URI so it would have checked it the first time you went there (which was after you created the icon file).
Typically most of the server domain manager software like Cpanel and Plex are configured to serve same site for both domains. Cpanel do have a public_html and www separately, but same content.