https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&user=Kmerrick&feedformat=atomUMIACS - User contributions [en]2024-03-28T21:18:41ZUser contributionsMediaWiki 1.39.6https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&diff=7062WebSpace2016-08-02T20:26:00Z<p>Kmerrick: </p>
<hr />
<div>UMIACS provides web space hosting for research/lab pages and user pages.<br />
<br />
==Main Website and Lab Pages==<br />
<br />
<pre>http://www.umiacs.umd.edu</pre><br />
<br />
Users can access the main website and lab sites for editing in two ways:<br />
* From <b>Unix</b> as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])<br />
* From <b>Windows</b> as \\umiacs-webftp.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]<br />
<br />
Faculty members and authorized users can modify their own public profiles on the main UMIACS homepage. For instructions, see [[ContentManagement]].<br />
<br />
==Personal Web Space==<br />
<br />
<pre>http://www.umiacs.umd.edu/~username</pre><br />
<br />
Users can access their website for editing two ways:<br />
<br />
* From <b>Unix</b> as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])<br />
* From <b>Windows</b> as \\umiacs-webftp.umiacs.umd.edu\www-users\username - and remotely accessed by the same file share over the [[VPN]]<br />
<br />
In general, large datasets related to a Labs research should go into the specific lab's web tree, not the individual users. Remember that users' webpage is not permanently maintained once the user leaves UMIACS.<br />
<br />
==Adding A Password Protected Folder To Your Web Space==<br />
<br />
1) Create the directory you want to password protect or <tt>cd</tt> into the directory you want to password protect<br />
<br />
2) Create a file called ''.htaccess'' (<tt> vi .htaccess</tt>) in the directory you wish to password protect.<br />
<br />
3) In the file you just created type the following lines <br />
<br />
<pre><br />
AuthUserFile "/your/directory/here/".htpasswd<br />
AuthName "Secure Document"<br />
AuthType Basic<br />
require user username<br />
</pre><br />
<br />
For example, if you were going to protect the <tt>/fs/www-users/username/private</tt> directory and you want the required name to be <tt>class239</tt>, then your file would look like this:<br />
<pre><br />
AuthUserFile /fs/www-users/username/private/.htpasswd<br />
AuthName "Secure Document"<br />
AuthType Basic<br />
require user class239<br />
</pre><br />
<br />
4) Create a file called ''.htpasswd'' in the same directory as ''.htaccess''. You create this file by typing in <tt>htpasswd -c .htpasswd ''username''</tt> in the directory area to be protected.<br />
<br />
In the example above, the username is <tt>class239</tt> so you would type <tt>htpasswd -c .htpasswd class239</tt><br />
<br />
You will be prompted to enter the password you want. The ''.htpasswd'' file will be created in the current directory and will contain an encrypted version of the password.<br />
<br />
To later change the username, edit the ''.htaccess'' file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.<br />
<br />
==Restricting Content based on IP address==<br />
It is possible to have pages on your webspace only accessible to clients connecting from certain IP addresses. In order to accomplish this, cd in to the directory you wish to restrict, and edit your ''.htaccess'' file. The example below shows how to make content only viewable to clients connecting from the UMD wifi in Apache 2.2.<br />
<br />
<pre style="white-space: pre-wrap; <br />
white-space: -moz-pre-wrap; <br />
white-space: -pre-wrap; <br />
white-space: -o-pre-wrap; <br />
word-wrap: break-word;">SetEnvIF X-Forwarded-For "^128\.8\.\d+\.\d+$" UMD_NETWORK<br />
SetEnvIF X-Forwarded-For "^129\.2\.\d+\.\d+$" UMD_NETWORK<br />
SetEnvIF X-Forwarded-For "^192\.168\.\d+\.\d+$" UMD_NETWORK<br />
SetEnvIF X-Forwarded-For "^206\.196\.(?:1[6-9][0-9]|2[0-5][0-9])\.\d+$" UMD_NETWORK<br />
SetEnvIF X-Forwarded-For "^10\.\d+\.\d+\.\d+$" UMD_NETWORK<br />
Order Deny,Allow<br />
Deny from all<br />
Allow from env=UMD_NETWORK<br />
</pre><br />
<br />
The SetEnvIF directive will modify one's environment if the specified attribute matches the provided regular expression. In this example, IP addresses that are forwarded from an IP within UMD's IP space are tagged with UMD_NETWORK. Then, all traffic to the example directory is blocked unless it has the UMD_NETWORK tag. See the following pages for a more in depth explanation of the commands used.<br />
<br />
[https://httpd.apache.org/docs/2.2/howto/htaccess.html .htaccess], [https://httpd.apache.org/docs/2.2/mod/mod_setenvif.html#setenvif SetEnvIf], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order Order], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#deny Deny], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow Allow]</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Shell&diff=6864Shell2016-04-21T18:02:13Z<p>Kmerrick: /* Adding paths */ removed link to minor shells</p>
<hr />
<div>===Changing your shell===<br />
You can use our [https://intranet.umiacs.umd.edu/directory/info/ web application] to change your default shell for new access, a specific [[ComputationalResource]] or all your shells in all [[ComputationalResource]]s.<br />
<br />
'''Warning:''' Attempting to change your shell by starting a new shell in the initialization files for your current shell can result in issues in services such as sftp<br />
<br />
===Adding paths===<br />
Please choose what type of Shell you are using. You can type the following in a terminal to see what shell you are using,<br />
<br />
<tt>echo $SHELL</tt><br />
<br />
* [[Bash]]<br />
* [[Tcsh]]<br />
* sh<br />
* csh<br />
* zsh<br />
* ksh</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Bash&diff=6863Bash2016-04-21T18:01:27Z<p>Kmerrick: /* Configuration Files */</p>
<hr />
<div>'''Bourne-again shell'''<br />
<br />
=Configuration Files=<br />
Bash has two main configuration files, ~/.bash_profile and ~/.bashrc in addition to the ones provided by the operating system. Please note that they are used differently depending on if you have started a login shell or a interactive shell.<br />
<br />
Login shells (ssh, console) use ~/.bash_profile<br />
<br />
Interactive shells (additional terminals in X) use ~/.bashrc<br />
<br />
Please see the man page by typing <code>man bash</code> for a complete explanation of features or see the [http://www.gnu.org/s/bash/manual/bash.html Bash Reference Manual].<br />
<br />
To change your shell, see [[shell]]<br />
<br />
=Paths=<br />
You can see your current paths (colon separated list) by the typing the following in your terminal.<br />
<br />
echo $PATH<br />
<br />
You can add additional paths by using the following command<br />
<br />
export PATH=${PATH}:/the/new/path<br />
<br />
By moving around the ${PATH} you can control the order that programs are found in your path (the path is looked up left to right).</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Tcsh&diff=6862Tcsh2016-04-21T18:00:56Z<p>Kmerrick: /* Configuration Files */</p>
<hr />
<div>=Configuration Files=<br />
Tcsh has two main configuration files either ~/.tcshrc or ~/.cshrc in addition to the ones provided by the operating system. It will source ~/.tcshrc first if it is found and if not then ~/.cshrc.<br />
<br />
Please type <code>man tcsh</code> for a complete explanation of features or see the online [http://www.tcsh.org/tcsh.html/top.html TCSH] documentation.<br />
<br />
To change your shell, see [[shell]]<br />
<br />
=Paths=<br />
You can see your current paths (colon separated list) by the typing the following in your terminal.<br />
<br />
echo $PATH<br />
<br />
You can add additional paths by using the following command<br />
<br />
setenv PATH ${PATH}:/my/new/path<br />
<br />
By moving around the ${PATH} you can put the path at the front of the list or the back as the programs are looked up left to right in the path.</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Shell&diff=6861Shell2016-04-21T17:50:18Z<p>Kmerrick: /* Adding paths */ added links to new pages on the wiki</p>
<hr />
<div>===Changing your shell===<br />
You can use our [https://intranet.umiacs.umd.edu/directory/info/ web application] to change your default shell for new access, a specific [[ComputationalResource]] or all your shells in all [[ComputationalResource]]s.<br />
<br />
'''Warning:''' Attempting to change your shell by starting a new shell in the initialization files for your current shell can result in issues in services such as sftp<br />
<br />
===Adding paths===<br />
Please choose what type of Shell you are using. You can type the following in a terminal to see what shell you are using,<br />
<br />
<tt>echo $SHELL</tt><br />
<br />
* [[Bash]]<br />
* [[Tcsh]]<br />
* [[sh]]<br />
* [[csh]]<br />
* [[zsh]]<br />
* [[ksh]]</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&diff=6860SSHFileTransferProtocol2016-04-20T18:58:48Z<p>Kmerrick: </p>
<hr />
<div>SSH File Transfer Protocol ([http://en.wikipedia.org/wiki/SSH_file_transfer_protocol SFTP]) is a network protocol used to securely transfer and manage files on remote systems. SFTP is layered on top of the [[SSH]] protocol, and is preferred over [[FTP]] as a method of remote file transfer.<br />
<br />
'''Warning:''' running interactive programs in your shell initialization files, such as starting another shell, causes SFTP to fail. See [[Shell]] on how to correctly change the shell you are using<br />
<br />
==Connecting to an SFTP Server==<br />
Under Under Red Hat Enterprise Linux, Ubuntu Linux, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].<br />
<br />
wing:~ bkirz$ sftp bkirz@openlab.umiacs.umd.edu<br />
<br />
For UMIACS supported Windows hosts, a SFTP client is already installed. For other hosts, you can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SFTP access. <br />
<br />
==Further Information==<br />
<br />
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&diff=6859SSHFileTransferProtocol2016-04-20T18:58:22Z<p>Kmerrick: added warning about starting shells in shell init files</p>
<hr />
<div>SSH File Transfer Protocol ([http://en.wikipedia.org/wiki/SSH_file_transfer_protocol SFTP]) is a network protocol used to securely transfer and manage files on remote systems. SFTP is layered on top of the [[SSH]] protocol, and is preferred over [[FTP]] as a method of remote file transfer.<br />
<br />
'''Warning:''' interactive programs in your shell initialization files, such as starting another shell, causes SFTP to fail. See [[Shell]] on how to correctly change the shell you are using<br />
<br />
==Connecting to an SFTP Server==<br />
Under Under Red Hat Enterprise Linux, Ubuntu Linux, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].<br />
<br />
wing:~ bkirz$ sftp bkirz@openlab.umiacs.umd.edu<br />
<br />
For UMIACS supported Windows hosts, a SFTP client is already installed. For other hosts, you can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SFTP access. <br />
<br />
==Further Information==<br />
<br />
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Shell&diff=6858Shell2016-04-20T18:54:36Z<p>Kmerrick: </p>
<hr />
<div>===Changing your shell===<br />
You can use our [https://intranet.umiacs.umd.edu/directory/info/ web application] to change your default shell for new access, a specific [[ComputationalResource]] or all your shells in all [[ComputationalResource]]s.<br />
<br />
'''Warning:''' Attempting to change your shell by starting a new shell in the initialization files for your current shell can result in issues in services such as sftp<br />
<br />
===Adding paths===<br />
Please choose what type of Shell you are using. You can type the following in a terminal to see what shell you are using,<br />
<br />
<tt>echo $SHELL</tt><br />
<br />
* [[Bash]]<br />
* [[Tcsh]]<br />
* sh<br />
* csh<br />
* zsh<br />
* ksh</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Shell&diff=6857Shell2016-04-20T18:54:00Z<p>Kmerrick: /* Changing your shell */ added warning about changing shells in init files</p>
<hr />
<div>===Changing your shell===<br />
You can use our [https://intranet.umiacs.umd.edu/directory/info/ web application] to change your default shell for new access, a specific [[ComputationalResource]] or all your shells in all [[ComputationalResource]]s.<br />
'''Warning:''' Attempting to change your shell by starting a new shell in the initialization files for your current shell can result in issues in services such as sftp<br />
<br />
===Adding paths===<br />
Please choose what type of Shell you are using. You can type the following in a terminal to see what shell you are using,<br />
<br />
<tt>echo $SHELL</tt><br />
<br />
* [[Bash]]<br />
* [[Tcsh]]<br />
* sh<br />
* csh<br />
* zsh<br />
* ksh</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Shell&diff=6856Shell2016-04-20T18:51:49Z<p>Kmerrick: /* Adding paths */ completed list of shells</p>
<hr />
<div>===Changing your shell===<br />
You can use our [https://intranet.umiacs.umd.edu/directory/info/ web application] to change your default shell for new access, a specific [[ComputationalResource]] or all your shells in all [[ComputationalResource]]s.<br />
<br />
===Adding paths===<br />
Please choose what type of Shell you are using. You can type the following in a terminal to see what shell you are using,<br />
<br />
<tt>echo $SHELL</tt><br />
<br />
* [[Bash]]<br />
* [[Tcsh]]<br />
* sh<br />
* csh<br />
* zsh<br />
* ksh</div>Kmerrickhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Programming&diff=6455Programming2015-01-09T21:23:44Z<p>Kmerrick: </p>
<hr />
<div>* C/C++<br />
** [[CCompilers|C/C++ Compilers]]<br />
** [[CDebuggers|C/C++ Debuggers]]<br />
* Java<br />
** [[JavaVersions|Java Versions]]<br />
** [[JavaDevelEnvironment|Java Development Environment]]<br />
* [[Perl | Perl]]<br />
** [[PerlVersions|Perl 5 Versions]]<br />
** [[PerlDevelEnvironment|Perl Development Environment]]<br />
** [[PerlModules|Perl Missing Modules]]<br />
* [[Python]]<br />
** [[Python]]<br />
** [[PythonVirtualEnv | Python Virtual Environment]]<br />
** [[WindowsPython | Windows Python ]]<br />
* OpenCV<br />
** [[OpenCVVersions | OpenCV Versions]]<br />
*CMake<br />
** [[CMake]]<br />
*R<br />
** [[R | R for Windows]]</div>Kmerrick