the_metaarray
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
the_metaarray [2021/04/03 15:58] – [SDF Nextcloud] hc9 | the_metaarray [2023/03/28 00:41] – [Getting Started] added line about emailing membership peteyboy | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Acceptable Use Policy ===== | ===== Acceptable Use Policy ===== | ||
- | Users of the MetaArray must agree to abide by the [[http:// | + | 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**, | + | To enable your access to **ma.sdf.org**, |
+ | >For passwords and access questions, please always email membership@sdf.org | ||
+ | |||
+ | |||
===== Disk Layout ===== | ===== Disk Layout ===== | ||
Line 16: | Line 20: | ||
The user directory structure is as follows: | The user directory structure is as follows: | ||
- | + | ^ Directory ^ Description ^ | |
- | |*|/ | + | |/ |
- | |*|/ | + | |/ |
- | |*|/meta/log|(person website access log)| | + | |meta/log| person website access log| |
- | |*|/ | + | |/ |
===== 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 '// | + | Packages on the MetaArray are managed with **pkgsrc** and **dpkg/ |
The package directory structure is as follows: | The package directory structure is as follows: | ||
- | + | ^ Path ^ Description ^ | |
- | |*|/bin, /usr/bin|(yum repo destination directories)| | + | | /bin, /usr/bin | apt-get |
- | |*|/ | + | | / |
- | |*|/ | + | | / |
+ | | / | ||
===== Services and features ===== | ===== Services and features ===== | ||
Line 36: | Line 41: | ||
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| | + | ^ Service/ |
- | |*|mkcron|Use '// | + | |screen, tmux|Terminal managers| |
- | |*|mkhomepg|Use '// | + | |mkcron|Use '// |
- | |*|setvmail|Put ' | + | |mkhomepg|Use '// |
- | |*|webmail|Be sure to forward your mail, login via https:// | + | |setvmail|Put ' |
- | |*|IMAP|imap(143) and imaps(993) address is ma.sdf.org| | + | |webmail|Be sure to forward your mail, login via https:// |
- | |*|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 ===== | ||
Line 50: | Line 56: | ||
To host your personal website on the MetaArray, please do the following: | To host your personal website on the MetaArray, please do the following: | ||
- | | + | |
- | | + | |
- | | + | |
- | | + | |
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 " | 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 " | ||
- | * 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/ | + | |
- | * 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 ' |
- | SDF makes available a [[https://nextcloud.com/|Nextcloud]] instance at [[https://ma.sdf.org/nc/|https://ma.sdf.org/nc/]]. | + | #!/usr/pkg/bin/python3.9 |
+ | # saved as $HOME/html/my_powerful.py | ||
+ | import cgi | ||
+ | |||
+ | print(' | ||
+ | print() | ||
+ | print('< | ||
+ | print('< | ||
+ | print('< | ||
+ | print('< | ||
+ | print('< | ||
+ | print('< | ||
+ | print(' | ||
+ | print('< | ||
+ | print('</ | ||
- | To initialize your login, go to [[https://ma.sdf.org/ | + | To get this script to behave properly on the MetaArray, change the first line to ''# |
- | In order to connect to your instance from a client, the " | ||
- | ===== Using SDF Nextcloud on ShareX | + | ===== 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" | ||
+ | |||
- | If you'd like to use SDF' | + | ===== SDF Nextcloud |
- | note: This tutorial was written for 10.1 | + | SDF makes available a //Nextcloud (([[https:// |
- | * Configure ShareX Destination for SDF Nextcloud | + | To initialize your login, go to [[https:// |
- | * Open the ShareX application window | + | |
- | * Click on Destinations | + | |
- | * Click on Destination Settings | + | |
- | * Select on the left pane, Nextcloud (under File uploaders) | + | |
- | + | ||
- | * Enter: | + | |
- | * Host: https:// | + | |
- | * Username: your sdf_nc login | + | |
- | * Password: your sdf_nc password | + | |
- | * Path: /foo | + | |
- | Place a check next to: | + | In order to connect to your instance from a client, the " |
- | * Create shareable URL (Optional) | + | ===== Using SDF Nextcloud on ShareX ===== |
- | * Ignore invalid SSL certificate (Required) | + | |
- | Close the settings window | + | 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// | |
- | Select from the menu Image Uploader - File Uploader - Nextcloud | + | * 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:// | ||
+ | * 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 | ||
+ | | ||
$Id: metaarray.html, | $Id: metaarray.html, | ||
the_metaarray.txt · Last modified: 2023/07/01 00:15 by hc9