While a user’s home directory on src code is normally available to only that user, src code gives you the option to share some content publicly via personal webpages. Each user’s homepage, if it exists, is visible at https://src-code.simons-rock.edu/~<username> to the internet at large. It is also possible for a user to restrict access to only those with Simon’s Rock credentials.

As with all use of src code, keep in mind the Terms of Service when building your webpages, and please be mindful of what content you choose to share publicly.

Setting Up a Basic Homepage

Setting up a basic webpage can be accomplished in two steps:

  1. Create a folder named public_html on your computer. Place HTML pages, CSS stylsheets, and any other goodies inside public_html. At the very least ensure that public_html contains a file named index.html at the top-level (not inside any subdirectories). Here’s a very simple index.html you can download to get you started. It is recommended that you test your content locally before transferring it over to src code. Simple webpages can be tested by loading the index.html directly in your browser (opening it from the command line, double-clicking it, or click-dragging it onto your browser window).

  2. Copy your public_html folder to your home directory in src code via SSH. There are two main ways to do this:

    • From the command line (GNU/Linux if OpenSSH is installed, OS X):

      Navigate to the directory containing public_html. Enter the command scp -r public_html <username>@src-code.simons-rock.edu:/home/<username> into your terminal, where ‘username’ is your Simon’s Rock username (i.e., what you would log into your Simon’s Rock email with). You should be provided with a message from src code in your terminal and prompted for a password; enter your Simon’s Rock password at this time. Once entered, one or several progress bars should appear and detail the progress of your transfer. As long as there are no error messages, you should be good.

    • With a graphical user interface (GNU/Linux, OS X, Windows):

      Install a FTP client such as FileZilla. We describe how to use FileZilla here for convenience, as it is available on a number of platforms. There are many other FTP clients that you are welcome to investigate, some of which operate quite similarly. The images below are screenshots of FileZilla v3.18.0 as running on Windows 7.

      • When you open up FileZilla, it should looks something like this: image1 The lower portion of the screen is split into two panes: the left pane (with the label “Local site” in the upper left corner) displays information relating to your local computer, and the right pane (with the greyed-out label “Remote site”) will display information pertaining to your home directory on src code.

      • To connect to src code, you need to fill out the connection bar at the top of the FileZilla window. For ‘Host’ put src-code.simons-rock.edu, for ‘Username’ and ‘Password’ put your Simon’s Rock credentials, and for ‘Port’ put 22, like so: image2 Once complete, click ‘Quickconnect’. Two pop-up windows will follow, one after the other: one will ask whether FileZilla should remember passwords (the choice is yours) and the other will notify you of an unknown host key (checking “Always trust this host, add this key to the cache” will prevent this popup from showing during future connections to src code). Click ‘OK’ for both pop-ups.

      • Assuming everything went well, your FileZilla window should look something like this: image3 All that’s left to do is upload the public_html folder. Navigate to your public_html folder with the left directory pane, right click it and select ‘Upload’. If the transfer is sucessful, then happy success messages should be displayed in the log above the directory panes: image5

And that’s it! Unfortunately, you will likely not be able to view your homepage at https://src-code.simons-rock.edu/~<username> right away (unless you’re quite lucky with your timing): currently, the server updates it’s cache at two hour intervals (starting from midnight) and so does not sync changes from public_html very rapidly. The initial upload and any future changes to your public_html folder will only become visible at that homepage URL at two hour intervals. This can be mitigated for most changes after the initial sync by appending ?nocache=true to the end of the homepage URL. After the initial sync, https://src-code.simons-rock.edu/~<username>?nocache=true will display content based on the current public_html, regardless of the time, but note that the wait required for the intial sync after the initial upload is unavoidable.

If you’ve placed static content other than HTML and CSS files inside public_html (images, music, movies and other files that are just stored in the directory and not generated by programs), these are also made accessible. For example, if you have a folder inside public_html named songs that contains the music track song.oga, song.oga is accessible via https://src-code.simons-rock.edu/~<username>/songs/song.oga. The ?nocache=true flag can be used here as well.

Requiring Authentication

Directions forthcoming.

More Info

If you would like to read more about the technical workings of the server, or would like to learn about developing interactive web applications, please contact Dennis Chen.