User Tools

Site Tools


the_metaarray

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
the_metaarray [2021/05/18 07:23] – merge better-formatted Nextcloud section from "metarray" (why are there two?) peteyboythe_metaarray [2023/01/26 00:14] – formatting simple personal server hosting peteyboy
Line 24: Line 24:
 ===== Executables and Packages ===== ===== Executables and Packages =====
  
-Packages on the MetaArray are managed with **pkgsrc** and **yum**. Nearly any program or package can be installed by making a request on the regular nodes of the SDF cluster via the '//bboard//' REQUESTS.+Packages on the MetaArray are managed with **pkgsrc** and **dpkg/apt-get**. Nearly any program or package can be installed by making a request on the regular nodes of the SDF cluster via the '//bboard//' REQUESTS.
  
 The package directory structure is as follows: The package directory structure is as follows:
  
-|  *  | /bin, /usr/bin | (yum repo destination directories) |+|  *  | /bin, /usr/bin | (apt-get 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) |
 +|  *  | /meta/sdf/bin | (compiled binaries installed by MetaARPA members) |
 ===== Services and features ===== ===== Services and features =====
  
Line 39: Line 39:
 |*|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 ClusterYour 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|
Line 57: Line 57:
 It may take up to 10 minutes for DNS to update locally; however your ISP DNS server may cache this data for up to 12 hours so you won't see the change immediately. Use the "host" command on the cluster to see if DNS has changed, and "lynx" on the cluster to verify that the site loads: then be patient as DNS changes propagate. It may take up to 10 minutes for DNS to update locally; however your ISP DNS server may cache this data for up to 12 hours so you won't see the change immediately. Use the "host" command on the cluster to see if DNS has changed, and "lynx" on the cluster to verify that the site loads: then be patient as DNS changes propagate.
  
-* The DOCROOT for your directory defaults to no-read access, so you must have an index.html. Directory listings will work on subdirs within the DOCROOT. You can defeat this by running 'chmod g+r $HOME/html'+ * The ''DOCROOT'' for your directory defaults to no-read access, so you must have an index.html. Directory listings will work on subdirs within the ''DOCROOT''. You can defeat this by running 'chmod g+r $HOME/html'
  
 * https through a self signed certificate is only available to personal URLs under *.sdf.org * 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'' .
 +
 +
 +===== Simple Personal Server Hosting =====
 + META users can run simple servers using the port that matches their user id. You may run a simple server process on the metaarray as long as it does not circumvent a membership and is a small server "of reasonable or less foot-print". Find more detail and instructions in [[Meta Port Allocation]]
 + 
  
 ===== SDF Nextcloud ===== ===== SDF Nextcloud =====
the_metaarray.txt · Last modified: 2023/07/01 00:15 by hc9