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/04 03:21] – [Executables and Packages] hc9 | the_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:// | + | 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: | ||
- | |*|/ | + | |•|/ |
- | |*|/ | + | |•|/ |
- | |*|/ | + | |•|/ |
- | |*|/ | + | |•|/ |
===== Executables and Packages ===== | ===== Executables and Packages ===== | ||
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) | |
- | | | + | |•| / |
- | | | + | |•| / |
===== Services and features ===== | ===== 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. | 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 '// | + | |•|mkcron|Use '// |
- | |*|mkhomepg|Use '// | + | |•|mkhomepg|Use '// |
- | |*|setvmail|Put ' | + | |•|setvmail|Put ' |
- | |*|webmail|Be sure to forward your mail, login via https:// | + | |•|webmail|Be sure to forward your mail, login via https:// |
- | |*|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 ===== | ===== Personal Website Hosting ===== | ||
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 " | 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/ | + | * The '' |
* 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 ' | ||
+ | |||
+ | # | ||
+ | # saved as $HOME/ | ||
+ | import cgi | ||
+ | | ||
+ | print(' | ||
+ | print() | ||
+ | print('< | ||
+ | print('< | ||
+ | print('< | ||
+ | print('< | ||
+ | print('</ | ||
+ | print('< | ||
+ | print(' | ||
+ | print('</ | ||
+ | print('</ | ||
+ | |||
+ | To get this script to behave properly on the MetaArray, change the first line to ''# | ||
===== SDF Nextcloud ===== | ===== SDF Nextcloud ===== | ||
Line 72: | Line 91: | ||
If you'd like to use SDF's Nextcloud as a destination for ShareX then follow the steps below: | 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// | |
- | note: This tutorial was written for 10.1 | + | * Configure ShareX Destination for SDF Nextcloud |
- | + | * Open the ShareX application window | |
- | | + | * Click on Destinations |
- | * Open the ShareX application window | + | * Click on Destination Settings |
- | * Click on Destinations | + | * Select on the left pane, Nextcloud (under File uploaders) |
- | * Click on Destination Settings | + | |
- | * Select on the left pane, Nextcloud (under File uploaders) | + | * Host: https:// |
- | | + | * Username: your sdf_nc login |
- | * Enter: | + | * Password: your sdf_nc password |
- | * Host: https:// | + | * Path: /foo |
- | * Username: your sdf_nc login | + | |
- | * Password: your sdf_nc password | + | * Create shareable URL (Optional) |
- | * Path: /foo | + | * Ignore invalid SSL certificate (Required) |
- | + | | |
- | Place a check next to: | + | |
- | + | ||
- | | + | |
- | * Ignore invalid SSL certificate (Required) | + | |
- | + | ||
- | Close the settings window | + | |
- | + | ||
- | Select from the menu Image Uploader - File Uploader - Nextcloud | + | |
$Id: metaarray.html, | $Id: metaarray.html, | ||
the_metaarray.txt · Last modified: 2023/07/01 00:15 by hc9