User Tools

Site Tools

Trace:
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
metaarray [2020/09/22 06:47] – Format fixes peteyboymetaarray [2024/09/05 05:47] (current) – st” 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 ===
  
-To enable your access to **ma.sdf.org**, run '//metaarray//' at the shell. This will first generate a random login password followed by a random database password sent via local e-mail if you have a DBA membership. To connect, use '//ssh ma.sdf.org//' (port 22 or 8080). Once you are connected, you can change your password with the 'passwd' command. If you ever forget your password, just run '//metaarray//' again from any of the regular nodes of the SDF cluster.+To enable your access to **ma.sdf.org**, run ‘//metaarray//’ at the shell. This will first generate a random login password followed by a random database password sent via local e-mail if you have a DBA membership. To connect, use ‘//ssh ma.sdf.org//’ (port 22 or 8080). Once you are connected, you can change your password with the ‘passwd’ command. If you ever forget your password, just run ‘//metaarray//’ again from any of the regular nodes of the SDF cluster.
  
 === Disk Layout === === Disk Layout ===
 +
 The MetaArray Logical Volume spans multiple Volume Groups across multiple Physical Volumes which are organized as multiple disk drives organized in multiple hardware RAID level 5 groups. To the user, this all appears to be under one contiguous file system: ///meta// The MetaArray Logical Volume spans multiple Volume Groups across multiple Physical Volumes which are organized as multiple disk drives organized in multiple hardware RAID level 5 groups. To the user, this all appears to be under one contiguous file system: ///meta//
  
Line 19: Line 20:
         * /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.
  
 The package directory structure is as follows: The package directory structure is as follows:
Line 35: Line 36:
  
         * 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+        * setvmail         Put ‘**$LOGNAME@ma.sdf.org**’ in your .forward on the SDF Cluster
                             Your default email address is **$LOGNAME@SDF.ORG**                             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
Line 50: Line 51:
 To host your personal website on the MetaArray, please do the following: To host your personal website on the MetaArray, please do the following:
  
-      * run 'mkhomepg' on the MetaArray. This creates the $HOME/html symlink and sets initial permissions.+      * run ‘mkhomepg’ on the MetaArray. This creates the $HOME/html symlink and sets initial permissions.
       * upload your site to $HOME/html on the MetaArray.       * upload your site to $HOME/html on the MetaArray.
-      * run 'mkhomepg' again on the MetaArray. This sets proper permissions on your content. +      * run ‘mkhomepg’ again on the MetaArray. This sets proper permissions on your content. 
-      * run 'mkhomepg -t' on the SDF cluster to toggle your site to the MetaArray+      * run ‘mkhomepg -t’ on the SDF cluster to toggle your site to the MetaArray
  
-NOTE: 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.+NOTE: 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+=== 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 ===
-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)+ 
 +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/]]. 
 + 
 +To initialize your login, go to [[https://ma.sdf.org/nc/|https://ma.sdf.org/nc/]], click “Forgot password?”, and enter your SDF username. 
 + 
 +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)
  
 === Using SDF Nextcloud on ShareX === === Using SDF Nextcloud on ShareX ===
Line 84: Line 93:
       * Select from the menu: **Image Uploader - File Uploader - Nextcloud**       * Select from the menu: **Image Uploader - File Uploader - Nextcloud**
  
-Legacy link: http://sdf.org/?tutorials/metaarray+Traditional link (using [[wp>Revision_Control_System|RCS]]): http://sdf.org/?tutorials/metaarray
  $Id: metaarray.html,v 1.38 2018/08/15 02:09:33 echosa Exp $  $Id: metaarray.html,v 1.38 2018/08/15 02:09:33 echosa Exp $
 +
metaarray.1600757237.txt.gz · Last modified: 2020/09/22 06:47 by peteyboy