Differences

This shows you the differences between two versions of the page.

--- the_metaarray [2021/05/18 07:26] – [Services and features] added period peteyboy
+++ the_metaarray [2022/02/25 05:17] – [Executables and Packages] hc9
@@ Line 17: / Line 17: @@
 The user directory structure is as follows:
-|*|/meta/initial/user|(home directory, considered private)|
+|•|/meta/initial/user|(home directory, considered private)|
-|*|/meta/www/initial/user|(web directory, considered public served via http)|
+|•|/meta/www/initial/user|(web directory, considered public served via http)|
-|*|/meta/log|(person website access log)|
+|•|/meta/log|(person website access log)|
-|*|/meta/mail/user|(user's mailbox - see the [[:configuration_changes_needed_when_using_maildir|Maildir tutorial]])|
+|•|/meta/mail/user|(user's mailbox - see the [[:configuration_changes_needed_when_using_maildir|Maildir tutorial]])|
 ===== Executables and Packages =====
@@ Line 28: / Line 28: @@
 The package directory structure is as follows:
-|  *  | /bin, /usr/bin | (yum repo destination directories) |
+|  •  | /bin, /usr/bin | (yum repo destination directories) |
-|  *  | /usr/pkg/bin | (pkgsrc destination directories) |
+|  •  | /usr/pkg/bin | (pkgsrc destination directories) |
-|  *  | /usr/local/bin | (MetaArray specific utilities) |
+|  •  | /usr/local/bin | (MetaArray specific utilities) |
 ===== Services and features =====
@@ Line 36: / Line 36: @@
 The MetaArray includes all features of the MetaARPA membership. However, some SDF specific utilities may not be available on the MetaArray because it is designed to be isolated from the SDF cluster. Some MetaArray specific services must be manually configured by the user.
-|*|screen, tmux|Terminal managers|
+|•|screen, tmux|Terminal managers|
-|*|mkcron|Use '//crontab -e//' to edit your crontab|
+|•|mkcron|Use '//crontab -e//' to edit your crontab|
-|*|mkhomepg|Use '//mkhomepg -t//' on the SDF Cluster to toggle website hosting 'mkhomepg' on the MetaArray will set secure perms for /meta/www|
+|•|mkhomepg|Use '//mkhomepg -t//' on the SDF Cluster to toggle website hosting 'mkhomepg' on the MetaArray will set secure perms for /meta/www|
-|*|setvmail|Put '**$LOGNAME@ma.sdf.org**' in your .forward on the SDF Cluster. Your default email address is **$LOGNAME@SDF.ORG**|
+|•|setvmail|Put '**$LOGNAME@ma.sdf.org**' in your .forward on the SDF Cluster. Your default email address is **$LOGNAME@SDF.ORG**|
-|*|webmail|Be sure to forward your mail, login via https://ma.sdf.org|
+|•|webmail|Be sure to forward your mail, login via https://ma.sdf.org|
-|*|IMAP|imap(143) and imaps(993) address is ma.sdf.org|
+|•|IMAP|imap(143) and imaps(993) address is ma.sdf.org|
-|*|X11|Connect with either ssh -X or ssh -Y to ma.sdf.org|
+|•|X11|Connect with either ssh -X or ssh -Y to ma.sdf.org|
-|*|Port forwarding|(via SSH)|
+|•|Port forwarding|(via SSH)|
-|*|startsql|MySQL database (with DBA membership)|
+|•|startsql|MySQL database (with DBA membership)|
 ===== Personal Website Hosting =====
@@ Line 61: / Line 61: @@
 * https through a self signed certificate is only available to personal URLs under *.sdf.org
+* Migrating your CGI scripts from the cluster to the MetaArray? You'll need to pay attention to the filename (only '.cgi' seems to work) and the path to the interpreter. For example, the following script will generate an actual webpage when served from the cluster, but when served from the MetaArray will prompt your browser for a location to save the script itself (first because the path to the interpreter is wrong, and second because the file extension is not recognized by nginx as needing the fastcgi module for its processing).
+  #!/usr/pkg/bin/python3.9
+  # saved as $HOME/html/my_powerful.py
+  import cgi
+  print('Content-Type:text/html')
+  print()
+  print('<!DOCTYPE html>')
+  print('<html lang="en">')
+  print('<head>')
+  print('<title>My powerful script</title>')
+  print('</head>')
+  print('<body>')
+  print('Hello, World!')
+  print('</body>')
+  print('</html>')
+To get this script to behave properly on the MetaArray, change the first line to ''#!/usr/bin/env python3.9'', and rename the file as ''my_powerful.cgi'' .
 ===== SDF Nextcloud =====