No announcement yet.

Tutorial Ideas

  • Filter
  • Time
  • Show
Clear All
new posts

  • Tutorial Ideas

    Hey All,

    Seeing as how I'm hearing rumors about a specific 'Server' forum, and how this forum has a sufficient lack of tutorials...I figure I'll take a stab at remedying that for you all.

    I have over 4 years experience in web hosting, and I'm quite knowledgeable about various hosting topics, so what I want to know is...what do you want to read about?What sort of tutorials would you all find useful?So far I've ( ) only posted one tutorial, fairly random topic-wise, but it should give a fair sample of one of my writing styles for hosting tutorials.

    If you have any suggestions, feel free to post them here or pm me. I'm hoping to have the cooperation of the moderators in that, if you find the tutorials useful, they might hope to be stickied or otherwise archived in an easily accessible form.
    "It's the bucket o' nothing, for only 99,99,99!"

  • #2
    I'm not sure about stickied, but I can definitely link to them from the newsletter.

    Cat-herder Extraordinaire


    • #3

      Er...I mean....

      Thanks for your cooperation, Pegasus.

      "It's the bucket o' nothing, for only 99,99,99!"


      • #4
        Well, I may be able to help with some tutorials too, but not for a little while. I'm pretty booked at the moment. Here are some of the things that I think there should be tutorials on:
        • Setting up DNS
        • Setting up Mail (SMTP & POP/IMAP)
        • Setting up FTP (chrooted to a specific dir, etc)
        • Setting up regular backups (I know there was already a crontab tutorial, but possibly touch on compression of the data, what data needs to be backed up, and then ftp/rsync)
        • File/Directory Permissions
        • Installing software from source (This could be hard due to different distros. Maybe give the basics for debian and RHEL? They seem to have a large market share...especially RHEL, and it's clones - CentOS, Fedora, etc. Maybe even touch on making Custom RPMs)
        I'm sure there are plenty more that I will think of later, but these are some of the basics. Also, I WOULD like to see the tutorials stickied. It's easier to find good clean answers that way.


        • #5

          Now I know why you have Tux in your use Linux, don't you?

          Permissions(CHMODing) would be a fairly simple explaination, perhaps I'll write that up in a bit. I atchually had several RHEL tutorials written..but I sort of..ahem...lost them. I think my priorities at this time will be specific operations...or installing specific when I do reference sheets(eg: how tos on cron, configure, make, compression on linux..etc..) I like to be as thorough as you hopefully see from my cron tutorial. I should likely cover configuring apache via the command line...installing apache know...things like that.

          You've sorta got a one-up on me on some of these things, Aaron...I have yet to be able to switch over to Linux on my home comp(planned for this summer) so everything I do is via a ssh connection to the server.
          "It's the bucket o' nothing, for only 99,99,99!"


          • #6
            Linux? What's that?

            Seriously though, at work, I have 4 computers at my desk. 2 Linux (Fedora and CentOS), 1 XP, and one Mac. I ONLY use the mac and windows computers for testing web-pages. I use the Fedora Computer for EVERYTHING else, and the CentOS one is my test server (set up just like my dedicated servers, so I can test changes in the same environment they will be implemented in).

            SSH is a perfectly viable option for linux administration, such, I would like to add something to my list
            • Setting up and using SSH


            • #7
              Heh..Yes...SSH is quite good...not to mension nessary if the only linux comp you have access to is a Barton CentOs Dedicated server located in SAVVIS. CentOs btw, I find is very good....I prefer it over RHEL..which I'm used to using. I'd really like to install CentOs as my desktop OS...and I do intend to..but I recon I'll wait until I get my second comp..or at least my new I can dual boot with XP for the windows dependent people in my house. But..nobody in my house uses iť..which makes me proud.

              One reason I tend to be less prolific writing tutorials is indeed, that I don't have a test server. Everything I do..I do because I'm confident I won't slip up on it. Although it is rather impossible to be entirely confident the first time you do something...I've spent the last 3 years or so doing server administration..and I consider myself comfortable with pretty much anything I'd need to do. However..if I had a test server..I'd have no problem whatsoever with churning out tutorials on everything I could possibly write a tutorial on. When I can...I will be setting up a local CentOs test server as well. I have yet to run into anything I haven't been able to read the instructions for...and go "mmk...piece of cake".
              "It's the bucket o' nothing, for only 99,99,99!"


              • #8
                Starting at the begining you need to get your pages to the server.You need to know how to use a ftp client.An easy one to use is gftp but there are others.A tutorial on that would be good.Next alot have problems setting up mysql.A tutorial on phpmyadmin would be good.


                • #9
                  Well, I'd say that starting at the need to know how to set up the server, before you get any files on it. Even so, an FTP tutorial WOULD be good, I'd prefer to see one on gFTP (gui FTP), and lftp (a command line FTP, with the ability to transfer files using: ftp, ftps, http, https, hftp, fish, sftp and file). The advantage of showing how to use the CLI is 2 fold. First, it shows a user how to use FTP FROM their server via SSH. Second, it can be easily implemented into cron jobs for remote backups (that or rsync).


                  • #10
                    Good Points...and I agree...CLIFTP and CLI in general is useful. If you can't use a really should be leaving the admin work to someone who can. Personally..I prefer a CLI...and have taken to doing the majority of my web development while in shell on my server

                    I'll see what I can do.
                    "It's the bucket o' nothing, for only 99,99,99!"


                    • #11
                      I guess you guys won't be including a dictioniary for all those fancy letters, eh? So that people who know squat about servers (aren't those the gals who take my order in Smitty's?) will know the right questions to ask? I mean, sorta like idiot-proofing some of the explanations?



                      • #12
                        Hi Lighthouse:

                        Defining a few terms does seem like a good idea for tutorials which may use unfamiliar ones, but since Aaron and I seem to have gotten into a discussion using are a few (rather simplified) definitions for those who may not know the meanings:

                        CLI - Command Line Interface. Simply put, it's a command line (eg: ms dos-like), text-based way of executing commands on a local or remote computer. If you have read my cron tutorial, you will notice certain things inside of code tags, such as:

                        command .....................
                        the code tags imply a line which you would type into the command line and execute (execution is usually done using the enter key [carriage return]).

                        GUI - Graphical User Interface. A visual interface designed to make usage of a computer easier for someone uncomfortable/unfamiliar with a CLI (see above), or to facilitate certain visual tasks which would be better achieved via a visual interface to the system at hand.

                        As you might tell by the names, a Command Line Interface is exactly that...a command line, whereas a Graphical User Interface may use a "skin" or other graphical component (usually these will be called 'desktop environments'), examples of such environments are: KDE (the K Desktop Environment), MacOs, and Windows (the later two when booted 'normally'). When referring to MacOs and Windows, I am referring to their visual interface components.
                        "It's the bucket o' nothing, for only 99,99,99!"


                        • #13
                          Originally posted by AaronCampbell
                          ...ftp, ftps, http, https, hftp, fish, sftp...CLI...SSH...rsync
                          ftp: File Transfer Protocol is a standard method for sending files from one computer to another on networks such as the Internet.

                          ftps: FTP SSL: File Transfer Protocol (FTP) with the added option of SSL security.

                          SSL: Secure Socket Layer is a security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. SSL was developed by Netscape Communications Corporation and RSA Data Security, Inc.

                          http: Hypertext Transfer Protocol: HTTP is the primary protocol on which the World Wide Web operates.

                          https: HTTP over SSL

                          hftp: ftp-over-http-proxy protocol

                          fish: Transfer protocol that uses ssh with no special program on server side.

                          sftp: Secure file transfer program similar to ftp, but performs all operations over an encrypted ssh transport, thus gaining the features of public key encryption and compression. (basically the same as ftps)

                          CLI: See above

                          SSH: Secure SHell is a program to log into another computer over a network, to execute commands in a remote machine, and to move files from one machine to another. It provides strong authentication and secure communications over insecure channels.

                          rsync: Remote SYNC is a computer program which synchronises files and directories from one location to another while minimizing data transfer. Two important features of rsync not found in most similar programs/protocols is that the mirroring takes place with only one transmission in each direction, and ONLY the data that is different is transfered (thus saving time and bandwidth).


                          • #14
                            Good addendum Aaron...being half asleep while defining terms doesn't leave much room for seeing what atchually needs defining
                            "It's the bucket o' nothing, for only 99,99,99!"


                            • #15
                              *blink* I think I'm sorry I asked. Okay, so maybe getting idiot-proofed isn't such a bright idea. It's not for dimbulbs, is it? Can you make a stickie thread that gives raw beginners an idea of what they need to know before they try hooking up (or whatever it is you do with) their own servers? Just so the light at the end of the tunnel doesn't feel like an on-coming train.