| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| metaarray [2021/03/12 19:00] – hc9 | metaarray [2021/05/18 07:27] (current) – fix list format peteyboy |
|---|
| === 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 === |
| * /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 === |
| 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 === | === Simple Personal Server Hosting === |
| | |
| === 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 === |
