followed the tutorial to develop a personal blog website. actually, just getting the website built up is not that difficult as every part and function of the website corresponds to their code, html, css or js. as long as we are clear about what we want and how they should be displayed, the next is just to find the corresponding items and function to create and build them up. if it’s just for learning and test, then it’s done. we can check and test from the computer locally, or any other computer of the same network range by typing the ip address. but when it comes to the public, or just different devices, like mobile phone and tablet, then we need to consider the final display on each kind of devices, and add/change the code so that it can be display “normally” when we visit our website from whichever kind of devices we have.
the next is about setting it up on the host server and make it public as our final purpose would be getting the website available to anyone else, or maybe just to ourselves when we are not in the internal network. there are two of the most important tasks that we need to get done before that:
first, accessible. that means, we need to make sure the host server is responsible and available to the internet. and maybe next we need to consider getting a domain and put our website under that domain, though access via ip is also working if we have a static ip. that will involve registering a domain and bind the domain to the ip of the server, or via some ddns settings so that when people type our domain, they can always be directed to our host server.
second, security. that includes security to the website itself and security to the host server. generally, https is mot secure that http, so we might considering getting our website a certificate and redirect all http traffic to https. and we might also want to limit the access to our host server.
most of both of these two tasks are related to the back-end. see, it’s not that easy if we want to build the websites ourselves. of course, we can reply on the third-party vendors and pay them money to get everything ready by them and we just worry about the code of our website, or even don’t need to either and just ask them to develop for what we want. that means, pay for all we want and we don’t need to get our hands dirty. well, it’s a good choice when it comes to business and they don’t have many people available or the deadline is short, but to us, the so called technical personnel, we might want to dig more and do some of the work for whomever that wants something out of technology, the above business people maybe. we might not need to do all of these as sometimes working with others and sharing the benefits is a smarter choice from the business perspective. that’s another say when it comes to real business. but when it comes to practice, just try to dig as deep as we can.