Great! So you have registered your domain, and signed up for hosting with a company. Now what? Well before we go any further, we should cover the details/options you have with these services. We will pretend you just signed up for hosting through Blue City Hosts, through this is not important as one usually fits all. — So here it goes:

Now that you have space on your Hosting Provider’s server, you have several ways to communicate with their server; each communication method is used to accomplish unique tasks. Here they are:

1) FTP - used for sending your webpages to their server
2) Website - used for setting various hosting options

FTP: The only purpose FTP has is to transfer files. “File Transfer Protocol”. This is used to send pictures and html/php webpage files to your web host. They will give you a username and password, and an address to connect to. You really should get a good FTP client vs. using Internet Explorers default. I recommend getting FireFTP extension for Mozilla Firefox or WS_FTP as a standalone. Once logged in, you can upload your entire site as well as see what is actually on your website. In the website section (in the next paragraph) you can manage the FTP username and accounts. You could for example give a friend access to only a particular sub-directory on your website for him to work on without comprimising your entire website. ex. http://webpuffs.com/randomuserfolder/. You will have to play with FTP, there are a lot of features.

Website: These are always unique, depending on the hosting provider, and many offer a lot of options. To access this area, they will give you a webaddress to type into your browser (eg. www.webpuffs.com/administration). There are options, usually, for passwording directories, managing FTP accounts, managing e-mail accounts, and many other administration settings. Blue City Hosts even offer Fantastico which manages default installations of forum software, shopping cart software, managing databases, and more.

Coming Up Next: Database websites: Getting Started.

I just installed Suse 10.1 for my desktop.

Pro’s: I can accomplish so much on the networking side. Most of the installation worked; found all my drivers; and even my printer; a slew of applications were installed by default to take care of my multimedia, websurfing, etc. I like the GUI.

Cons: I am missing Dreamweaver, Google Chat, TrueCrypt, AVG (I’m sure I could find an alterative for this), Picasa, iTunes… well the list goes on. I get only 24bit color with correct video driver installed. Online Updater was not finding their server even though internet was working fine. Slower in general. I don’t like the GUI (more dislike than like).

The Pro’s are something I can get by without… a few of the Cons are irreplaceable. I cannot use linux for my desktop, only servers. It was fun though, I always like to see what progress they have made in the desktop world.

I cannot believe how many developers are still developing OS specific applications instead of web-based apps.

Certain applications need to be developed to to run on the machine — games, word processors, etc. However, there are many applications out there, that could be developed just as effectively in a web-based solution vs. an actual OS application. A Benefit to web-based applications: Can be run remotely on any OS. I have seen numerous custom small business applications which have been developed to run only on Windoze machines, the data cannot be viewed remotely, and modifying the application is almost impossible due to them being compiled onto the machine. Web based applications with all the scripting done on the server-side are the most portable and dynamic.

If you are considering getting a program made for your small business to keep track of customers/sales/etc. Web-based applications is most likely the best solution for you.

After the last post I made, a lot of people were pry wondering… why not just use this package for your website? What a watse of time. There are many downsides to having a one-man development team. Time/Knowledge/Money are all limiting factors to the success of an application. The more developers, the more money, the quicker better (if managed properly) products get made. Windows Vista is a prime example of this. I believe Windows Vista will be worth the wait despite the many tragedy’s it currently has. Is hand coding all my websites the most efficient? No. Have I caved by putting a forum on Jpauls.net? Not really. When to make and when to take…

Does my code function exactly how I want? Yes. I love saying… wow I wish I had this… and actually having the ability to think up a solution to build into my entire site in minutes. If this was a package, I would be sorting through thousands of lines of obfuscated code only to be stumped when trying to impliment it. This is the main benefit of writing my own code.

Do bugs popup? Absolutely. This is a major frustration/downside to developing code yourself. You instantly volunteer your website for becoming a giant beta project. Withe me developing as fast as I am… its more like an alpha project. So why do I have a bias against taking code?
Big organizations/businesses with their drag and drop, one fits all templates make me sick. These projects stifle innovation, and if we are not careful will bring about the end of multiple custom web interfaces. I am picturing Windows XP for websites… The market will naturally chooses the best web applications and support them; which in and of itself is good. However, a long-term view is necessary to realize the reprocutions of this behavior; or is it (windows xp). Bill gates took window groupings in the taskbar from linux, just like he took NetBSD’s networking stack for windows 2000. The side projects contribute greatly to the mother-market, and should get more funding than they currently do. Sure picking the best solution today is a simple choice, but where we sit today, are we ready to make that choice now? Personally, I would like to wait as long as possible to choose.

At this point, most people reading are thinking “GOOGLE.” You are forgetting Google Master Jpauls… This is why I do not like Google: I worry about the millions of users giving Google access to their lives. Who can you trust with your data? The government? LOL. Losing thousands of records of veterans, Chinese launching cyber attacks to steal data. Google is becoming an empire, and I am a firm believer in divided power for long term reigns of power to provide a level of security for when Google goes bankrupt. Hey, they did just waste 1.65 billion on YouTube. This is why I like Google: For as long as they have been in business, they have been raising the bar for online services, stimulating innovation. When they aren’t busy developing their own technologies, they are buying and investing into more small companies and allowing them to continue to develop. They seem to grasp the overall effect of their actions, I sure wish they have a failsafe for when the Government starts knocking on their door. It’s not a matter of when, they are already doing it, its a matter of when the government crosses the line. With great power becomes great responsibility; responsiblity sometimes outside the grasp of even the most thoughtout, organized, and wealthy companies.

So next time you are choosing to make or take, ask yourself, do I want accept what they are giving me, or encourage the market to develop something better. Just make it.

In the web design world, there is a huge difference between how you picture something working and how it actually ends up working. Shortcuts often get taken to get the task done which ends up leading to confusing code; or confusing code can lead to shortcuts being taken, which only makes the problem worse. This ends up with a user interface (UI) that was not planned, and an unmanagable website for someone else to manage who is unfamiliar with the code. Problems start to show up accross the board due to the unorganized coding

What can a PHP developer due to prevent this problem? Is there a ‘one fits all’ structure? Probably not. Overtime I notice my PHP code evolving into similar structures on multiple websites. Most of my websites have multiple ‘class’ files with all my useful functions for that particular section. For example, if I have a booklisting system, I would have a folder named ‘booklisting’ with files named booklisting.php, booksearch.php, mybooks.php. These files contain only page flow for their respective functions. So where does all the actual code happen? Inside of my ‘booklisting’ folder there is a subfolder named ‘class.’ Withing this folder are files named booklisting_class.php, booksearch_class.php, and mybooks_class.php. These files contain all the functions I need for each of my flow control pages. There is also a config.php file inside the class file; this file is used for any functions that will be used across all booklisting pages. If there is a function I want to use across my entire site, I have a functions.php file in my main directory in a folder named ‘includes.’ With this hierarchy of functions, I can precide which file contains the function I am looking for; along with comments and formatting I can find it with ease. This code layout also forms a layer of flexibility to your site, I can place a booksearch box on any page I want simply by including my ‘booklisting/class/config.php’ file and calling the function responsible for showing the search box. This coding format, also adds a layer of continuity to all pages on your website, by using the same code, the search box will look exact on all pages. This also allows for you, the coder, to justify spending more time working on it knowing it will be used time and time again.

This is my method. Find a method that works for you, and run with it. It is bound to change over time regardless; happy rewriting.

PHP guru, Jpauls/Jeff Schollaart