Hi Professor Higgins,
I took a quick look at the KLC guide and found one main item that seems worth updating, plus a couple of optional workflow suggestions.
Main update: KLC hostname format
The guide currently uses the older ci.northwestern.edu hostname format, for example:
klc0307.ci.northwestern.edu
ssh <netID>@klc<node>.ci.northwestern.edu
The current KRS documentation uses the quest.northwestern.edu domain instead, for example:
ssh <netID>@klc0307.quest.northwestern.edu
Source: https://rs-kellogg.github.io/krs-cookbook/klc-accessing.html
I also tested this on my side: the ci.northwestern.edu hostname did not resolve, while the quest.northwestern.edu hostname worked. So the FileZilla host example and the SSH command in the README should probably be updated from ci.northwestern.edu to quest.northwestern.edu.
Optional workflow suggestions
A few optional additions could improve the experience of working with KLC:
-
Termius could be mentioned as an optional SSH/SFTP client. It integrates SSH and SFTP in one app, syncs across platforms/devices, and is available to education users/students through the GitHub Student Developer Pack.
Source: https://termius.com/education
-
rclone could be mentioned as an optional advanced file-transfer tool. It is an open-source CLI and supports both local files and cloud storage providers such as Dropbox, Google Drive, OneDrive, Box, and S3. This is useful when large data files are already in Dropbox/cloud storage, because users can copy/sync them directly to KLC instead of downloading to a laptop and re-uploading through SFTP. It also supports --dry-run, filtering, batch transfers, and scripting, so it works well with AI-assisted CLI workflows.
Sources: https://rclone.org/dropbox/ and https://rclone.org/docs/
Hi Professor Higgins,
I took a quick look at the KLC guide and found one main item that seems worth updating, plus a couple of optional workflow suggestions.
Main update: KLC hostname format
The guide currently uses the older
ci.northwestern.eduhostname format, for example:The current KRS documentation uses the
quest.northwestern.edudomain instead, for example:Source: https://rs-kellogg.github.io/krs-cookbook/klc-accessing.html
I also tested this on my side: the
ci.northwestern.eduhostname did not resolve, while thequest.northwestern.eduhostname worked. So the FileZilla host example and the SSH command in the README should probably be updated fromci.northwestern.edutoquest.northwestern.edu.Optional workflow suggestions
A few optional additions could improve the experience of working with KLC:
Termius could be mentioned as an optional SSH/SFTP client. It integrates SSH and SFTP in one app, syncs across platforms/devices, and is available to education users/students through the GitHub Student Developer Pack.
Source: https://termius.com/education
rclone could be mentioned as an optional advanced file-transfer tool. It is an open-source CLI and supports both local files and cloud storage providers such as Dropbox, Google Drive, OneDrive, Box, and S3. This is useful when large data files are already in Dropbox/cloud storage, because users can copy/sync them directly to KLC instead of downloading to a laptop and re-uploading through SFTP. It also supports
--dry-run, filtering, batch transfers, and scripting, so it works well with AI-assisted CLI workflows.Sources: https://rclone.org/dropbox/ and https://rclone.org/docs/