User Tools

Site Tools

Trace:
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/03/11 01:34] – [Acceptable Use Policy] hc9the_metaarray [2022/02/25 05:17] – [Executables and Packages] hc9
Line 5: Line 5:
 ===== Acceptable Use Policy ===== ===== Acceptable Use Policy =====
  
-Users of the MetaArray must agree to abide by the [[http://sdf.org/?tutorials/metaarray_aup|MetaArray Acceptable Use Policy]]+Users of the MetaArray must agree to abide by the [[:metaarray_acceptable_use_policy|MetaArray Acceptable Use Policy]]
  
 ===== Getting Started ===== ===== Getting Started =====
Line 17: Line 17:
 The user directory structure is as follows: 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 [[http://sdf.org/?tutorials/maildir|Maildir tutorial]])+|•|/meta/mail/user|(user's mailbox - see the [[:configuration_changes_needed_when_using_maildir|Maildir tutorial]])|
  
-=== 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 **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.
Line 28: Line 28:
 The package directory structure is as follows: 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 ===+===== Services and features =====
  
 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. 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|Use '//mkhomepg -t//' on the SDF Cluster to toggle website hosting 'mkhomepg' on the MetaArray will set secure perms for /meta/www|   
-                       '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 +|•|webmail|Be sure to forward your mail, login via https://ma.sdf.org| 
-                        Your default email address is **$LOGNAME@SDF.ORG** +|•|IMAP|imap(143) and imaps(993) address is ma.sdf.org| 
-    * webmail          Be sure to forward your mail, login via https://ma.sdf.org +|•|X11|Connect with either ssh -X or ssh -Y to ma.sdf.org| 
-    * IMAP             imap(143) and imaps(993) address is ma.sdf.org +|•|Port forwarding|(via SSH)| 
-    * X11              Connect with either ssh -X or ssh -Y to ma.sdf.org +|•|startsql|MySQL database (with DBA membership)|
-    * Port forwarding  (via SSH) +
-    * startsql         MySQL database (with DBA membership)+
  
-=== Personal Website Hosting ===+===== Personal Website Hosting =====
  
 To host your personal website on the MetaArray, please do the following: To host your personal website on the MetaArray, please do the following:
Line 59: 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
  
-=== SDF Nextcloud ===+* 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).
  
-SDF makes available an [[https://nextcloud.com/|Nextcloud]] instance at https://ma.sdf.org/nc/. To initialize your login, run the //metaarray// command on the cluster and check for instructions via e-mail.In order to connect to your instance from a client, the server should be set to **https://ma.sdf.org/nc/**. (the client will probably complain for the *.sdf.org SSL certificate, but that's fine)+  #!/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>')
  
-=== Using SDF Nextcloud on ShareX ===+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 =====
  
-If you'd like to use SDF's Nextcloud as a destination for ShareX then follow the steps below:note: This tutorial was written for 10.1 +SDF makes available a //Nextcloud (([[https://nextcloud.com/|Nextcloud -- Share and collaborate on documents, send and receive email, manage your calendar and have video chats without data leaks]]))// instance at [[https://ma.sdf.org/nc/|https://ma.sdf.org/nc/]].
-  * Configure ShareX Destination for SDF Nextcloud +
-  * Open the ShareX application window +
-  * Click on Destinations +
-  * Click on Destination Settings +
-  * Select on the left pane, Nextcloud (under File uploaders) +
-  * Enter: +
-  * Host: https://ma.sdf.org/nc +
-  * Username: your sdf_nc login +
-  * Password: your sdf_nc password +
-  * Path: /foo Place a check next to: +
-  * Create shareable URL (Optional) +
-  * Ignore invalid SSL certificate (Required)+
  
-Close the settings window+To initialize your login, go to [[https://ma.sdf.org/nc/|https://ma.sdf.org/nc/]], click "Forgot password?", and enter your SDF username.
  
-Select from the menu Image Uploader - File Uploader - Nextcloud+In order to connect to your instance from a client, the "server" should be set to "**<nowiki>https://ma.sdf.org/nc/</nowiki>**". (The client might complain about the *.sdf.org SSL certificate, but that's fine)
  
-$Id: metaarray.html,v 1.38 2018/08/15 02:09:33 echosa Exp $ [[http://sdf.org/?tutorials/metaarray|The MetaArray]] legacy link+===== Using SDF Nextcloud on ShareX ===== 
 + 
 +If you'd like to use SDF's Nextcloud as a destination for ShareX then follow the steps below: 
 +//note: This tutorial was written for 10.1// 
 +      * Configure ShareX Destination for SDF Nextcloud 
 +      * Open the ShareX application window 
 +      * Click on Destinations 
 +      * Click on Destination Settings 
 +      * Select on the left pane, Nextcloud (under File uploaders) 
 +      *  Enter: 
 +        * Host: https://ma.sdf.org/nc 
 +        * Username: your sdf_nc login 
 +        * Password: your sdf_nc password 
 +        * Path: /foo  
 +      * Place a check next to: 
 +          * Create shareable URL (Optional) 
 +          * Ignore invalid SSL certificate (Required)  
 +      * Close the settings window 
 +      * Select from the menu: **Image Uploader - File Uploader - Nextcloud** 
 + 
 +$Id: metaarray.html,v 1.38 2018/08/15 02:09:33 echosa Exp $ [[http://sdf.org/?tutorials/metaarray|The MetaArray]] - traditional link (using [[wp>Revision_Control_System|RCS]])
  
the_metaarray.txt · Last modified: 2023/07/01 00:15 by hc9