Sugar Labs - User contributions [en]

Service/smtp

2026-02-24T07:31:59Z

Chimosky: switch to sunjammer.sl.o as I changed the cert because of mta-sts

== Hostnames ==

{|class=wikitable
! hostname !! service !! port !! function
|-
| sunjammer.sugarlabs.org || smtp || 25 || Local delivery (plain SMTP)
|-
| sunjammer.sugarlabs.org || [http://www.faqs.org/rfcs/rfc2476.html submission] || 587 || SMTP with STARTTLS, legacy
|-
| sunjammer.sugarlabs.org || [https://tools.ietf.org/html/rfc6409 submissions] || 465 || Email relay (SMTP with SSL, password authentication required)
|}

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

* postmaster AT sugarlabs DOT org

== Sysadmins ==

* [[User:Bernie|Bernie Innocenti]]
* (add yourself here if you tend to the postmaster [[Machine/rt|RT]] queue)

== Notes ==

* Users with a Sugar Labs [[Service/shell|shell account]] on [[Machine/sunjammer|sunjammer]] can use our SMTP relay for personal email submission. ''Any abuse will be prosecuted.''

* The [https://tools.ietf.org/html/rfc6409 submissions] port (465) is preferred for email relay. Unauthenticated and unencrypted connections are not allowed to relay.

* All email originating from the sugarlabs.org domain must be submitted through our SMTP server. '''Failure to do so may result in your email being blocked by spam filters.'''

== SPF ==

Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] records.

You can add an spf record in the zone file in the form

hostname TXT "v=spf1 redirect=_spf.hostname.sugarlabs.org"
_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/mask a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"

The '''a''' and '''mx''' values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined
for hostname.

Also maintain spacing and formatting for each section you add in the zone file.

== DKIM ==

Our domain publishes a [http://en.wikipedia.org/wiki/DKIM DKIM] key.

To test DKIM, send an email to autorespond+dkim@dk.elandsys.com

To generate an ed25519 key to use for DKIM, you can use openssl

# Generate ed25519 key
$ openssl genpkey -algorithm ed25519 -out dkim_private.pem
# Generate public key from private key
$ openssl pkey -in dkim_private.pem -pubout -out dkim_public.pem

For ed25519 keys, the p value in the DKIM record must only contain the BASE64 encoded public key, without an ASN.1 structure

$ openssl asn1parse -in dkim_public.pem -offset 12 -noout -out /dev/stdout | openssl base64
VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo=

Your entry would look like this

selector1._domainkey.hostname TXT "v=DKIM1; g=*; k=ed25519; p=VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo="
_adsp._domainkey.hostname TXT "dkim=unknown"

When using an ed25519 key, you'll need to add a fallback RSA key for backward compatibility.

# Generate rsa key
$ openssl genrsa -out rsa_private.key 2048
# Generate public key from private key
$ openssl rsa -in rsa_private.key -pubout -outform der 2>/dev/null | openssl base64 -A

You can then add a KeyTable and SigningTable to your opendkim.conf

KeyTable refile:/etc/opendkim/KeyTable
SigningTable refile:/etc/opendkim/SigningTable

# Contents of KeyTable with both keys
selector1._domainkey.hostname.sugarlabs.org hostname.domain-name:selector1:/path/to/selector1/private/*.key
selector2._domainkey.hostname.sugarlabs.org hostname.domain-name:selector2:/path/to/selector2/private/*.key

# Contents of SigningTable
*@hostname.domain-name selector1._domainkey.hostname.sugarlabs.org
*@hostname.domain-name selector2._domainkey.hostname.sugarlabs.org

Then add a DKIM record for the second selector

w-mail._domainkey.weblate IN TXT ("v=DKIM1; h=sha256; k=rsa; p="*")

The value of p is the public key of the generated RSA key above.

Ensure your private keys are on hostname.

== Set up ==

=== Thunderbird ===

These are the settings for setting up SMTP with Thunderbird. Note that you use your LDAP username and password, and that the username __'''does not'''__ have "@sugarlabs.org" at the end.

{|class=wikitable
! Server name !! Port !! Connection security !! Authentication method !! User name
|-
| smtp.sugarlabs.org || 587 || STARTTLS || Normal Password || your LDAP username -- AND WITHOUT @SUGARLABS.ORG AT THE END!
|}

Example:

[[File:Screenshot from 2024-06-13 22-45-20.png|thumb|left|example of smtp set up in thunderbird ]]

== See also ==

* [[Service/imap]]
* [[Service/webmail]]
* [[Service/email]]

[[Category:Service|imap]]

Service/lists

2026-02-04T22:44:30Z

Chimosky: Undo mistake.

== Hostnames ==

* https://lists.sugarlabs.org/

== Hosted on ==

[[Machine/bender]]

== Administrative contact ==

* For problems concerning a specific mailing-list, please contact the individual administrator reported on in the mailing-list summary page
* Technical contact for Mailman and general sugarlabs.org email routing: '''postmaster AT sugarlabs DOT org'''

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact above.

* [[User:bernie|Bernie Innocenti]]
* [[User:Chimosky|Chihurumnaya Ibiam]]

== Requesting a new mailing list ==

The best way to start a new mailing list is to begin a discussion on a related list that already exists,
and once the discussion becomes active, to ask for a separate list for that topic or that sort of traffic.

When you have a critical mass of people regularly talking about the same topic, request a mailing list by
emailing the following information to the administrative contact:

# The name you want for your mailing list, with alternative names if the first one is taken
# A description of the list, its purpose, and why it's needed (being able to say "we've been talking on this other list for a while, and the discussion has grown too big - see these archive links" is helpful)
# The name/email of the list admin, and of at least one other moderator (minimum one admin and one moderator)
# At least 10 names/emails of people who want to be the initial subscribers

It may take up to 48h to hear a response back, so please be patient!
== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|mailman}}
|-

|-
!scope="row" | Home
|{{Code|/opt/mailman}}
|-
!scope="row" | Daemon
|
{{Code|/etc/systemd/system/mailman3.service}} 
{{Code|/etc/systemd/system/mailmanweb.service}} 
{{Code|/etc/systemd/system/uwsgi.service}} 
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|/opt/mailman/web/logs/*}} 
{{Code|/opt/mailman/mm/var/logs/*}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-available/mailman.sugarlabs.org}} 
{{Code|/etc/mailman3/*}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|ss -tnlp}} View service ports 
|-
!scope="row" | Admin scripts
|
{{Code|/opt/mailman/mm/bin/}} 
|-

|}

== Sysadmin Recipes ==

=== Adding a new a mailing list ===

* Login to mailman user.

* Create the list:

python3 create-list.py --list LISTNAME

Mailman3 has separate parts and the core communicates with a [https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html REST API],
the script is aimed to make it easier to create a list, and can be viewed
to see how to authenticate to the API.

* Send additional instructions to list administrator

I created the new list LISTNAME@lists.sugarlabs.org.

You are the list admin, and should have received a welcome message
with your admin password. You can share this role with others, if
you wish, or nominate one or more moderators.

Feel free to make any configuration changes you need. In particular,
you may want to add a meaningful summary and description of what this
list is about. Please, notify systems@ if you change security or privacy
related settings.

After making changes to any config, restart all three services as django has quite the
persistent cache.

You can make any changes you need to make to any list using the mailmanclient, see [https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclient/docs/using.html mailmanclient] for more info.

== See Also ==

* [[Mailing_Lists]]

[[Category:Service|zzz]]

Service/lists

2026-02-04T22:43:01Z

Chimosky: Add mailmanclient doc.

=== Adding a new a mailing list ===

* Login to mailman user.

* Create the list:

python3 create-list.py --list LISTNAME

Mailman3 has separate parts and the core communicates with a [https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html REST API],
the script is aimed to make it easier to create a list, and can be viewed
to see how to authenticate to the API.

* Send additional instructions to list administrator

I created the new list LISTNAME@lists.sugarlabs.org.

You are the list admin, and should have received a welcome message
with your admin password. You can share this role with others, if
you wish, or nominate one or more moderators.

Feel free to make any configuration changes you need. In particular,
you may want to add a meaningful summary and description of what this
list is about. Please, notify systems@ if you change security or privacy
related settings.

After making changes to any config, restart all three services as django has quite the
persistent cache.

You can make any changes you need to make to any list using the mailmanclient, see [https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclient/docs/using.html mailmanclient] for more info.

Service/lists

2026-01-31T21:38:45Z

Chimosky: Remove mailman hostname as it no longer exists.

== Hostnames ==

* https://lists.sugarlabs.org/

== Hosted on ==

[[Machine/bender]]

== Administrative contact ==

* For problems concerning a specific mailing-list, please contact the individual administrator reported on in the mailing-list summary page
* Technical contact for Mailman and general sugarlabs.org email routing: '''postmaster AT sugarlabs DOT org'''

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact above.

* [[User:bernie|Bernie Innocenti]]
* [[User:Chimosky|Chihurumnaya Ibiam]]

== Requesting a new mailing list ==

The best way to start a new mailing list is to begin a discussion on a related list that already exists,
and once the discussion becomes active, to ask for a separate list for that topic or that sort of traffic.

When you have a critical mass of people regularly talking about the same topic, request a mailing list by
emailing the following information to the administrative contact:

# The name you want for your mailing list, with alternative names if the first one is taken
# A description of the list, its purpose, and why it's needed (being able to say "we've been talking on this other list for a while, and the discussion has grown too big - see these archive links" is helpful)
# The name/email of the list admin, and of at least one other moderator (minimum one admin and one moderator)
# At least 10 names/emails of people who want to be the initial subscribers

It may take up to 48h to hear a response back, so please be patient!
== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|mailman}}
|-

|-
!scope="row" | Home
|{{Code|/opt/mailman}}
|-
!scope="row" | Daemon
|
{{Code|/etc/systemd/system/mailman3.service}} 
{{Code|/etc/systemd/system/mailmanweb.service}} 
{{Code|/etc/systemd/system/uwsgi.service}} 
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|/opt/mailman/web/logs/*}} 
{{Code|/opt/mailman/mm/var/logs/*}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-available/mailman.sugarlabs.org}} 
{{Code|/etc/mailman3/*}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|ss -tnlp}} View service ports 
|-
!scope="row" | Admin scripts
|
{{Code|/opt/mailman/mm/bin/}} 
|-

|}

== Sysadmin Recipes ==

=== Adding a new a mailing list ===

* Login to mailman user.

* Create the list:

python3 create-list.py --list LISTNAME

Mailman3 has separate parts and the core communicates with a [https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html REST API],
the script is aimed to make it easier to create a list, and can be viewed
to see how to authenticate to the API.

* Send additional instructions to list administrator

I created the new list LISTNAME@lists.sugarlabs.org.

You are the list admin, and should have received a welcome message
with your admin password. You can share this role with others, if
you wish, or nominate one or more moderators.

Feel free to make any configuration changes you need. In particular,
you may want to add a meaningful summary and description of what this
list is about. Please, notify systems@ if you change security or privacy
related settings.

After making changes to any config, restart all three services as django has quite the
persistent cache.

== See Also ==

* [[Mailing_Lists]]

[[Category:Service|zzz]]

Service/lists

2026-01-24T01:12:57Z

Chimosky: Note for config changes.

== Hostnames ==

* https://lists.sugarlabs.org/
* https://mailman.sugarlabs.org/

== Hosted on ==

[[Machine/bender]]

== Administrative contact ==

* For problems concerning a specific mailing-list, please contact the individual administrator reported on in the mailing-list summary page
* Technical contact for Mailman and general sugarlabs.org email routing: '''postmaster AT sugarlabs DOT org'''

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact above.

* [[User:bernie|Bernie Innocenti]]
* [[User:Chimosky|Chihurumnaya Ibiam]]

== Requesting a new mailing list ==

The best way to start a new mailing list is to begin a discussion on a related list that already exists,
and once the discussion becomes active, to ask for a separate list for that topic or that sort of traffic.

When you have a critical mass of people regularly talking about the same topic, request a mailing list by
emailing the following information to the administrative contact:

# The name you want for your mailing list, with alternative names if the first one is taken
# A description of the list, its purpose, and why it's needed (being able to say "we've been talking on this other list for a while, and the discussion has grown too big - see these archive links" is helpful)
# The name/email of the list admin, and of at least one other moderator (minimum one admin and one moderator)
# At least 10 names/emails of people who want to be the initial subscribers

It may take up to 48h to hear a response back, so please be patient!
== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|mailman}}
|-

|-
!scope="row" | Home
|{{Code|/opt/mailman}}
|-
!scope="row" | Daemon
|
{{Code|/etc/systemd/system/mailman3.service}} 
{{Code|/etc/systemd/system/mailmanweb.service}} 
{{Code|/etc/systemd/system/uwsgi.service}} 
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|/opt/mailman/web/logs/*}} 
{{Code|/opt/mailman/mm/var/logs/*}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-available/mailman.sugarlabs.org}} 
{{Code|/etc/mailman3/*}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|ss -tnlp}} View service ports 
|-
!scope="row" | Admin scripts
|
{{Code|/opt/mailman/mm/bin/}} 
|-

|}

== Sysadmin Recipes ==

=== Adding a new a mailing list ===

* Login to mailman user.

* Create the list:

python3 create-list.py --list LISTNAME

Mailman3 has separate parts and the core communicates with a [https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html REST API],
the script is aimed to make it easier to create a list, and can be viewed
to see how to authenticate to the API.

* Send additional instructions to list administrator

I created the new list LISTNAME@lists.sugarlabs.org.

You are the list admin, and should have received a welcome message
with your admin password. You can share this role with others, if
you wish, or nominate one or more moderators.

Feel free to make any configuration changes you need. In particular,
you may want to add a meaningful summary and description of what this
list is about. Please, notify systems@ if you change security or privacy
related settings.

After making changes to any config, restart all three services as django has quite the
persistent cache.

== See Also ==

* [[Mailing_Lists]]

[[Category:Service|zzz]]

Service/lists

2026-01-24T01:08:50Z

Chimosky:

== Hostnames ==

* https://lists.sugarlabs.org/
* https://mailman.sugarlabs.org/

== Hosted on ==

[[Machine/bender]]

== Administrative contact ==

* For problems concerning a specific mailing-list, please contact the individual administrator reported on in the mailing-list summary page
* Technical contact for Mailman and general sugarlabs.org email routing: '''postmaster AT sugarlabs DOT org'''

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact above.

* [[User:bernie|Bernie Innocenti]]
* [[User:Chimosky|Chihurumnaya Ibiam]]

== Requesting a new mailing list ==

The best way to start a new mailing list is to begin a discussion on a related list that already exists,
and once the discussion becomes active, to ask for a separate list for that topic or that sort of traffic.

When you have a critical mass of people regularly talking about the same topic, request a mailing list by
emailing the following information to the administrative contact:

# The name you want for your mailing list, with alternative names if the first one is taken
# A description of the list, its purpose, and why it's needed (being able to say "we've been talking on this other list for a while, and the discussion has grown too big - see these archive links" is helpful)
# The name/email of the list admin, and of at least one other moderator (minimum one admin and one moderator)
# At least 10 names/emails of people who want to be the initial subscribers

It may take up to 48h to hear a response back, so please be patient!
== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|mailman}}
|-

|-
!scope="row" | Home
|{{Code|/opt/mailman}}
|-
!scope="row" | Daemon
|
{{Code|/etc/systemd/system/mailman3.service}} 
{{Code|/etc/systemd/system/mailmanweb.service}} 
{{Code|/etc/systemd/system/uwsgi.service}} 
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|/opt/mailman/web/logs/*}} 
{{Code|/opt/mailman/mm/var/logs/*}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-available/mailman.sugarlabs.org}} 
{{Code|/etc/mailman3/*}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|ss -tnlp}} View service ports 
|-
!scope="row" | Admin scripts
|
{{Code|/opt/mailman/mm/bin/}} 
|-

|}

== Sysadmin Recipes ==

=== Adding a new a mailing list ===

* Login to mailman user.

* Create the list:

python3 create-list.py --list LISTNAME

Mailman3 has separate parts and the core communicates with a [https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html REST API],
the script is aimed to make it easier to create a list, and can be viewed
to see how to authenticate to the API.

* Send additional instructions to list administrator

I created the new list LISTNAME@lists.sugarlabs.org.

You are the list admin, and should have received a welcome message
with your admin password. You can share this role with others, if
you wish, or nominate one or more moderators.

Feel free to make any configuration changes you need. In particular,
you may want to add a meaningful summary and description of what this
list is about. Please, notify systems@ if you change security or privacy
related settings.

== See Also ==

* [[Mailing_Lists]]

[[Category:Service|zzz]]

Service/lists

2026-01-24T01:07:27Z

Chimosky: Add mailman hostname and change machine.

== Hostnames ==

* https://lists.sugarlabs.org/
* https://mailman.sugarlabs.org/

== Hosted on ==

[[Machine/bender]]

== Administrative contact ==

* For problems concerning a specific mailing-list, please contact the individual administrator reported on in the mailing-list summary page
* Technical contact for Mailman and general sugarlabs.org email routing: '''postmaster AT sugarlabs DOT org'''

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact above.

* [[User:bernie|Bernie Innocenti]]
* [[User:Chimosky|Chihurumnaya Ibiam]]

== Requesting a new mailing list ==

The best way to start a new mailing list is to begin a discussion on a related list that already exists,
and once the discussion becomes active, to ask for a separate list for that topic or that sort of traffic.

When you have a critical mass of people regularly talking about the same topic, request a mailing list by
emailing the following information to the administrative contact:

# The name you want for your mailing list, with alternative names if the first one is taken
# A description of the list, its purpose, and why it's needed (being able to say "we've been talking on this other list for a while, and the discussion has grown too big - see these archive links" is helpful)
# The name/email of the list admin, and of at least one other moderator (minimum one admin and one moderator)
# At least 10 names/emails of people who want to be the initial subscribers

It may take up to 48h to hear a response back, so please be patient!
== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|mailman}}
|-

|-
!scope="row" | Home
|{{Code|/opt/mailman}}
|-
!scope="row" | Daemon
|
{{Code|/etc/systemd/system/mailman3.service}} 
{{Code|/etc/systemd/system/mailmanweb.service}} 
{{Code|/etc/systemd/system/uwsgi.service}} 
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|/opt/mailman/web/logs/*}} 
{{Code|/opt/mailman/mm/var/logs/*}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-available/mailman.sugarlabs.org}} 
{{Code|/etc/mailman3/*}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|ss -tnlp}} View service ports 
|-
!scope="row" | Admin scripts
|
{{Code|/opt/mailman/mm/bin/}} 
|-

|}

== Sysadmin Recipes ==

=== Adding a new a mailing list ===

* Login to mailman user.

* Create the list:

python3 create-list.py --list LISTNAME

Mailman3 has separate parts and the core communicates with a [https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html REST API],
the script is aimed to make it easier to create a list, and can be viewed
to see how to authenticate to the API.

* Send additional instructions to list administrator

I created the new list LISTNAME@lists.sugarlabs.org.

You are the list admin, and should have received a welcome message
with your admin password. You can share this role with others, if
you wish, or nominate one or more moderators.

Feel free to make any configuration changes you need. In particular,
you may want to add a meaningful summary and description of what this
list is about. Please, notify systems@ if you change security or privacy
related settings.

== See Also ==

* [[Mailing_Lists]]

[[Category:Service|zzz]]

Service/lists

2026-01-24T01:04:38Z

Chimosky: Change information to reflect move to mailman3.

== Hostnames ==

* https://lists.sugarlabs.org/

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

* For problems concerning a specific mailing-list, please contact the individual administrator reported on in the mailing-list summary page
* Technical contact for Mailman and general sugarlabs.org email routing: '''postmaster AT sugarlabs DOT org'''

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact above.

* [[User:bernie|Bernie Innocenti]]
* [[User:Chimosky|Chihurumnaya Ibiam]]

== Requesting a new mailing list ==

The best way to start a new mailing list is to begin a discussion on a related list that already exists,
and once the discussion becomes active, to ask for a separate list for that topic or that sort of traffic.

When you have a critical mass of people regularly talking about the same topic, request a mailing list by
emailing the following information to the administrative contact:

# The name you want for your mailing list, with alternative names if the first one is taken
# A description of the list, its purpose, and why it's needed (being able to say "we've been talking on this other list for a while, and the discussion has grown too big - see these archive links" is helpful)
# The name/email of the list admin, and of at least one other moderator (minimum one admin and one moderator)
# At least 10 names/emails of people who want to be the initial subscribers

It may take up to 48h to hear a response back, so please be patient!
== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|mailman}}
|-

|-
!scope="row" | Home
|{{Code|/opt/mailman}}
|-
!scope="row" | Daemon
|
{{Code|/etc/systemd/system/mailman3.service}} 
{{Code|/etc/systemd/system/mailmanweb.service}} 
{{Code|/etc/systemd/system/uwsgi.service}} 
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|/opt/mailman/web/logs/*}} 
{{Code|/opt/mailman/mm/var/logs/*}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-available/mailman.sugarlabs.org}} 
{{Code|/etc/mailman3/*}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|ss -tnlp}} View service ports 
|-
!scope="row" | Admin scripts
|
{{Code|/opt/mailman/mm/bin/}} 
|-

|}

== Sysadmin Recipes ==

=== Adding a new a mailing list ===

* Login to mailman user.

* Create the list:

python3 create-list.py --list LISTNAME

Mailman3 has separate parts and the core communicates with a [https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html REST API],
the script is aimed to make it easier to create a list, and can be viewed
to see how to authenticate to the API.

* Send additional instructions to list administrator

I created the new list LISTNAME@lists.sugarlabs.org.

You are the list admin, and should have received a welcome message
with your admin password. You can share this role with others, if
you wish, or nominate one or more moderators.

Feel free to make any configuration changes you need. In particular,
you may want to add a meaningful summary and description of what this
list is about. Please, notify systems@ if you change security or privacy
related settings.

== See Also ==

* [[Mailing_Lists]]

[[Category:Service|zzz]]

Machine/bender

2025-06-03T17:49:04Z

Chimosky: /* Machines */

== Info ==
Bender and [[Machine/papert | Papert]] are two twin blade servers donated to Sugar Labs in 2021.

Bender is our primary KVM host, while Papert is a hot standby and [[Service/backup|backup]] machine.

== Hostnames ==
* bender.sugarlabs.org
* papert.sugarlabs.org

== Machines ==
* [[Machine/lightwave]], [[Service/Nameservers]],
* [[Machine/weblate]], with [[Service/Weblate]], or https://weblate.sugarlabs.org and https://translate.sugarlabs.org

== Hardware ==
* HPE ProLiant DL360 Gen10 1RU server
** Dual socket, current configuration has one CPU
* [https://ark.intel.com/content/www/us/en/ark/products/199342/intel-xeon-gold-5218r-processor-27-5m-cache-2-10-ghz.html Xeon Gold 5218R]
** 20 cores/40 threads
** 2.1GHz base frequency, 4.0GHz max turbo frequency
** 27.5MB of cache
* 64GB RAM
* 2TB NVMe SSD

[[Image:BenderRacked.jpg|thumb|320px]]

== Admins ==
* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Libera.chat IRC network
* [[User:Bernie|Bernie Innocenti]], @bernie:matrix.org on Sugar Systems

== Hosting ==

[[Image:SonicColo.jpg|thumb|320px]]

Hosted by Sonic in Santa Rosa CA

== Network configuration ==

Network configuration is managed via [https://netplan.io/ netplan]. To modify, do:

vi /etc/netplan/bender.yaml
netplan generate
netplan apply

=== IPv4 ===

Bender and Papert are globally accessible through a public, static IPv4 address

Sonic assigned a /28 network to Sugar Labs. IP assignments are managed in our DNS configuration. Search for "Sonic IP pool" in <code>masters/sugarlabs.org.zone</code>.

* Usable IPv4 addresses: 192.184.220.210 ~ 192.184.220.222 (13 addresses)
* Subnet Mask: 255.255.255.240
* Default Gateway: 192.184.220.209
* DNS: 8.8.8.8, 8.8.4.4

=== IPv6 ===
IPv6 configuration is a bit weird.

* Public block: 2001:5a8:601:f::/64
* Sonic gateway: 2001:5a8:5:3a::15:0/127
* Transport IP: 2001:5a8:5:3a::15:1/127

The gateway is configured to route all traffic for our netblock to the transport IP, which is currently assigned to bender.

=== Bridges ===
The br0 bridge is created at startup and shared with the virtual machines hosted on Bender. It gives the VMs unfiltered access to the external network. There's no DHCP, all machines must define a static IP configuration, taking care not to stomp onto each other.

There is also a virbr0 bridge created by libvirt on startup from <code>/etc/libvirt/qemu/networks/default.xml</code>. This is a NAT interface and is not meant for VMs directly serving on the Internet.

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Virtualization ==

Virtual machines are KVM guests managed with libvirt.

=== Storage ===

All virtual disks come from a pool backed by the main LVM VG:

virsh # pool-define-as nvme-pool logical --source-name nvme-pool
Pool nvme-pool defined

virsh # pool-start nvme-pool
Pool nvme-pool started

virsh # pool-autostart nvme-pool
Pool nvme-pool marked as autostarted

virsh # pool-info nvme-pool
Name: nvme-pool
UUID: 5812819f-b8bf-484e-98fb-2e100fe83df2
State: running
Persistent: yes
Autostart: yes
Capacity: 1.64 TiB
Allocation: 250.00 GiB
Available: 1.40 TiB

Disks assigned to VMs will appear here:

virsh # vol-list nvme-pool
Name Path
-----------------------------------------
aslo1-root /dev/nvme-pool/aslo1-root
aslo1-srv /dev/nvme-pool/aslo1-srv
backup /dev/nvme-pool/backup

Disks can be created, listed and deleted using the vol-* commands:

virsh # vol-create-as nvme-pool testvm-root 20G
Vol testvm-root created

virsh # vol-info testvm-root --pool nvme-pool
Name: testvm-root
Type: block
Capacity: 20.00 GiB
Allocation: 20.00 GiB

virsh # vol-delete testvm-root --pool nvme-pool
Vol testvm-root deleted

'''NOTE''': avoid allocating large VM volumes as image file within the host's root filesystem, as they're slow and hard to manage. It's ok to use images for test VMs.

Machine

2025-06-03T17:48:51Z

Chimosky: Add translate.sugarlabs.org domain name as it also points to weblate.

<noinclude>{{TeamHeader|Infrastructure Team}}</noinclude>

Computing hardware or virtual machines maintained by the Sugar Labs [[Infrastructure Team]].

== Physical ==

* [[Machine/justice]]
* [[Machine/freedom]]
* [[Machine/bender]]
* [[Machine/papert]]

== Virtual ==

* [[Machine/lightwave]], with [[Service/Nameservers]],
* [[Machine/pootle]], with [[Service/translate]], or https://translate.sugarlabs.org,
* [[Machine/aslo]], with [[Service/activities]] aslo, or https://activities.laptop.org,
* [[Machine/library]],
* [[Machine/aslo3]], with [[Service/activities3]] aslo-v3, https://github.com/sugarlabs/aslo-v3,
* [[Machine/jita]], with [[Service/git]], [[Service/jabber]], [[Service/meeting]], [[Service/obs]], [[Service/chat]], [[Service/cgit]], [[Service/blacklist]], [[Service/stats]],
* [[Machine/amnesia]],
* [[Machine/beacon]], 
* [[Machine/weblate]], with [[Service/Weblate]], or https://weblate.sugarlabs.org and https://translate.sugarlabs.org,
* [[Machine/containers]]

== Containers ==

* org.sugarlabs.bugs
* org.sugarlabs.developer-rebuilder
* org.sugarlabs.www-rebuilder
* org.sugarlabs.use-socialhelp
* org.sugarlabs.socialhelp_sso
* local_discourse/app
* org.turtleartday.www-rebuilder
* org.sugarlabs.help-rebuilder

== Student Listing ==

This list was made by a GCI 2018 student.

* [[Machine/backup]]
* [[Machine/bender]]
* [[Machine/freedom]]
* [[Machine/jita]]
* [[Machine/justice]]
* [[Machine/lightwave]]
* [[Machine/pootle]]
* [[Machine/schools]]
* [[Machine/schoolserver]]
* [[Machine/trinity]]

== Automatic Listing ==

This list is generated automatically from Wiki pages that have a prefix of "Machine". It may contain subpages of machines. It may contain machines that have been decommissioned; kept as historical data against future need.

{{Special:PrefixIndex/Machine/}}

[[Image:Sugarlabs systems.jpg|frame]]

Machine/justice

2025-06-03T17:48:09Z

Chimosky: Remove lightwave as it's no longer hosted on justice, also remove aslo4 as that's hosted on sunjammer.

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* justice.sugarlabs.org
* freedom.sugarlabs.org

== Info ==

Freedom and Justice are two twin KVM hosts bought by Sugar Labs in 2012.

Justice is currently our primary VM hosting box, while freedom is a hot-standby running some secondary services in docker containers and backups.

== Machines ==

The following machines services are hosted:

* [[Machine/pootle]], [[Service/translate]],
* [[Service/activities]] aslo,
* [[Machine/library]],
* [[Machine/jita]], [[Service/git]], [[Service/jabber]], [[Service/meeting]], [[Service/obs]], [[Service/chat]], [[Service/cgit]], [[Service/blacklist]], [[Service/stats]],

== Hardware ==
* 2U rack-mountable case
* Motherboard Supermicro H8SGL (or maybe H8SGL-F)
* 8-core Opteron 6212 @ 1.7GHz
* 64GB RAM
* 2x1TB RAID1

== Management ==
The two servers have SMT management cards from Supermicro with a seriously awful web interface:
* [http://justice-mng.sugarlabs.org/ justice-mng.sugarlabs.org]
* [http://freedom-mng.sugarlabs.org/ freedom-mng.sugarlas.org]
Of course you need a separate account. Full KVM support requires the Java browser plugin (yuck!), so we mostly use them for the big reset button in case a server hangs (it happened about once per year).

'''Use a long, unguessable password, but not one you're also using elsewhere! A few years ago, a backdoor was discovered in this firmware which would reveal all passwords in plaintext with a simple telnet! Also, login uses unencrypted http.'''

It's also possible to talk to the management card from Linux using ipmitool.

Both cards are running firmware version 3.16, which patched a huge backdoor that would trivially reveal all passwords in plaintext. No kidding. There's a [https://www.supermicro.com/support/resources/bios_ipmi.php?vendor=2&keywords=H8S newer firmware version], but attempts to update to it failed with both Chrome and Firefox (error: "413 - Request Entity Too Large"). I suspect a bug in their http POST implementation :-(

== Software ==
* Justice: Ubuntu 18.04 LTS Bionic
* Freedom: Ubuntu 18.04 LTS Bionic

== Location ==
Hosted by the [http://media.mit.edu/ MIT Media Lab] in server room E15-243.

== Admins ==
* [[User:MrBIOS|Alex Perez]], aperezbios on #sugar libera.chat
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar libera.chat
* [[User:Srevin03|Srevin Saju]], srevinsaju on #sugar on libera.chat

== Network configuration ==
Justice is globally accessible through public, static IPv4.
The IPv6 /64 subnet (6to4) is currently experimental and not associated with AAAA records.

== Hosted VMs ==
All KVM virtual machines are managed by libvirtd.

See [[Sysadmin/Add virtual machine]] for creating new VMs.

{{Special:PrefixIndex/{{PAGENAME}}/}}

Machine/bender

2025-06-03T17:46:05Z

Chimosky: Add translate.sugarlabs.org domain name as it also points to weblate.

== Info ==
Bender and [[Machine/papert | Papert]] are two twin blade servers donated to Sugar Labs in 2021.

Bender is our primary KVM host, while Papert is a hot standby and [[Service/backup|backup]] machine.

== Hostnames ==
* bender.sugarlabs.org
* papert.sugarlabs.org

== Machines ==
* [[Machine/lightwave]], [[Service/Nameservers]],
* [[Machine/weblate]], with [[Service/Weblate]], or https://weblate.sugarlabs.org, https://translate.sugarlabs.org

== Hardware ==
* HPE ProLiant DL360 Gen10 1RU server
** Dual socket, current configuration has one CPU
* [https://ark.intel.com/content/www/us/en/ark/products/199342/intel-xeon-gold-5218r-processor-27-5m-cache-2-10-ghz.html Xeon Gold 5218R]
** 20 cores/40 threads
** 2.1GHz base frequency, 4.0GHz max turbo frequency
** 27.5MB of cache
* 64GB RAM
* 2TB NVMe SSD

[[Image:BenderRacked.jpg|thumb|320px]]

== Admins ==
* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Libera.chat IRC network
* [[User:Bernie|Bernie Innocenti]], @bernie:matrix.org on Sugar Systems

== Hosting ==

[[Image:SonicColo.jpg|thumb|320px]]

Hosted by Sonic in Santa Rosa CA

== Network configuration ==

Network configuration is managed via [https://netplan.io/ netplan]. To modify, do:

vi /etc/netplan/bender.yaml
netplan generate
netplan apply

=== IPv4 ===

Bender and Papert are globally accessible through a public, static IPv4 address

Sonic assigned a /28 network to Sugar Labs. IP assignments are managed in our DNS configuration. Search for "Sonic IP pool" in <code>masters/sugarlabs.org.zone</code>.

* Usable IPv4 addresses: 192.184.220.210 ~ 192.184.220.222 (13 addresses)
* Subnet Mask: 255.255.255.240
* Default Gateway: 192.184.220.209
* DNS: 8.8.8.8, 8.8.4.4

=== IPv6 ===
IPv6 configuration is a bit weird.

* Public block: 2001:5a8:601:f::/64
* Sonic gateway: 2001:5a8:5:3a::15:0/127
* Transport IP: 2001:5a8:5:3a::15:1/127

The gateway is configured to route all traffic for our netblock to the transport IP, which is currently assigned to bender.

=== Bridges ===
The br0 bridge is created at startup and shared with the virtual machines hosted on Bender. It gives the VMs unfiltered access to the external network. There's no DHCP, all machines must define a static IP configuration, taking care not to stomp onto each other.

There is also a virbr0 bridge created by libvirt on startup from <code>/etc/libvirt/qemu/networks/default.xml</code>. This is a NAT interface and is not meant for VMs directly serving on the Internet.

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Virtualization ==

Virtual machines are KVM guests managed with libvirt.

=== Storage ===

All virtual disks come from a pool backed by the main LVM VG:

virsh # pool-define-as nvme-pool logical --source-name nvme-pool
Pool nvme-pool defined

virsh # pool-start nvme-pool
Pool nvme-pool started

virsh # pool-autostart nvme-pool
Pool nvme-pool marked as autostarted

virsh # pool-info nvme-pool
Name: nvme-pool
UUID: 5812819f-b8bf-484e-98fb-2e100fe83df2
State: running
Persistent: yes
Autostart: yes
Capacity: 1.64 TiB
Allocation: 250.00 GiB
Available: 1.40 TiB

Disks assigned to VMs will appear here:

virsh # vol-list nvme-pool
Name Path
-----------------------------------------
aslo1-root /dev/nvme-pool/aslo1-root
aslo1-srv /dev/nvme-pool/aslo1-srv
backup /dev/nvme-pool/backup

Disks can be created, listed and deleted using the vol-* commands:

virsh # vol-create-as nvme-pool testvm-root 20G
Vol testvm-root created

virsh # vol-info testvm-root --pool nvme-pool
Name: testvm-root
Type: block
Capacity: 20.00 GiB
Allocation: 20.00 GiB

virsh # vol-delete testvm-root --pool nvme-pool
Vol testvm-root deleted

'''NOTE''': avoid allocating large VM volumes as image file within the host's root filesystem, as they're slow and hard to manage. It's ok to use images for test VMs.

Machine/bender

2025-06-03T17:43:32Z

Chimosky: Add machines hosted on weblate.

== Info ==
Bender and [[Machine/papert | Papert]] are two twin blade servers donated to Sugar Labs in 2021.

Bender is our primary KVM host, while Papert is a hot standby and [[Service/backup|backup]] machine.

== Hostnames ==
* bender.sugarlabs.org
* papert.sugarlabs.org

== Machines ==
* [[Machine/lightwave]], [[Service/Nameservers]],
* [[Machine/weblate]], with [[Service/Weblate]], or https://weblate.sugarlabs.org

== Hardware ==
* HPE ProLiant DL360 Gen10 1RU server
** Dual socket, current configuration has one CPU
* [https://ark.intel.com/content/www/us/en/ark/products/199342/intel-xeon-gold-5218r-processor-27-5m-cache-2-10-ghz.html Xeon Gold 5218R]
** 20 cores/40 threads
** 2.1GHz base frequency, 4.0GHz max turbo frequency
** 27.5MB of cache
* 64GB RAM
* 2TB NVMe SSD

[[Image:BenderRacked.jpg|thumb|320px]]

== Admins ==
* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Libera.chat IRC network
* [[User:Bernie|Bernie Innocenti]], @bernie:matrix.org on Sugar Systems

== Hosting ==

[[Image:SonicColo.jpg|thumb|320px]]

Hosted by Sonic in Santa Rosa CA

== Network configuration ==

Network configuration is managed via [https://netplan.io/ netplan]. To modify, do:

vi /etc/netplan/bender.yaml
netplan generate
netplan apply

=== IPv4 ===

Bender and Papert are globally accessible through a public, static IPv4 address

Sonic assigned a /28 network to Sugar Labs. IP assignments are managed in our DNS configuration. Search for "Sonic IP pool" in <code>masters/sugarlabs.org.zone</code>.

* Usable IPv4 addresses: 192.184.220.210 ~ 192.184.220.222 (13 addresses)
* Subnet Mask: 255.255.255.240
* Default Gateway: 192.184.220.209
* DNS: 8.8.8.8, 8.8.4.4

=== IPv6 ===
IPv6 configuration is a bit weird.

* Public block: 2001:5a8:601:f::/64
* Sonic gateway: 2001:5a8:5:3a::15:0/127
* Transport IP: 2001:5a8:5:3a::15:1/127

The gateway is configured to route all traffic for our netblock to the transport IP, which is currently assigned to bender.

=== Bridges ===
The br0 bridge is created at startup and shared with the virtual machines hosted on Bender. It gives the VMs unfiltered access to the external network. There's no DHCP, all machines must define a static IP configuration, taking care not to stomp onto each other.

There is also a virbr0 bridge created by libvirt on startup from <code>/etc/libvirt/qemu/networks/default.xml</code>. This is a NAT interface and is not meant for VMs directly serving on the Internet.

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Virtualization ==

Virtual machines are KVM guests managed with libvirt.

=== Storage ===

All virtual disks come from a pool backed by the main LVM VG:

virsh # pool-define-as nvme-pool logical --source-name nvme-pool
Pool nvme-pool defined

virsh # pool-start nvme-pool
Pool nvme-pool started

virsh # pool-autostart nvme-pool
Pool nvme-pool marked as autostarted

virsh # pool-info nvme-pool
Name: nvme-pool
UUID: 5812819f-b8bf-484e-98fb-2e100fe83df2
State: running
Persistent: yes
Autostart: yes
Capacity: 1.64 TiB
Allocation: 250.00 GiB
Available: 1.40 TiB

Disks assigned to VMs will appear here:

virsh # vol-list nvme-pool
Name Path
-----------------------------------------
aslo1-root /dev/nvme-pool/aslo1-root
aslo1-srv /dev/nvme-pool/aslo1-srv
backup /dev/nvme-pool/backup

Disks can be created, listed and deleted using the vol-* commands:

virsh # vol-create-as nvme-pool testvm-root 20G
Vol testvm-root created

virsh # vol-info testvm-root --pool nvme-pool
Name: testvm-root
Type: block
Capacity: 20.00 GiB
Allocation: 20.00 GiB

virsh # vol-delete testvm-root --pool nvme-pool
Vol testvm-root deleted

'''NOTE''': avoid allocating large VM volumes as image file within the host's root filesystem, as they're slow and hard to manage. It's ok to use images for test VMs.

User:Chimosky

2025-06-01T16:45:25Z

Chimosky: Testing update 2

== Ibiam Chihurumnaya ==
My name is Ibiam Chihurumnaya, I'm from Nigeria. You can contact me on

*Email ibiamchihurumnaya AT sugarlabs DOT org
*[https://github.com/chimosky Github ]

User:Chimosky

2025-06-01T16:44:52Z

Chimosky: Test for update

== Ibiam Chihurumnaya ==
My name is Ibiam Chihurumnaya, I'm from Nigeria. You can contact me

*Email ibiamchihurumnaya AT sugarlabs DOT org
*[https://github.com/chimosky Github ]

Oversight Board/2025-2026-candidates

2024-11-25T13:36:36Z

Chimosky:

==Election==

There are to be three (3) [https://www.sugarlabs.org/leadership/ Board of Director] seats to be elected for the 2025-2026 period, currently held by Lionel Laské and Alex Perez, as well as one empty seat.

==Calendar==

{| class="wikitable"
|Stage I
|November 8
|Announcement of election date and first call for candidates.
|-
|Stage II
|~~November 22~~ November 24 ([https://www.sugarlabs.org/community/2024/11/22/elections-extension/ extension])
|Deadline to receive [[#Candidates|candidacy applications]] and candidate bios; and deadline to receive [https://forms.gle/48F6h5wdV6BpSro66 ballot applications].
|-
|Stage III
|November 27
|Ballots to be sent by email; If you do not receive your ballot by the following day, please email elections@sugarlabs.org
|-
|Stage IV
|December 13
|Deadline to vote
|-
|Stage V
|December 19
|Election results announced
|}

==Candidates==

Candidates should create a Wiki entry at [[/Candidate Name|Candidates' Wiki submissions]], one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.

Candidates should read and understand the terms of the [[Sugar_Labs/Governance|Sugar Labs Inc.'s Bylaws]], as well as any domestic and international laws governing participation in a US-based 501(c)(3) nonprofit board.

{{Special:PrefixIndex/Oversight_Board/2025-2026-candidates/}}

==References==

This election is being run by Devin Ulibarri, executive director for Sugar Labs. We welcome volunteers to assist in running our elections. Please email volunteering@sugarlabs.org if you are interested in volunteering.

Oversight Board/2025-2026-candidates

2024-11-18T13:51:52Z

Chimosky: Add prefix of candidates.

==Election==

There are to be three (3) [https://www.sugarlabs.org/leadership/ Board of Director] seats to be elected for the 2025-2026 period, currently held by Lionel Laské and Alex Perez, as well as one empty seat.

==Calendar==

{| class="wikitable"
|Stage I
|November 8
|Announcement of election date and first call for candidates.
|-
|Stage II
|November 22
|Deadline to receive [[#Candidates|candidacy applications]] and candidate bios; and deadline to receive [https://forms.gle/48F6h5wdV6BpSro66 ballot applications].
|-
|Stage III
|November 27
|Ballots to be sent by email; If you do not receive your ballot by the following day, please email elections@sugarlabs.org
|-
|Stage IV
|December 13
|Deadline to vote
|-
|Stage V
|December 19
|Election results announced
|}

==Candidates==

Candidates should create a Wiki entry at [[/Candidate Name|Candidates' Wiki submissions]], one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.

Candidates should read and understand the terms of the [[Sugar_Labs/Governance|Sugar Labs Inc.'s Bylaws]], as well as any domestic and international laws governing participation in a US-based 501(c)(3) nonprofit board.

{{Special:PrefixIndex/Oversight_Board/2025-2026-candidates/}}

===Template Name of Candidate===

Template text from candidate, template text from candidate...

==References==

This election is being run by Devin Ulibarri, executive director for Sugar Labs. We welcome volunteers to assist in running our elections. Please email volunteering@sugarlabs.org if you are interested in volunteering.

Development Team/Source Code

2024-10-08T22:46:02Z

Chimosky: Remove unstable section.

{{TeamHeader|Development Team|home=Development Team Home|roadmap_link={{Upcoming Stable Release}}/Roadmap}}

{{Developers}}

If you want to package Sugar for your favourite distribution or just want to examine Sugar's lovely code ;) you can find all the source code of each module at the links below.

== Stable ==

* [[{{Current Stable Release}}|Sucrose {{Current Stable Release}}]]

{{:Development Team/Release/Modules}}
== Honey ==
:(Activities developed ''in the wild'')

:See [[Activities]].

== Dependencies ==

The Sugar interface is based on the GNOME and freedesktop software
stacks, using technologies like Gtk+, dbus, xorg,
matchbox-window-manager and gconf. It is written in Python, making it
easily extended. For the collaboration part, Sugar is using the
telepathy framework.

The activities depend on technologies like xulrunner for the browser,
abiword for the write activity and squeak for etoys.

* [http://www.gnome.org/ GNOME]
* [http://www.freedesktop.org/wiki/ freedesktop]
* [http://www.gtk.org/ Gtk+]
* [http://www.freedesktop.org/wiki/Software/dbus dbus]
* [http://www.x.org/wiki/Home X Windows System]
* <strike>[http://matchbox-project.org/ matchbox]</strike> [http://blogs.gnome.org/metacity metacity]
* [http://www.gnome.org/projects/gconf/ gconf]
* [http://telepathy.freedesktop.org/wiki/ telepathy]
* [http://developer.mozilla.org/en/XULRunner xulrunner]
* [http://www.abisource.com/ abiword]
* [http://www.squeak.org/ squeak]

[[Category:Developer]]
[[Category:Installing Sugar]]

Template:Current Stable Release

2024-10-08T22:44:48Z

Chimosky: Update latest release.

0.121<noinclude>

This template returns the current stable release number.
</noinclude>

0.121

2024-10-08T22:36:21Z

Chimosky:

== Notes ==

Sugar 0.121 is a new stable release of the Sugar Learning Platform. It was released on 5th February 2024. The original release announcement can be viewed at the [https://lists.sugarlabs.org/archive/sugar-devel/2024-February/059610.html sugar-devel mailing list archives].

== Downloads ==

* [https://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.121.tar.xz sugar-artwork-0.121.tar.xz]
* [https://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.121.tar.xz sugar-datastore-0.121.tar.xz]
* [https://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.121.tar.xz sugar-toolkit-gtk3-0.121.tar.xz]
* [https://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.121.tar.xz sugar-0.121.tar.xz]

== What's fixed ==

* Fix text clipping cannot be removed from frame. (Bhavya)
* Buddy.props.keys is no longer a quoted bytes. (Ibiam Chihurumnaya)
* Build warnings from gcc fixed in sugar-toolkit-gtk3. (Ibiam Chihurumnaya)
* DescriptionItem cursor now visible; makes it easier to edit text in the description box. (Ibiam Chihurumnaya)
* Port to WebKit2-4.1 API; support for WebKit2-4.0 API has been dropped. (Ibiam Chihurumnaya)
* Fix this web page could not be loaded in Browse and MiniBrowser (James Cameron)

0.121

2024-10-08T22:35:57Z

Chimosky: Created page with "== Notes == Sugar 0.121 is a new stable release of the Sugar Learning Platform. It was released on 5th February 2024. The original release announcement can be viewed at the [..."

== Notes ==

Sugar 0.121 is a new stable release of the Sugar Learning Platform. It was released on 5th February 2024. The original release announcement can be viewed at the [https://lists.sugarlabs.org/archive/sugar-devel/2024-February/059610.html sugar-devel mailing list archives].

== Downloads ==

* [https://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.121.tar.xz sugar-artwork-0.121.tar.xz]
* [https://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.121.tar.xz sugar-datastore-0.121.tar.xz]
* [https://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.121.tar.xz sugar-toolkit-gtk3-0.121.tar.xz]
* [https://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.121.tar.xz sugar-0.121.tar.xz]

== What's fixed ==

* Fix text clipping cannot be removed from frame (Bhavya)
* Buddy.props.keys is no longer a quoted bytes. (Ibiam Chihurumnaya)
* Build warnings from gcc fixed in sugar-toolkit-gtk3 (Ibiam Chihurumnaya)
* DescriptionItem cursor now visible; makes it easier to edit text in the description box. (Ibiam Chihurumnaya)
* Port to WebKit2-4.1 API; support for WebKit2-4.0 API has been dropped.(Ibiam Chihurumnaya)
* Fix this web page could not be loaded in Browse and MiniBrowser (James Cameron)

Service/Weblate

2024-10-04T16:45:53Z

Chimosky: Changes to adding translation component workflow

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to Git.
* Set source code repository link - using ssh -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Leave Push branch empty as repository branch would be used.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Git version control above, the hooks configured in the repos make it easy for weblate to pull changes from Github.

== Backups ==
Weblate currently backs up to papert using [https://docs.weblate.org/en/weblate-5.4.2/admin/backup.html#remote-backups borgbackup] at {{Code|'''/home/weblate/backups'''}}.

You can view the list of backups with {{Code|'''borg list /home/weblate/backups'''}} which will ask for a passphrase,
the passphrase can be found in weblate admin page -> Backup -> Backup service credentials.
Borg's access is restricted to that directory.

== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2024-10-04T16:43:49Z

Chimosky: Remove GH action code as it's not needed anymore.

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to Git.
* Set source code repository link - using ssh -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Git version control above, the hooks configured in the repos make it easy for weblate to pull changes from Github.

== Backups ==
Weblate currently backs up to papert using [https://docs.weblate.org/en/weblate-5.4.2/admin/backup.html#remote-backups borgbackup] at {{Code|'''/home/weblate/backups'''}}.

You can view the list of backups with {{Code|'''borg list /home/weblate/backups'''}} which will ask for a passphrase,
the passphrase can be found in weblate admin page -> Backup -> Backup service credentials.
Borg's access is restricted to that directory.

== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Machine/containers

2024-10-03T13:52:09Z

Chimosky: Write basic containers details.

== Hostnames ==

* https://containers.sugarlabs.org/

== Services ==

== General Information ==

This machine hosts only container workloads.

== Location ==

KVM virtual machine hosted on [[Machine/bender]]

== Admins ==

* [[User:Chimosky|Chihurumnaya Ibiam]], Ibiam on [https://matrix.to/#/#sugar-systems:matrix.org #sugar-systems matrix channel] (general containers admin)

* [[User:Bernie|Bernie Innocenti]], Bernie on [https://matrix.to/#/#sugar-systems:matrix.org #sugar-systems matrix channel] (only machine-level issues)

Machine

2024-10-03T13:49:58Z

Chimosky: /* Virtual */

<noinclude>{{TeamHeader|Infrastructure Team}}</noinclude>

Computing hardware or virtual machines maintained by the Sugar Labs [[Infrastructure Team]].

== Physical ==

* [[Machine/justice]]
* [[Machine/freedom]]
* [[Machine/bender]]
* [[Machine/papert]]

== Virtual ==

* [[Machine/lightwave]], with [[Service/Nameservers]],
* [[Machine/pootle]], with [[Service/translate]], or https://translate.sugarlabs.org,
* [[Machine/aslo]], with [[Service/activities]] aslo, or https://activities.laptop.org,
* [[Machine/library]],
* [[Machine/aslo3]], with [[Service/activities3]] aslo-v3, https://github.com/sugarlabs/aslo-v3,
* [[Machine/jita]], with [[Service/git]], [[Service/jabber]], [[Service/meeting]], [[Service/obs]], [[Service/chat]], [[Service/cgit]], [[Service/blacklist]], [[Service/stats]],
* [[Machine/amnesia]],
* [[Machine/beacon]], 
* [[Machine/weblate]], with [[Service/Weblate]], or https://weblate.sugarlabs.org,
* [[Machine/containers]]

== Containers ==

* org.sugarlabs.bugs
* org.sugarlabs.developer-rebuilder
* org.sugarlabs.www-rebuilder
* org.sugarlabs.use-socialhelp
* org.sugarlabs.socialhelp_sso
* local_discourse/app
* org.turtleartday.www-rebuilder
* org.sugarlabs.help-rebuilder

== Student Listing ==

This list was made by a GCI 2018 student.

* [[Machine/backup]]
* [[Machine/bender]]
* [[Machine/freedom]]
* [[Machine/jita]]
* [[Machine/justice]]
* [[Machine/lightwave]]
* [[Machine/pootle]]
* [[Machine/schools]]
* [[Machine/schoolserver]]
* [[Machine/trinity]]

== Automatic Listing ==

This list is generated automatically from Wiki pages that have a prefix of "Machine". It may contain subpages of machines. It may contain machines that have been decommissioned; kept as historical data against future need.

{{Special:PrefixIndex/Machine/}}

[[Image:Sugarlabs systems.jpg|frame]]

Service/Weblate

2024-08-29T00:28:38Z

Chimosky: Use ssh to clone repos as we're using git for the version control system.

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to Git.
* Set source code repository link - using ssh -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.

Add this workflow to {{Code|'''.github/workflows/weblate-sync.yaml'''}} in the Github repo;

name: Weblate - Create PR when weblate pushes changes
on:
push:
branches:
- weblate-sync
jobs:
weblateSync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Create Pull Request
run: gh pr create --base main --head weblate-sync -t "Weblate Synchronization" --body ""
env:
GH_TOKEN: ${\{ github.token }}

This will automatically open a pull-request whenever weblate pushes changes to Github, be sure to drop the
{{Code|\}} in {{Code|GH_TOKEN}}

== Backups ==
Weblate currently backs up to papert using [https://docs.weblate.org/en/weblate-5.4.2/admin/backup.html#remote-backups borgbackup] at {{Code|'''/home/weblate/backups'''}}.

You can view the list of backups with {{Code|'''borg list /home/weblate/backups'''}} which will ask for a passphrase,
the passphrase can be found in weblate admin page -> Backup -> Backup service credentials.
Borg's access is restricted to that directory.

== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2024-08-27T21:31:03Z

Chimosky:

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - using https -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.

Add this workflow to {{Code|'''.github/workflows/weblate-sync.yaml'''}} in the Github repo;

name: Weblate - Create PR when weblate pushes changes
on:
push:
branches:
- weblate-sync
jobs:
weblateSync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Create Pull Request
run: gh pr create --base main --head weblate-sync -t "Weblate Synchronization" --body ""
env:
GH_TOKEN: ${\{ github.token }}

This will automatically open a pull-request whenever weblate pushes changes to Github, be sure to drop the
{{Code|\}} in {{Code|GH_TOKEN}}

== Backups ==
Weblate currently backs up to papert using [https://docs.weblate.org/en/weblate-5.4.2/admin/backup.html#remote-backups borgbackup] at {{Code|'''/home/weblate/backups'''}}.

You can view the list of backups with {{Code|'''borg list /home/weblate/backups'''}} which will ask for a passphrase,
the passphrase can be found in weblate admin page -> Backup -> Backup service credentials.
Borg's access is restricted to that directory.

== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2024-08-27T21:18:07Z

Chimosky:

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - using https -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.

Add this workflow to {{Code|'''.github/workflows/weblate-sync.yaml'''}} in the Github repo;

name: Weblate - Create PR when weblate pushes changes
on:
push:
branches:
- weblate-sync
jobs:
weblateSync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Create Pull Request
run: gh pr create --base main --head weblate-sync -t "Weblate Synchronization" --body ""
env:
GH_TOKEN: ${\{ github.token }}

This will automatically open a pull-request whenever weblate pushes changes to Github, be sure to drop the
{{Code|\}} in {{Code|GH_TOKEN}}

== Backups ==
Weblate currently backs up to papert using [https://docs.weblate.org/en/weblate-5.4.2/admin/backup.html#remote-backups borgbackup] at {{Code|'''/home/weblate/backups'''}}.

You can view the list of backups with {{Code|'''borg list /home/weblate/backups'''}} which will ask for a passphrase,
the passphrase can be found in weblate admin page -> Backup -> Backup service credentials

== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2024-04-04T18:03:59Z

Chimosky: FIx typo

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - using https -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.

Add this workflow to {{Code|'''.github/workflows/weblate-sync.yaml'''}} in the Github repo;

name: Weblate - Create PR when weblate pushes changes
on:
push:
branches:
- weblate-sync
jobs:
weblateSync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Create Pull Request
run: gh pr create --base main --head weblate-sync -t "Weblate Synchronization" --body ""
env:
GH_TOKEN: ${\{ github.token }}

This will automatically open a pull-request whenever weblate pushes changes to Github, be sure to drop the
{{Code|\}} in {{Code|GH_TOKEN}}

== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2024-04-04T17:55:13Z

Chimosky: Add weblate workflow script

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - using https -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation component, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.

Add this workflow to {{Code|'''.github/workflows/webalte-sync.yaml'''}} in the Github repo;

name: Weblate - Create PR when weblate pushes changes
on:
push:
branches:
- weblate-sync
jobs:
weblateSync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Create Pull Request
run: gh pr create --base main --head weblate-sync -t "Weblate Synchronization" --body ""
env:
GH_TOKEN: ${\{ github.token }}

This will automatically open a pull-request whenever weblate pushes changes to Github, be sure to drop the
{{Code|\}} in {{Code|GH_TOKEN}}

== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/translate

2024-04-04T17:30:10Z

Chimosky:

{{Obsolete | Replaced by [[ Service/Weblate]]}}

== Hostnames ==

* http://translate.sugarlabs.org/

== Hosted on ==

[[Machine/pootle]]

== Administrative contact ==

* translate AT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Sebastian|Sebastian Silva]] has assumed maintainership tasks
* [[User:Cjl|Chris Leonard]] has Pootle administrator privs, and heads the localization efforts.
* [[User:Bernie|Bernie Innocenti]] has system admin and Pootle administrator privs, but takes care only of OS-level administration.
* [[User:SayaminduDasgupta|Sayamindu Dasgupta]] is the former admin. He still has an emeritus sysadmin account and he can be very helpful if contacted by email.

== Language Administrators ==

Language administrators are typically native speakers of a given language that take on responsibility (granted by a Pootle administrator after a request to the Localization list) for reviewing and committing PO files for a given language. Contacting language administrators is generally done by posting to the Localization list.

More information on language administrator duties can be found on [[Translation_Team/Administration_QuickStart|this page]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/var/lib/pootle}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/apache2}} 
{{Code|/etc/init.d/pootle}}
|-
!scope="row" | Logs
|{{Code|/var/log/apache2}}
|-
!scope="row" | Config
|
{{Code|/etc/apache2/sites-enabled/000-default}} 
{{Code|/etc/cron.d/pootle}} 
{{Code|/var/www/pootle/sugarlabs/pootle.conf}} 
|-
!scope="row" | Ports
|
{{Code|80}} HTTP server
|-
|}

== Upgrade notes ==

*A backup of the DB and pootle localsettings.py must be done also.
*Backup of the /var/lib/pootle structure
*New versions of Django and Translate toolkit must be installed first
*Restore localsettings and DB backup

== Mantainance Notes ==

Pootle in Sugar is maintained. (icarito has step-up to be maint)

== Migrated to Pootle 2.5.0 ==

Notes on the process were recorded here: [[Service/translate/Pootle2.5]]

== Files ==

Important files and directories in the root directory, {{Code|/var/lib/pootle}}.

{{Code|'''checkouts'''}} 
Sources are checked out in this directory and being used to keep final {{Code|.pot}} and {{Code|.po}} files. The hierarchy is:

checkouts/''pootle-project''/''pootle-po-filename-without-po-suffix''/''sources''

{{Code|'''translations'''}} 
Pootle uses this directory as a sources of files to translate, it contains symlinks to files from the {{Code|checkouts}} directory. The hierarchy is:

translations/''pootle-project''/''lang''/''symlinks-to-po-files''

{{Code|'''maintenance'''}} 
Contains some sugar-specific scripts to help maintain our Pootle instance, they are managed in http://git.sugarlabs.org/projects/pootle-helpers.

{{Code|'''maintenance/helpers/potupdater/project_list.ini'''}} 
This is an Ini file that contains configuration for all used sources repositories. Each section describes one sources repository, where section name is full path, in form of {{Code|/var/lib/pootle/checkouts/''pootle-project''/''pootle-filename''/''some-path-within-sources''/''pot-file''}}, to the {{Code|.pot}} file, and contains following options:

* {{Code|project}} required, meaning-less project name;
* {{Code|vcs}} required, the type of VCS for; supported values are: {{Code|git}};
* {{Code|method}} required, the method how to generate {{Code|.pot}} files from sources; supported values are: {{Code|bundlebuilder}} for activities, {{Code|intltool}} for intltool based projects;
* {{Code|layout}} required, ?;
* {{Code|ignore-files}} optional, the semicolon separated list of file paths that are relative to the sources root; if {{Code|method}} is {{Code|bundlebuilder}} this value will be used to ignore while producing {{Code|.pot files}};

== Tools ==

* {{Code|potupdater/pogenerator.py}} pulls from git and svn so we have updated sources, then it generates a new .pot file from them. Translated strings get reflected in the .po files in each module, and when the language maintainer clicks the Commit to VCS link, get pushed back to the upstream module.
* {{Code|admin/pootlepopulator.py}} checkout sources.
* {{Code|misc/pootle.cron}} all daily basis routines.
* ''...''

== Tips ==

=== Create new Pootle project ===

* Create new project in Pootle admin menu, ''admin->projects'';
* Add all needed langs;
* Checkout all sources using command:

sudo -u pootle -i python maintenance/helpers/admin/pootlepopulator.py ''pootle-project'' ''git-clone-url'' ''pootle-filename-wo-po-suffix'' ''git-branch''

Example:

To checkout the sugar in the branch sucrose-0.94 (in pootle is in the project glucose94) we sshould do:

cd /var/lib/pootle/
sudo -u pootle -i python maintenance/helpers/admin/pootlepopulator.py glucose94 gitorious@git.sugarlabs.org:sugar/mainline.git sugar sucrose-0.94

* Add new sections to the [[#Files|project_list.ini]] file to describe new {{Code|.pot}} locations;
* Run {{Code|misc/pootle.cron}} script from {{Code|pootle}} user to generate all sufficient files;
* Click ''rescan the project files'' in ''Templates->Project->Files'' to reveal newly created {{Code|.pot}} files;
* Click ''Update from templates'' for all languages in newly created project to peek up {{Code|.po}} files symlinked by {{Code|misc/pootle.cron}} script.

=== Adding activities ===

Before registering new activity on http://translate.sugarlabs.org, make sure that:

* New activity is being hosted on http://git.sugarlabs.org;
* The {{Code|pootle}} user was added to the repository with commit access rights;
* You have a proper {{Code|GIT_URL}} to clone repository from with commit permissions, e.g., {{Code|gitorious@git.sugarlabs.org:cartoon-builder/mainline.git}}; that might be found on home page in Gitorious, e.g., http://git.sugarlabs.org/cartoon-builder, in ''Clone & push urls'' field with selector ''SSH'';
* You know the proper {{Code|CATEGORY}} name to register the project in;
* There is an unique {{Code|NAME}} of activity, this name will be used as a name of project in Pootle and directory name;
* You know the proper {{Code|BRANCH}} in Git repository to use for translation; by default, it is {{Code|master}}.

To process the registration, login to translate.sugarlabs.org and enter:

sudo -u pootle python /var/lib/pootle/maintenance/helpers/admin/pootlepopulator.py ''<CATEGORY>'' ''<GIT_URL>'' /var/lib/pootle/checkouts/''<CATEGORY>''/''<NAME>'' [''<BRANCH>'']

After that, for [http://git.sugarlabs.org/pootle-helpers pootle-helper] project in {{Code|potupdater/project_list.ini}}, add the following strings:

[/var/lib/pootle/checkouts/''<CATEGORY>''/''<NAME>''/po/''<.pot-filename>'']
project = ''<NAME>''
vcs = git
method = bundlebuilder
layout = gnu

Commit new changes, and pull from on pootle VM:

(cd /var/lib/pootle/maintenance/helpers; sudo -u pootle git pull origin master)

Do ''update from templates'' on the ''templates'' project on Pootle's frontend. And wait until daily cron job will populate languages for newly registered project, or run it immediately:

sudo -u pootle python /var/lib/pootle/maintenance/helpers/admin/add_langs.py

Then your activity must be in place to be translated and ''commit to VCS/update from VCS'' links must be activated.

=== Working with git in the pootle server ===

The git operations must be done by the pootle user:

sudo -u pootle git log

sudo -u pootle git push origin sucrose-0.82

This script tell you when you can update different clones of activities, when new strings are added via gettext in each repo.

/var/lib/pootle/maintenance/helpers/potupdater/check_unmerged_translations.sh

Other important script is pogenerator.py this script re-generates pot in each repo.

=== Resolving conflicts ===

If the maintainer did a commit with a file in the po directory we will have a conflict, and Pootle can not do a pull.

Pootle build the pot file from the sources, if we compare and the translations are updated in pootle
we can do a pull preserving the info in pootle:

sudo -u pootle git pull -s ours

=== Checking that pootle is working ===

* When commiting from pootle interface, repos in git reflect the commit as something similar to:

pootle pushed 3fd0cf7b to taportfolio/mainline:master
on March 04, 2011 01:32
Commit from Sugar Labs: Translation System by user cjl.: 2 of 25 messages translated (0 fuzzy).

* Pogenerator.py (in cronjob), it's also giving mails with info like:

Already up-to-date. or
####### Checking POT for Write (master) ######

=== Etoys .pot update ===

Go to Etoys translation directory (that is svn checkout from upstream project):

su - pootle
cd ~/translations/etoys_new

Since there is no need in changing .pot files on Pootle level, revert local changes if they present:

svn revert templates/*.pot

Fetch new update from the upstream:

svn up templates

=== Tips ===

* How to manipulate users:

django-admin shell --settings=pootle.settings
>>> from django.contrib.auth.models import User
>>> u = User.objects.get(username='bernie')
>>> u.is_superuser = True
>>> u.save()

* Refresh stats, needed when the database and the checked out modules get out of sync:

sudo -u pootle django-admin refresh_stats --settings=pootle.settings

* If you have a commit error file because of only read git url, please rm the old '''/var/lib/pootle/checkouts/''' files related with that activity or project and re run pootlepopulator.

* Also if there are errors related with git add, is likely that some lang.po files are not versionated on pootle server, please run '''git add .''' inside the activity or project.

* When there are '''commit to cvs/update to cvs''' links missing in activities or projects please check git url in .git/config , this URL must be writable by pootle.

== References ==

* http://translate.sourceforge.net/wiki/pootle/installation
* http://lists.laptop.org/listinfo/localization
* http://git.sugarlabs.org/pootle-helpers
* /usr/lib/python2.6/dist-packages/translate/storage/versioncontrol/git.py (Translate)

[[Category:Service|translate]]

Machine/pootle

2024-04-04T17:29:34Z

Chimosky:

== Hostnames ==

* http://translate.sugarlabs.org/

== Services ==

* [[Service/translate]]

== General Information ==

This machine hosts only Pootle.

== Location ==

KVM virtual machine hosted on [[Machine/justice]]

== Admins ==

* [[User:Sebastian|Sebastian Silva]], icarito on #sugar Freenode (general pootle admin)

* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Freenode (only machine-level issues)

* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Freenode

Machine/pootle

2024-04-04T17:29:01Z

Chimosky:

{{Obsolete | Replaced by [[ Service/Weblate]]}}

== Hostnames ==

* http://translate.sugarlabs.org/

== Services ==

* [[Service/translate]]

== General Information ==

This machine hosts only Pootle.

== Location ==

KVM virtual machine hosted on [[Machine/justice]]

== Admins ==

* [[User:Sebastian|Sebastian Silva]], icarito on #sugar Freenode (general pootle admin)

* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Freenode (only machine-level issues)

* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Freenode

Sugar on a Stick/Downloads

2024-02-12T17:05:48Z

Chimosky: Point to fedora SOAS download page

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="4" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickAvocado-320px.png|320px|left|link=https://spins.fedoraproject.org/soas/]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [https://fedoraproject.org/wiki/Overview Fedora®] [https://spins.fedoraproject.org/soas Spin] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]].

Sugar on a Stick will run on
* any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a [[wikipedia:Live USB|Live USB]],
* a 32-bit computer with the TOAST version of Sugar (Trisquel on a Sugar Toast). See [[Trisquel On A Sugar Toast]].
* a Raspberry Pi 2 or 3, using a microSD card, or;
* any computer as a virtual machine.

You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Tutorials/Installation/Install with liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.

|- style="border: 0; border-width: 0; text-align: center"
| colspan="2" style="border: 0; border-width: 0; text-align: left" |


[[File:Download Mirabell.png|link=https://fedoraproject.org/spins/soas/download]]

x86_64 (64-bit)

| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/35/Spins/armhfp/images/Fedora-SoaS-35-1.2.armhfp.raw.xz]]
armhfp Raspberry Pi 2 or 3, see [https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md How to install].
|-
| colspan="3" style="border: 0; border-width: 0; text-align: left" |

* How to quickly demonstrate: ([[Sugar on a Stick/Installation Process|English]]), ([[Sugar on a Stick/Proceso de instalacion|en español]])

|-
|

| colspan="2" |

|}

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

Sugar on a Stick/Downloads

2024-02-12T16:56:18Z

Chimosky: Undo revision 104108 by Chimosky (talk)

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="4" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickAvocado-320px.png|320px|left|link=https://spins.fedoraproject.org/soas/]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [https://fedoraproject.org/wiki/Overview Fedora®] [https://spins.fedoraproject.org/soas Spin] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]].

Sugar on a Stick will run on
* any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a [[wikipedia:Live USB|Live USB]],
* a 32-bit computer with the TOAST version of Sugar (Trisquel on a Sugar Toast). See [[Trisquel On A Sugar Toast]].
* a Raspberry Pi 2 or 3, using a microSD card, or;
* any computer as a virtual machine.

You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Tutorials/Installation/Install with liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.

|- style="border: 0; border-width: 0; text-align: center"
| colspan="2" style="border: 0; border-width: 0; text-align: left" |


[[File:Download Mirabell.png|link=http://download.sugarlabs.org/soas/Fedora-SoaS-Live-x86_64-F35-20220215.iso]]

x86_64 (64-bit)

| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/35/Spins/armhfp/images/Fedora-SoaS-35-1.2.armhfp.raw.xz]]
armhfp Raspberry Pi 2 or 3, see [https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md How to install].
|-
| colspan="3" style="border: 0; border-width: 0; text-align: left" |

* How to quickly demonstrate: ([[Sugar on a Stick/Installation Process|English]]), ([[Sugar on a Stick/Proceso de instalacion|en español]])

|-
|

| colspan="2" |

|}

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

Sugar on a Stick/Downloads

2024-02-12T16:55:18Z

Chimosky: Point to SOAS download page in fedora

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="4" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickAvocado-320px.png|320px|left|link=https://spins.fedoraproject.org/soas/]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [https://fedoraproject.org/wiki/Overview Fedora®] [https://spins.fedoraproject.org/soas Spin] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]].

Sugar on a Stick will run on
* any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a [[wikipedia:Live USB|Live USB]],
* a 32-bit computer with the TOAST version of Sugar (Trisquel on a Sugar Toast). See [[Trisquel On A Sugar Toast]].
* a Raspberry Pi 2 or 3, using a microSD card, or;
* any computer as a virtual machine.

You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Tutorials/Installation/Install with liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.

|- style="border: 0; border-width: 0; text-align: center"
| colspan="2" style="border: 0; border-width: 0; text-align: left" |


[[File:Download Mirabell.png|link=http://download.sugarlabs.org/soas/Fedora-SoaS-Live-x86_64-F35-20220215.iso]]

x86_64 (64-bit)

| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/35/Spins/armhfp/images/Fedora-SoaS-35-1.2.armhfp.raw.xz]]
armhfp Raspberry Pi 2 or 3, see [https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md How to install].
|-
| colspan="3" style="border: 0; border-width: 0; text-align: left" |

* How to quickly demonstrate: ([[Sugar on a Stick/Installation Process|English]]), ([[Sugar on a Stick/Proceso de instalacion|en español]])

|-
|

| colspan="2" |

|}

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

Sysadmin/Letsencrypt

2024-01-01T12:25:10Z

Chimosky: /* Sites */ Add weblate

== Description ==

Let’s Encrypt (LE) is a free, automated, and open certificate authority (CA), run for the public’s benefit. It is sponsored by the biggest Internet companies and browsers: Google (Chrome), Mozilla (Firefox), and so on. At the time of writing, LE is in public beta.

Currently, we have LE installed on [[Machine/freedom]] and [[Machine/sunjammer]].

== Installation ==

We have chosen <code>/opt/letsencrypt</code> as the base or home directory for the LE client. The LE Client is a fully-featured, extensible client for the Let’s Encrypt CA (or any other CA that speaks the ACME protocol) that can automate the tasks of obtaining certificates and configuring webservers to use them.

Because there is no a LE package for Ubuntu yet, we must clone the <code>letsencrypt-auto</code> wrapper script. This script obtains some dependencies from the OS (apt-get) and puts others in a python virtual environment (Pip). The only requirement is Python 2.6 or Python 2.7.

<pre>git clone https://github.com/letsencrypt/letsencrypt</pre>

This client requires root access in order to write to <code>/etc/letsencrypt</code>, <code>/var/log/letsencrypt</code>, <code>/var/lib/letsencrypt</code>; to bind to ports 80 and 443 and to read and modify webserver configurations (for apache or nginx plugins).

== Getting a certificate ==

The Let’s Encrypt client supports a number of different ''plugins'' that can be used to obtain and/or install certificates. For the moment, we decided to get the certificates manually and apply the changes to the the web server with a script. We can use the Nginx plugin to automatically obtain and install the certificate but this plugin is still experimental.

In order to automate the process (of getting the cert), we create a config file for each domain inside the folder <code>/etc/letsencrypt/config</code>. For example, the config file for www.slo is:

<pre>
# We use a 4096 bit RSA key instead of 2048
rsa-key-size = 4096

email = sysadmin@sugarlabs.org
domains = sugarlabs.org, www.sugarlabs.org

authenticator = webroot

# This is the webroot directory of your domain in which
# letsencrypt will write a hash in /.well-known/acme-challenge directory.
webroot-path = /srv/www-sugarlabs/
</pre>

The LE validation server must have access to the domain (port 80) of which we want to get the certificate. In order to validate that the server control the domain, the LE CA will issue one or more sets of challenges. For example, provisioning an HTTP resource under a well-known URI. Usually, the resource requested will be located at <code>/.well-known/acme-challenge</code> under the webroot folder of the requested site.

In Nginx, we can define how to process a specific request with the location directive. Be sure to add the following lines to the server block inside Nginx:

<pre>
location '/.well-known/acme-challenge' {
root /srv/www-sugarlabs/;
}
</pre>

To get the certificate using the previous config file, we must execute the following command:

<pre>/opt/letsencrypt/letsencrypt-auto certonly --config /etc/letsencrypt/config/sugarlabs.org.ini </pre>

All generated keys and issued certificates can be found in <code>/etc/letsencrypt/live/sugarlabs.org/</code>.

The same process can be applied for getting certs for other domains:
(1) create a subdomain.domain.tld config file,
(2) define the well-know resource and,
(3) request the certificate.

'''NOTE''': We had to comment out our CAA records in the DNS in order to obtain the certificates. CAA records forbids LE to issue certificates for a domain.

== Renewing a Certificate ==

Let’s Encrypt CA issues short lived certificates (90 days). In order to automate the renewal, we everyday automatically execute a script which checks the expiration day for every certificate and requests the renewal 15 days before the expiration day (this value is tweakable). After renewing the cert, the script reload the Nginx config.

<pre>
#!/bin/bash

LE_CERTS='/etc/letsencrypt/live'
LE_CONFIG_PATH='/etc/letsencrypt/config'
LE_BIN='/opt/letsencrypt/letsencrypt-auto'
WEB_SERVER='nginx'
EXP_LIMIT=15

for config in $(ls $LE_CONFIG_PATH/*.ini); do
domain=$(basename "$config" .ini)
DATE_NOW=$(date -d "now" +%s)
EXP_DATE=$(date -d "`openssl x509 -in $LE_CERTS/$domain/cert.pem -text -noout | grep "Not After" | cut -c 25-`" +%s)
EXP_DAYS=$(( (EXP_DATE - $DATE_NOW) / 86400 ))
if (( $EXP_DAYS < $EXP_LIMIT )) ; then
echo "The certificate for $domain is about to expire soon. Starting renewal..."
$LE_BIN certonly --renew-by-default --config $config
echo "Reloading $WEB_SERVER"
/usr/sbin/service $WEB_SERVER reload
echo "Renewal process finished for $domain"
else
echo "The certificate for $domain is up to date, no need for renewal ($EXP_DAYS days left for renewal)."
fi
done
</pre>

The script is named <code>renew-letsencrypt.sh</code> and is located in <code>/usr/local/bin </code>

== Sites ==

The sites currently with a LE SSL certificate are:

bugs.sugarlabs.org
bundlebin.sugarlabs.org
developer.sugarlabs.org
freedom.sugarlabs.org
help.sugarlabs.org
hook.sugarlabs.org
nagios.sugarlabs.org
socialhelp.sugarlabs.org
sugarlabs.org
turtleartday.org
use-socialhelp.sugarlabs.org
vote.sugarlabs.org

download.sugarlabs.org
ldap.sugarlabs.org
lists.sugarlabs.org
munin.sugarlabs.org
musicblocks.sugarlabs.org
people.sugarlabs.org
static.sugarlabs.org
sunjammer.sugarlabs.org
turtle.sugarlabs.org
wiki.sugarlabs.org
weblate.sugarlabs.org

== Contact ==

* [[User:scg|Samuel]], scg on #sugar on Freenode.

Service/Weblate

2023-12-19T14:26:08Z

Chimosky: /* Maintenance Notes */

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - using https -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation componet, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.
== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2023-12-19T14:25:32Z

Chimosky: Add saslauthd instructions

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maintainer)

After a restart, make sure to run saslauthd to enable authentication for postfix;
{{Code|'''$ saslauthd -a shadow'''}} 

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - using https -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation componet, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.
== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2023-12-08T12:14:54Z

Chimosky: /* Create new Weblate translation component */

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maint)

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - using https -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If an upload is incomplete, return to translation componet, then Manage->Repository maintenance->Rescan, this will re-scan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.
== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2023-12-08T12:01:17Z

Chimosky: /* Create new Weblate translation component */

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maint)

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - using https -.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If you don't see the uploaded po files after uploading an activity, click the Activity then Manage->Repository maintenance->Rescan,
this will rescan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.
== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2023-12-08T11:59:49Z

Chimosky:

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maint)

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link.
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

If you don't see the uploaded po files after uploading an activity, click the Activity then Manage->Repository maintenance->Rescan,
this will rescan the repo and add all the po files.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.
== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2023-08-19T15:44:12Z

Chimosky:

== Hostnames ==

* https://weblate.sugarlabs.org/

== Hosted on ==

[[Machine/weblate]]

== Administrative contact ==

* admin AT weblate DOT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Chimosky|Chihurumnaya Ibiam]] has assumed maintainership tasks.
* [[User:Bernie|Bernie Innocenti]] has system admin privs, but takes care only of OS-level administration.
* [[User:MrBIOS|Alex Perez]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|weblate}}
|-

|-
!scope="row" | Home
|{{Code|/home/weblate/weblate-docker}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/nginx}} 
{{Code|/etc/init.d/docker}}
|-
!scope="row" | Logs
|
{{Code|/var/log/nginx}} 
{{Code|docker logs weblate-docker-weblate-1}} 
|-
!scope="row" | Config
|
{{Code|/etc/nginx/sites-enabled/weblate}} 
{{Code|/home/weblate/weblate-docker/docker-compose.yml}} 
|-
!scope="row" | Ports
|
{{Code|443}} HTTP server 
{{Code|8080}} weblate docker container port 
|-
!scope="row" | Volumes
|
{{Code|/var/lib/docker/volumes/weblate-docker_postgres-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_redis-data}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-cache}} 
{{Code|/var/lib/docker/volumes/weblate-docker_weblate-data}} 
|-
|}

== Upgrade Notes ==

Weblate has [https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container upgrade notes] on upgrading the docker container.

== Maintenance Notes ==
Weblate is maintained. (ibiam has step-up to be maint)

== Files ==
Important files and directories in the root directory, {{Code|/home/weblate/weblate-docker}}.

{{Code|'''docker-compose.yml'''}} 
Contains definitions for all the services and volumes used by weblate, which includes weblate, database and cache with volumes weblate-cache, weblate-data, postgres-data, redis-data.
.

{{Code|'''environment'''}} 
Contains environment variables used by container.

== Tips ==

=== Create new Weblate translation component ===

* Create new translation component in Weblate admin menu, ''Add new translation component'';
* Select Project, we currently have {{Code|core-sugar}} and {{Code|Sugar-Activities}}, core-sugar contains sugar core APIs.
* Set version control system to GitHub pull request.
* Set source code repository link - ssh links would be preferred -
* Set repository branch.
* Set File format gettext PO file, File mask po/*.po
* Set Repository push URL to enable autoupdate of changes to Github from weblate.
* Set Push branch to weblate-sync which would be used to create a PR.
* On Github, add hook {{Code|https://weblate.sugarlabs.org/hooks/github/}} to activity repo as it's used for automated flow of updates to weblate.
* Check license in activity repo matches Translation license selected by weblate or set to the right license.
* Add all needed langs; when adding from Github, weblate automatically adds all the PO files and you'll only need to do this if the only PO file the activity has is the template PO file.

== Synchronization ==

Weblate automatically pushes changes to Github when there's a change on weblate because of the Github pull request version control above and the Github configuration can be found in the
environment file, the hooks configured in the repos make it easy for weblate to pull changes from Github.
== References ==

https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-the-docker-container

Service/Weblate

2023-08-19T15:39:40Z

Chimosky: Add weblate service info

Machine

2023-08-19T14:19:40Z

Chimosky:

<noinclude>{{TeamHeader|Infrastructure Team}}</noinclude>

Computing hardware or virtual machines maintained by the Sugar Labs [[Infrastructure Team]].

== Physical ==

* [[Machine/justice]]
* [[Machine/freedom]]
* [[Machine/bender]]
* [[Machine/papert]]

== Virtual ==

* [[Machine/lightwave]], with [[Service/Nameservers]],
* [[Machine/pootle]], with [[Service/translate]], or https://translate.sugarlabs.org,
* [[Machine/aslo]], with [[Service/activities]] aslo, or https://activities.laptop.org,
* [[Machine/library]],
* [[Machine/aslo3]], with [[Service/activities3]] aslo-v3, https://github.com/sugarlabs/aslo-v3,
* [[Machine/jita]], with [[Service/git]], [[Service/jabber]], [[Service/meeting]], [[Service/obs]], [[Service/chat]], [[Service/cgit]], [[Service/blacklist]], [[Service/stats]],
* [[Machine/amnesia]],
* [[Machine/beacon]], 
* [[Machine/weblate]], with [[Service/Weblate]], or https://weblate.sugarlabs.org,

== Containers ==

* org.sugarlabs.bugs
* org.sugarlabs.developer-rebuilder
* org.sugarlabs.www-rebuilder
* org.sugarlabs.use-socialhelp
* org.sugarlabs.socialhelp_sso
* local_discourse/app
* org.turtleartday.www-rebuilder
* org.sugarlabs.help-rebuilder

== Student Listing ==

This list was made by a GCI 2018 student.

* [[Machine/backup]]
* [[Machine/bender]]
* [[Machine/freedom]]
* [[Machine/jita]]
* [[Machine/justice]]
* [[Machine/lightwave]]
* [[Machine/pootle]]
* [[Machine/schools]]
* [[Machine/schoolserver]]
* [[Machine/trinity]]

== Automatic Listing ==

This list is generated automatically from Wiki pages that have a prefix of "Machine". It may contain subpages of machines. It may contain machines that have been decommissioned; kept as historical data against future need.

{{Special:PrefixIndex/Machine/}}

[[Image:Sugarlabs systems.jpg|frame]]

Machine/weblate

2023-08-19T14:16:12Z

Chimosky: Created page with "== Hostnames == * https://weblate.sugarlabs.org/ == Services == * Service/Weblate == General Information == This machine hosts only Weblate. == Location == KVM virt..."

== Hostnames ==

* https://weblate.sugarlabs.org/

== Services ==

* [[Service/Weblate]]

== General Information ==

This machine hosts only Weblate.

== Location ==

KVM virtual machine hosted on [[Machine/bender]]

== Admins ==

* [[User:Chimosky|Chihurumnaya Ibiam]], Ibiam on [https://matrix.to/#/#sugar-systems:matrix.org #sugar-systems matrix channel] (general weblate admin)

* [[User:Bernie|Bernie Innocenti]], Bernie on [https://matrix.to/#/#sugar-systems:matrix.org #sugar-systems matrix channel] (only machine-level issues)

* [[User:MrBIOS|Alex Perez]], MrBIOS on [https://matrix.to/#/#sugar-systems:matrix.org #sugar-systems matrix channel]

Service/smtp

2023-07-30T15:15:43Z

Chimosky:

== Hostnames ==

{|class=wikitable
! hostname !! service !! port !! function
|-
| smtp.sugarlabs.org || smtp || 25 || Local delivery (plain SMTP)
|-
| smtp.sugarlabs.org || [http://www.faqs.org/rfcs/rfc2476.html submission] || 587 || SMTP with STARTTLS, legacy
|-
| smtp.sugarlabs.org || [https://tools.ietf.org/html/rfc6409 submissions] || 465 || Email relay (SMTP with SSL, password authentication required)
|}

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

* postmaster AT sugarlabs DOT org

== Sysadmins ==

* [[User:Bernie|Bernie Innocenti]]
* (add yourself here if you tend to the postmaster [[Machine/rt|RT]] queue)

== Notes ==

* Users with a Sugar Labs [[Service/shell|shell account]] on [[Machine/sunjammer|sunjammer]] can use our SMTP relay for personal email submission. ''Any abuse will be prosecuted.''

* The [https://tools.ietf.org/html/rfc6409 submissions] port (465) is preferred for email relay. Unauthenticated and unencrypted connections are not allowed to relay.

* All email originating from the sugarlabs.org domain must be submitted through our SMTP server. '''Failure to do so may result in your email being blocked by spam filters.'''

== SPF ==

Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] records.

You can add an spf record in the zone file in the form

hostname TXT "v=spf1 redirect=_spf.hostname.sugarlabs.org"
_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/mask a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"

The '''a''' and '''mx''' values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined
for hostname.

Also maintain spacing and formatting for each section you add in the zone file.

== DKIM ==

Our domain publishes a [http://en.wikipedia.org/wiki/DKIM DKIM] key.

To test DKIM, send an email to autorespond+dkim@dk.elandsys.com

To generate an ed25519 key to use for DKIM, you can use openssl

# Generate ed25519 key
$ openssl genpkey -algorithm ed25519 -out dkim_private.pem
# Generate public key from private key
$ openssl pkey -in dkim_private.pem -pubout -out dkim_public.pem

For ed25519 keys, the p value in the DKIM record must only contain the BASE64 encoded public key, without an ASN.1 structure

$ openssl asn1parse -in dkim_public.pem -offset 12 -noout -out /dev/stdout | openssl base64
VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo=

Your entry would look like this

selector1._domainkey.hostname TXT "v=DKIM1; g=*; k=ed25519; p=VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo="
_adsp._domainkey.hostname TXT "dkim=unknown"

When using an ed25519 key, you'll need to add a fallback RSA key for backward compatibility.

# Generate rsa key
$ openssl genrsa -out rsa_private.key 2048
# Generate public key from private key
$ openssl rsa -in rsa_private.key -pubout -outform der 2>/dev/null | openssl base64 -A

You can then add a KeyTable and SigningTable to your opendkim.conf

KeyTable refile:/etc/opendkim/KeyTable
SigningTable refile:/etc/opendkim/SigningTable

# Contents of KeyTable with both keys
selector1._domainkey.hostname.sugarlabs.org hostname.domain-name:selector1:/path/to/selector1/private/*.key
selector2._domainkey.hostname.sugarlabs.org hostname.domain-name:selector2:/path/to/selector2/private/*.key

# Contents of SigningTable
*@hostname.domain-name selector1._domainkey.hostname.sugarlabs.org
*@hostname.domain-name selector2._domainkey.hostname.sugarlabs.org

Then add a DKIM record for the second selector

w-mail._domainkey.weblate IN TXT ("v=DKIM1; h=sha256; k=rsa; p="*")

The value of p is the public key of the generated RSA key above.

Ensure your private keys are on hostname.

== See also ==

* [[Service/imap]]
* [[Service/webmail]]
* [[Service/email]]

[[Category:Service|imap]]

Service/smtp

2023-07-30T15:14:22Z

Chimosky:

== Hostnames ==

{|class=wikitable
! hostname !! service !! port !! function
|-
| smtp.sugarlabs.org || smtp || 25 || Local delivery (plain SMTP)
|-
| smtp.sugarlabs.org || [http://www.faqs.org/rfcs/rfc2476.html submission] || 587 || SMTP with STARTTLS, legacy
|-
| smtp.sugarlabs.org || [https://tools.ietf.org/html/rfc6409 submissions] || 465 || Email relay (SMTP with SSL, password authentication required)
|}

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

* postmaster AT sugarlabs DOT org

== Sysadmins ==

* [[User:Bernie|Bernie Innocenti]]
* (add yourself here if you tend to the postmaster [[Machine/rt|RT]] queue)

== Notes ==

* Users with a Sugar Labs [[Service/shell|shell account]] on [[Machine/sunjammer|sunjammer]] can use our SMTP relay for personal email submission. ''Any abuse will be prosecuted.''

* The [https://tools.ietf.org/html/rfc6409 submissions] port (465) is preferred for email relay. Unauthenticated and unencrypted connections are not allowed to relay.

* All email originating from the sugarlabs.org domain must be submitted through our SMTP server. '''Failure to do so may result in your email being blocked by spam filters.'''

== SPF ==

Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] records.

You can add an spf record in the zone file in the form

hostname TXT "v=spf1 redirect=_spf.hostname.sugarlabs.org"
_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/mask a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"

The '''a''' and '''mx''' values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined
for hostname.

Also maintain spacing and formatting for each section you add in the zone file.

== DKIM ==

Our domain publishes a [http://en.wikipedia.org/wiki/DKIM DKIM] key.

To test DKIM, send an email to autorespond+dkim@dk.elandsys.com

To generate an ed25519 key to use for DKIM, you can use openssl

# Generate ed25519 key
$ openssl genpkey -algorithm ed25519 -out dkim_private.pem
# Generate public key from private key
$ openssl pkey -in dkim_private.pem -pubout -out dkim_public.pem

For ed25519 keys, the p value in the DKIM record must only contain the BASE64 encoded public key, without an ASN.1 structure

$ openssl asn1parse -in dkim_public.pem -offset 12 -noout -out /dev/stdout | openssl base64
VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo=

Your entry would look like this

selector1._domainkey.hostname TXT "v=DKIM1; g=*; k=ed25519; p=VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo="
_adsp._domainkey.hostname TXT "dkim=unknown"

When using an ed25519 key, you'll need to add a fallback RSA key for backward compatibility.

# Generate rsa key
$ openssl genrsa -out rsa_private.key 2048
# Generate public key from private key
$ openssl rsa -in rsa_private.key -pubout -outform der 2>/dev/null | openssl base64 -A

You can then add a KeyTable and SigningTable to your opendkim.conf

KeyTable refile:/etc/opendkim/KeyTable
SigningTable refile:/etc/opendkim/SigningTable

# Contents of KeyTable with both keys
selector1._domainkey.hostname.domain-name hostname.domain-name:selector1:/path/to/selector1/private/*.key
selector2._domainkey.hostname.domain-name hostname.domain-name:selector2:/path/to/selector2/private/*.key

# Contents of SigningTable
*@hostname.domain-name selector1._domainkey.hostname.domain-name
*@hostname.domain-name selector2._domainkey.hostname.domain-name

Then add a DKIM record for the second selector

w-mail._domainkey.weblate IN TXT ("v=DKIM1; h=sha256; k=rsa; p="*")

The value of p is the public key of the generated RSA key above.

Ensure your private keys are on hostname.

== See also ==

* [[Service/imap]]
* [[Service/webmail]]
* [[Service/email]]

[[Category:Service|imap]]

Service/smtp

2023-07-29T13:05:47Z

Chimosky:

== Hostnames ==

{|class=wikitable
! hostname !! service !! port !! function
|-
| smtp.sugarlabs.org || smtp || 25 || Local delivery (plain SMTP)
|-
| smtp.sugarlabs.org || [http://www.faqs.org/rfcs/rfc2476.html submission] || 587 || SMTP with STARTTLS, legacy
|-
| smtp.sugarlabs.org || [https://tools.ietf.org/html/rfc6409 submissions] || 465 || Email relay (SMTP with SSL, password authentication required)
|}

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

* postmaster AT sugarlabs DOT org

== Sysadmins ==

* [[User:Bernie|Bernie Innocenti]]
* (add yourself here if you tend to the postmaster [[Machine/rt|RT]] queue)

== Notes ==

* Users with a Sugar Labs [[Service/shell|shell account]] on [[Machine/sunjammer|sunjammer]] can use our SMTP relay for personal email submission. ''Any abuse will be prosecuted.''

* The [https://tools.ietf.org/html/rfc6409 submissions] port (465) is preferred for email relay. Unauthenticated and unencrypted connections are not allowed to relay.

* All email originating from the sugarlabs.org domain must be submitted through our SMTP server. '''Failure to do so may result in your email being blocked by spam filters.'''

== SPF ==

Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] records.

You can add an spf record in the zone file in the form

hostname TXT "v=spf1 redirect=_spf.hostname.sugarlabs.org"
_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/mask a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"

The '''a''' and '''mx''' values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined
for hostname.

Also maintain spacing and formatting for each section you add in the zone file.

== DKIM ==

Our domain publishes a [http://en.wikipedia.org/wiki/DKIM DKIM] key.

To test DKIM, send an email to autorespond+dkim@dk.elandsys.com

To generate an ed25519 key to use for DKIM, you can use openssl

# Generate ed25519 key
$ openssl genpkey -algorithm ed25519 -out dkim_private.pem
# Generate public key from private key
$ openssl pkey -in dkim_private.pem -pubout -out dkim_public.pem

For ed25519 keys, the p value in the DKIM record must only contain the BASE64 encoded public key, without an ASN.1 structure

$ openssl asn1parse -in dkim_public.pem -offset 12 -noout -out /dev/stdout | openssl base64
VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo=

Your entry would look like this

default._domainkey.hostname TXT "v=DKIM1; g=*; k=ed25519; p=VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo="
_adsp._domainkey.hostname TXT "dkim=unknown"

Ensure your private key is on hostname and specify the path to it when using a tool like opendkim - /etc/opendkim.conf -, with
the user and group of the key set to opendkim.

== See also ==

* [[Service/imap]]
* [[Service/webmail]]
* [[Service/email]]

[[Category:Service|imap]]

Service/smtp

2023-07-29T12:51:53Z

Chimosky: Make a and m bold.

== Hostnames ==

{|class=wikitable
! hostname !! service !! port !! function
|-
| smtp.sugarlabs.org || smtp || 25 || Local delivery (plain SMTP)
|-
| smtp.sugarlabs.org || [http://www.faqs.org/rfcs/rfc2476.html submission] || 587 || SMTP with STARTTLS, legacy
|-
| smtp.sugarlabs.org || [https://tools.ietf.org/html/rfc6409 submissions] || 465 || Email relay (SMTP with SSL, password authentication required)
|}

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

* postmaster AT sugarlabs DOT org

== Sysadmins ==

* [[User:Bernie|Bernie Innocenti]]
* (add yourself here if you tend to the postmaster [[Machine/rt|RT]] queue)

== Notes ==

* Users with a Sugar Labs [[Service/shell|shell account]] on [[Machine/sunjammer|sunjammer]] can use our SMTP relay for personal email submission. ''Any abuse will be prosecuted.''

* The [https://tools.ietf.org/html/rfc6409 submissions] port (465) is preferred for email relay. Unauthenticated and unencrypted connections are not allowed to relay.

* All email originating from the sugarlabs.org domain must be submitted through our SMTP server. '''Failure to do so may result in your email being blocked by spam filters.'''

== SPF ==

Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] records.

You can add an spf record in the zone file in the form

hostname TXT "v=spf1 redirect=_spf.hostname.sugarlabs.org"
_spf.hostname TXT "v=spf1 ip4:IPv4_of_hostname/mask ip6:IPv6_of_hostname/mask a:hostname.sugarlabs.org mx:hostname.sugarlabs.org ~all"

The '''a''' and '''mx''' values are authorized mail server by domain name and authorized server by domain MX record, the MX record should also be defined
for hostname.

Also maintain spacing and formatting for each section you add in the zone file.

== DKIM ==

Our domain publishes a [http://en.wikipedia.org/wiki/DKIM DKIM] key.

To test DKIM, send an email to autorespond+dkim@dk.elandsys.com

To generate an ed25519 key to use for DKIM, you can use openssl

# Generate ed25519 key
$ openssl genpkey -algorithm ed25519 -out dkim_private.pem
# Generate public key from private key
$ openssl pkey -in dkim_private.pem -pubout -out dkim_public.pem

For ed25519 keys, the p value in the DKIM record must only contain the BASE64 encoded public key, without an ASN.1 structure

$ openssl asn1parse -in dkim_public.pem -offset 12 -noout -out /dev/stdout | openssl base64
VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo=

Your entry would look like this

default._domainkey.hostname TXT "v=DKIM1; g=*; k=ed25519; p=VGhpcyBpcyBqc3V0ZSBhc29ka2ZvYXNrZWpkZmtsc2pkZgo="
_adsp._domainkey.hostname TXT "dkim=unknown"

Ensure your private key is on hostname and specify the path to it when using a tool like opendkim - /etc/opendkim.conf -, with
the user and group of the key being opendkim.

== See also ==

* [[Service/imap]]
* [[Service/webmail]]
* [[Service/email]]

[[Category:Service|imap]]