Service/shell: Difference between revisions
→Public web hosting: clarify |
Remove reference to git proxy |
||
| (16 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
''' | '''If you don't have a Sugar Labs account, visit [[Service/Account]] first.''' | ||
== Hostnames == | == Hostnames == | ||
| Line 9: | Line 9: | ||
[[Machine/sunjammer]] | [[Machine/sunjammer]] | ||
== Administrative contact == | == Administrative contact == | ||
| Line 18: | Line 17: | ||
For urgent requests, the list of systems administrators is on [[Machine/sunjammer]]. | For urgent requests, the list of systems administrators is on [[Machine/sunjammer]]. | ||
== | == Prerequisites == | ||
A shell account; | |||
* requires a sponsor, | |||
* is only available to core contributors, | |||
* is only for when an existing public service such as GitHub cannot help. | |||
A shell account makes sense only if you're '''already''' comfortable using ssh and the Linux command line. The SL systems administrators are not tutors. | |||
== Requesting a shell account == | |||
Fill up the following template and send it by email to '''sysadmin''' @ '''sugarlabs''' . '''org''': | |||
Username: <[a-z]+> | |||
First: <your first name(s)> | |||
Last: <your last name(s)> | |||
Email: <desired forwarding email destination for USERNAME@sugarlabs.org> | |||
Sponsor(s): <names of people sponsoring your account request> | |||
<intended purpose of account> | |||
<public ssh key(s), one per line. don't attach, paste with word-wrapping disabled> | |||
* Please cc your sponsor(s) | |||
* Preferably sign your request with a GPG key uploaded to public keyservers and signed by at least another Sugar Labs member. | |||
* Accurately describe the intended purpose of your shell account. '''Insufficiently justified requests will be delayed by the sysadmins to request further details.''' | |||
== Usage notes == | |||
=== Password Management === | === Password Management === | ||
| Line 48: | Line 75: | ||
Do not distribute non-free software from your account, as this is not allowed by the terms of service of our host, the [http://www.fsf.org/ Free Software Foundation]. | Do not distribute non-free software from your account, as this is not allowed by the terms of service of our host, the [http://www.fsf.org/ Free Software Foundation]. | ||
<!-- | |||
I believe git, openID and IRC proxies are all deprecated -- Devin | |||
=== Public git hosting === | === Public git hosting === | ||
| Line 57: | Line 86: | ||
* Ensure that the path to your repository is publicly readable. | * Ensure that the path to your repository is publicly readable. | ||
* Touch the file <code>git-daemon-export-ok</code> in the repository. | * Touch the file <code>git-daemon-export-ok</code> in the repository. | ||
=== OpenID === | === OpenID === | ||
| Line 68: | Line 96: | ||
You can run your favorite IRC client or proxy on your account. We also offer a system-wide [[Sysadmin/IRC_Proxy|IRC Proxy]]. | You can run your favorite IRC client or proxy on your account. We also offer a system-wide [[Sysadmin/IRC_Proxy|IRC Proxy]]. | ||
--> | |||
== See Also == | == See Also == | ||
| Line 74: | Line 102: | ||
* [[Service/Account]] (for users) | * [[Service/Account]] (for users) | ||
* [[Sysadmin/User_management]] (for sysadmins) | * [[Sysadmin/User_management]] (for sysadmins) | ||
* [[Service/email]] | |||
* [[Service/imap]] | * [[Service/imap]] | ||
* [[Service/smtp]] | * [[Service/smtp]] | ||
[[Category:Service|shell]] | [[Category:Service|shell]] | ||
Latest revision as of 13:09, 30 January 2025
If you don't have a Sugar Labs account, visit Service/Account first.
Hostnames
Hosted on
Administrative contact
sysadmin AT sugarlabs DOT org
For non-emergency calls, preferably send email to the administrative contact. For urgent requests, the list of systems administrators is on Machine/sunjammer.
Prerequisites
A shell account;
- requires a sponsor,
- is only available to core contributors,
- is only for when an existing public service such as GitHub cannot help.
A shell account makes sense only if you're already comfortable using ssh and the Linux command line. The SL systems administrators are not tutors.
Requesting a shell account
Fill up the following template and send it by email to sysadmin @ sugarlabs . org:
Username: <[a-z]+> First: <your first name(s)> Last: <your last name(s)> Email: <desired forwarding email destination for USERNAME@sugarlabs.org> Sponsor(s): <names of people sponsoring your account request> <intended purpose of account> <public ssh key(s), one per line. don't attach, paste with word-wrapping disabled>
- Please cc your sponsor(s)
- Preferably sign your request with a GPG key uploaded to public keyservers and signed by at least another Sugar Labs member.
- Accurately describe the intended purpose of your shell account. Insufficiently justified requests will be delayed by the sysadmins to request further details.
Usage notes
Password Management
To change your password, you can visit https://ldap.sugarlabs.org/passwd . To reset your password, send a GPG-signed request to the sysadmin contact.
Passwords expire every 6 months. You will receive an email remainder a few days in advance. If you don't update your password, your account will be disabled, including shell access via ssh public keys.
To conserve resources, shell accounts will be removed from the system after 6 months of inactivity.
Local email management
Instead of forwarding email to another account, you could use IMAP or our webmail. See Service/imap and Service/smtp.
Public web hosting
The contents of ~/public_html will be visible as http://people.sugarlabs.org/USERNAME
and http://people.sugarlabs.org/~USERNAME .
You can use PHP in your web pages. It will execute with your credentials.
Do not distribute non-free software from your account, as this is not allowed by the terms of service of our host, the Free Software Foundation.
See Also
- Service/Account (for users)
- Sysadmin/User_management (for sysadmins)
- Service/email
- Service/imap
- Service/smtp