CS accounts - Revision history

Jkinne: /* Node, Django, etc. */

2026-02-18T02:13:15Z

Node, Django, etc.

← Older revision		Revision as of 02:13, 18 February 2026
Line 55:		Line 55:

	==Node, Django, etc.==		==Node, Django, etc.==
	Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu		Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

	=Assignments=		=Assignments=

Jkinne: /* Apache */

2026-02-18T02:09:20Z

Apache

← Older revision		Revision as of 02:09, 18 February 2026
Line 44:		Line 44:
	The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.		The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
	<pre>		<pre>
	cd ~jkinne@isuad.indstate.edu		cd ~jkinne@isuad.indstate.edu # jkinne's home directory
	mkdir public_html		mkdir public_html # directory apache looks in for website files
	setfacl -m group:www-data:x .		setfacl -m group:www-data:x . # give apache execute access to home directory
	setfacl -R -m group:www-data:rX public_html		setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
	setfacl -R -m default:group:www-data:rX public_html		setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
	cd public_html		cd public_html # go into that directory
	echo "Hello world" > index.html		echo "Hello world" > index.html # write a hello world file
	</pre>		</pre>
	Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.		Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

Jkinne: /* Apache */

2026-02-18T02:07:30Z

Apache

← Older revision		Revision as of 02:07, 18 February 2026
Line 42:		Line 42:
	=Websites / Webservers=		=Websites / Webservers=
	==Apache==		==Apache==
	The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code>, would do the following to create the right directories.		The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
	<pre>		<pre>
	cd ~jkinne		cd ~jkinne@isuad.indstate.edu
	mkdir public_html		mkdir public_html
	setfacl -m group:www-data:x .		setfacl -m group:www-data:x .

Jkinne: /* Assignments */

2026-02-18T02:06:41Z

Assignments

← Older revision		Revision as of 02:06, 18 February 2026
Line 39:		Line 39:

	When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).		When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

			=Websites / Webservers=
			==Apache==
			The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code>, would do the following to create the right directories.
			<pre>
			cd ~jkinne
			mkdir public_html
			setfacl -m group:www-data:x .
			setfacl -R -m group:www-data:rX public_html
			setfacl -R -m default:group:www-data:rX public_html
			cd public_html
			echo "Hello world" > index.html
			</pre>
			Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

			==Node, Django, etc.==
			Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu

	=Assignments=		=Assignments=

Jkinne: /* Assignments */

2026-01-15T19:06:07Z

Assignments

← Older revision		Revision as of 19:06, 15 January 2026
Line 44:		Line 44:

	A student can "checkout" or "get" an assignment by running		A student can "checkout" or "get" an assignment by running
	<~~code~~>hw_get.py cs151 h7</~~code~~>		<pre>hw_get.py cs151 h7</pre>
	This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.		This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

Jkinne: /* Assignments */

2026-01-15T19:05:43Z

Assignments

← Older revision		Revision as of 19:05, 15 January 2026
Line 42:		Line 42:
	=Assignments=		=Assignments=
	Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.		Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

			A student can "checkout" or "get" an assignment by running
			<code>hw_get.py cs151 h7</code>
			This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

	An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.		An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

Jkinne: /* Fall 2025 */

2026-01-09T03:12:52Z

Fall 2025

← Older revision		Revision as of 03:12, 9 January 2026
Line 45:		Line 45:
	An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.		An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

	=~~Fall 2025~~=		=Spring 2026=
	The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.		The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
	<pre>		<pre>
	course,admin_accounts		course,admin_accounts
	cs151,"jkinne,jkinne@isuad.indstate.edu,~~jeff~~"		cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
	cs201,majid		cs170,"hrafieipour@isuad.indstate.edu"
	cs203,namoako@isuad.indstate.edu		cs201,"majid,mafsharnoghon@isuad.indstate.edu"
	~~cs256~~,~~kwexoo~~		cs203,"namoako,namoako@isuad.indstate.edu"
	~~cs302~~,~~arash~~		cs211,"mjenkins1@isuad.indstate.edu"
	cs331,namoako@isuad.indstate.edu		cs351,"rabhyankar@isuad.indstate.edu"
	"cs401,cs501",majid		cs331,"namoako,namoako@isuad.indstate.edu"
	cs401L,majid		"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
	"~~cs473~~,~~cs573~~,~~cs680~~",jkinne		cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
	"~~cs479~~,~~cs579~~",katterson1		"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
	~~cs617~~,~~majid~~		cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
	cs685,arash		"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
	cs695,arash		cs457L,"kwexoo,kexoo@isuad.indstate.edu"
	~~ect437~~,jkinne		"cs458,cs558","namoako,namoako@isuad.indstate.edu"
			cs458L,"namoako,namoako@isuad.indstate.edu"
			"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
			"cs475,cs575","rabhyankar@isuad.indstate.edu"
			cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
			cs600,"arash,arafiey@isuad.indstate.edu"
			"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
			cs609,"katterson1,katterson1@isuad.indstate.edu"
			cs611,"rabhyankar@isuad.indstate.edu"
			cs618,"shosseini@isuad.indstate.edu"
			cs685,"arash,arafiey@isuad.indstate.edu"
			cs695,"arash,arafiey@isuad.indstate.edu"
			ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
	</pre>		</pre>
	If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.		If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

Jkinne: /* Change of Semester and Backups */

2026-01-09T03:11:18Z

Change of Semester and Backups

← Older revision		Revision as of 03:11, 9 January 2026
Line 38:		Line 38:
	Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.		Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

	When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students.		When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

	=Assignments=		=Assignments=

Jkinne: /* Course Account - Instructor Private Files */

2026-01-09T03:10:13Z

Course Account - Instructor Private Files

← Older revision		Revision as of 03:10, 9 January 2026
Line 31:		Line 31:

	The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>		The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>
			Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

	====Change of Semester and Backups====		====Change of Semester and Backups====

Jkinne: /* Course Account - Instructor Private Files */

2026-01-09T03:08:27Z

Course Account - Instructor Private Files

← Older revision		Revision as of 03:08, 9 January 2026
Line 28:		Line 28:
	The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).		The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

	Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' ~~accounts~~ by going to the private/students/ directory and going from there.		Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

	The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>		The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>