nyuuzyou/wikis huggingface dataset:
SAC:GitLab

GitLab is an OpenSource git hoster platform with a corporate centralized hub. See more on wikipedia
= On gitlab.com =
On https://gitlab.com/, we have an organization account created for the OSGeo Foundation, but no repository is under that name
(projects have tipically their own namespace)
A bot account exists and is used for some mirroring tasks.
You can ask User:strk if you want to know more about it
= Experimental Self-hosted instance (historical) =
An experimental deployment of GitLab has been setup at an external server (vps306914.ovh.net) which was temporarely offered by Vincent Picavet. 
It's accessible via https://git.osgeo.org/gitlab which is configured as a reverse proxy on TracSVN to the external server.
The deployment has been configured to authenticate via OSGeo LDAP which required opening it up to the remote server as announced here:
https://lists.osgeo.org/pipermail/sac/2016-August/007343.html
The deployment was made by https://wiki.osgeo.org/wiki/User:Bjornharrtell in August 2016 and the server is provided by https://wiki.osgeo.org/wiki/User:VincentP.
Category:infrastructure
Category:services
SAC:Gitea

Gitea is an instance of the Go Git Service that runs on TracSVN as part of the OSGeo Git Services.
It can be accessed via https://git.osgeo.org/gitea/ (login with your OSGeo Userid)
= Files location and configuration =
It is installed in /home/git/gitea.
Its configuration is in the custom/ subdir and controlled via ansible.
Repositories are in /home/git/gitea-repositories and all files are created as readable for any user in the git group.
Apache running user (www-data) is made part of the group to allow for browsing gitea-managed repositories via existing trac instances.
Attachment and session data are in /home/git/gitea/data.
It is configured to use LDAP for authentication and PostgreSQL as the backend, see the configuration for access parameters.
Backups are currently automated for the database and data directory via scripts in /osgeo/backup/ (start from /osgeo/backup/bacula_before.sh). No repositories are backed up (what's a distributed code version control system worth otherwise?:). Refer to SAC:Backups for other backup info.
It listens on IP 127.0.0.1 and TCP port 3001 via HTTP. Apache is configured to deal with HTTPS and act as a proxy.
See TracSVN for info about the apache configuration.
Gitea is built to be composed by a single binary.
See https://gitea.io/ for more info.
= Administration =
At the moment Sandro Santilli (promoter of the initiative) and Martin Spott have admin privileges from the web UI.
Regina Obe and Jeff McKenna are willing to help.
Server configuration is done via https://git.osgeo.org/gitea/sac/ansible-deployment
 (requires login and authorization to see)
== Starting and stopping the service ==
The service is managed via systemctl:
 - systemctl start gitea
 - systemctl stop gitea
 - systemctl restart gitea
= Continuous integration =
A CI server is associated to the hosting service,
see Dronie and Woodie
Category:Infrastructure
SAC:Heisenbridge

Heisenbridge is an IRC <-> Matrix bridge that we are running on an LXC container
hosted on osgeo3 machine and administered by the OSGeo System Administration Committee.
The bridge registers as an app service with the OSGeo SAC:MatrixSynapse homeserver.
The configuration and install of the bridge is driven by Ansible (restricted access): https://git.osgeo.org/gitea/sac/ansible-deployment
At time of writing this the running Heisenbridge version is 1.14.6
== Bridging IRC channels ==
Bridging IRC channels with Matrix rooms is a manual operation that is done by interacting with a bot Matrix user.
Only the admin user can interact with the bot, the current allowed user is set via an HEISENBRIDGE_OWNER_MXID variable in ansible, and is currently set to @strk:osgeo.org - the bot supports "help" commands to figure how to do things.
On the IRC side it is helpful to grant auto-op to the bridge user.
Bridge user on libera.chat is registered as "osgeo-matrix", and you can grant it auto-op on IRC channels with:
 /msg ChanServ flags #<channelname> osgeo-matrix +O
Granting operator status to the bot allows automatic synchronization of the IRC channel topic with the Matrix Room description.
Category:Infrastructure
Category:Services
SAC:ISO Mirroring

I think this page is obsolete
Telascience and SDSU have substantial bandwidth available for mirroring useful Open Source Geospatial software and datasets. Datasets are primarily handled by the Geodata Committee, but Software ISO mirroring is handled by SAC. 
The process to mirror an iso is to:
# Propose the ISO to be mirrored to the sac mailing list. Try to include some details on what it is all about, who it is for, what software it includes, etc. 
# Wait 2 working days for support and objections. At least two SAC members should speak up in support, and there be no objections to proceed.
# Put the iso somewhere web accessable.
# Notify John Graham (johng at telascience.org) who will copy it to: http://telascience.sdsc.edu/tela_data/foss4g/
# Notify the original requestor the mirror is active. 
# Add the item to the following list for contact purposes. 
There has also been an index.html maintained in the past, but this may be somewhat hard now that the files have to be copied by John.
= Mirrored ISOs = 
# foss4gtk.iso - Contact: Venkatesh (raghavan at media.osaka-cu.ac.jp), Details: http://wgrass.media.osaka-cu.ac.jp/foss4g
# GN_OS203.iso - Contact: Jeroen Tichler (Jeroen.Ticheler at fao.org), Details: http://tecproda01.fao.org/geofoss_dvd
# lausanneLiveCD_release_proj.iso - Contact: ?, Details: FOSS4G Conference Workshop Live CD
Category:Infrastructure
Category: Live-demo
SAC:MatrixSynapse

OSGeo hosts a Matrix homeserver reachable from address https://matrix.osgeo.org
Running version can be extracted from https://matrix.osgeo.org/_synapse/admin/v1/server_version
At the time of writing we are running server version 1.112.0 with pyton version 3.9.2
The homeserver is a federated instance of Synapse
running in an LXC container
hosted on osgeo3 machine and administered by the OSGeo System Administration Committee.
The homeserver can be currently accessed by anyone with an OSGeo UserID.
The Matrix ID for users will be @<LDAPUSER>:osgeo.org.
See section in Matrix page for how to effectively use IRC from matrix.
Configuration of the service is documented in SAC-private repository https://git.osgeo.org/gitea/sac/osgeo3/wiki/matrix-container
Trac ticket which was used to track setup of this service is https://trac.osgeo.org/osgeo/ticket/2309
As part of the matrix ecosystem we are also running an Heisenbridge (in IRC bridge)
Category:Infrastructure
Category:Services
SAC:Message Submission Agent

With this Message Submission Agent (MSA) service, OSGeo provides the ability to send emails with the @osgeo.org domain for community members. Note that this is not a full email service with an inbox to manage and store messages. 
== Prerequisites ==
* Get an OSGeo ID.
* Open a ticket in the OSGeo Trac for an admin to grant this service to your user. Remember to assign to the SysAdmin component for faster routing.
** An admin should create an alias for you in osgeo6
** An admin should add you to the shell management LDAP group
* You probably also want to receive messages so please, communicate a stable, working, email to set up a forward.
== MUA set up ==
Configure your e-mail client (Mail User Agent) with new SMTP outgoing server with the following settings (using Thunderbird terminology):
* Server Name: lists.osgeo.org
* Port: 465
* User Name: Your OSGeo ID
* Authentication method: Normal password
* Connection security: SSL/TLS
Category:Services
SAC:Migration Commands

stash of commands I'm using in the migration.
osgeo1:
 $ time for trac in `cat tracs`; do pg_dump -f $trac.dump $trac; done
 $ cd ..
 $ zip -9r db.zip trac-db
 $ scp db.zip tracsvn.osgeo.osuosl.org
tracsvn:
 $ unzip db.zip
 $ cd trac-db
 $ time for i in `cat tracs`; do dropdb $i; createdb $i; psql -f $i.dump $i; done
 $ rsync -rav trac root@tracsvn.osgeo.osuosl.org:/var/www/
Category:Infrastructure
SAC:Old-osgeo3

=== osgeo3 before transformation ===
NOTE this information is just historical of what exited before osgeo3 was reformatted.
Each of the sections below represent a Virtual Machine and describes which services are running on it, and by which name they are reachable.
==== Web ====
*** TURNED OFF 2019-11-01 and containerized on osgeo7***
* Drupal instances for the main OSGeo web site and projects like MapGuide and FDO are hosted here (??). DEFUNCT- moved to wordpress on osgeo7 wordpress container
* Virtual Hosts (on same server)
** http://fdo.osgeo.org
** http://mapguide.osgeo.org
* LDAP Python Admin Scripts in /usr/lib/cgi-bin - accessed via https://id.osgeo.org (this current reside on osgeo7 lxd container called old-web)
See Infrastructure Transition Plan 2010#Final_Plan for full details.
* Infrastructure Transition Plan 2010#osgeo3_.26_osgeo4
* Lots of config information in the Migration Documentation.
==== TracSvnGit ====
**Moved to osgeo7 **
See TracsvnVM for full details, and some notes on services running here
* SAC:Backups describes backup strategy.
SAC:Primary Administrators

This page documents what a Primary Administrator is, and who they are. 
Primary Administrators are those people who have been given the highest level of access to OSGeo system resources. This is a position of substantial trust and responsibility. Primary Administrators are provided with:
* account information for the OSGeo DNS account at Pairnic. 
* LDAP Password for primary LDAP repository
The following individuals are Primary Administrators and have access to this information. If they don't know the info, they should contact another primary administrator for details, and keep it somewhere off the main server so they can get to it in an emergency!
* Shawn Barnes: +1 613.565.5056 - Ottawa/CAN business hours - timezone GMT-4
* Frank Warmerdam: +1 650.701.7823 - anytime (all incl. UPS reboot)
* Howard Butler: +1 515 708 0858 IRC (UPS reboot)
* Martin Spott: +49 172 2019167 - timezone (GMT +1)
* Wolf Bergenheim: (Drupal) +358-41-5176362 - timezone GMT+2
* Markus Neteler: +49 228 387 580 80 business hours - timezone GMT+1
* Alex Mandel - timezone GMT-7
* Sandro Santilli - timezone Europe/Rome GMT+1 / GMT+2
* Regina Obe - +1 617 227 3636 timezone USA/Boston UTC-5 / UTC-4
* Jürgen Fischer - +49 4931 918 175 31 business hours - timezone UTC+1
* Vicky Vergara - 52 55 2882-3716 - UTC-6
* Laurențiu Nicola
=== Other Admins of Note ===
* Arnulf Christl: (Mediawiki)
* HyperJohnGraham: (Telascience)
=== IRC channels ===
Go here to catch people:
* irc://irc.libera.chat#osgeo-sac (see IRC)
* https://matrix.to/#/#sac:osgeo.org (see Matrix)
Category: Infrastructure
SAC:SSLCert

On most VMs we run the following configuration for using SSL certificates with Apache and its vhost config files:
 SSLCertificateFile /etc/ssl/certs/STAR_osgeo_org.crt
 SSLCertificateKeyFile /etc/ssl/private/osgeo.key
 SSLCACertificateFile /etc/ssl/certs/COMODOHigh-AssuranceSecureServerCA.crt
For LDAP authentication put the following into '/etc/ldap/ldap.conf':
 TLS_CACERT /etc/ssl/certs/COMODOHigh-AssuranceSecureServerCA.crt
Category:Infrastructure
SAC:Security Groups Policy

This document is under development, and has not yet been adopted.
It is planned that a central LDAP database be used for user authentication on all (or at least most) SAC administered services. This includes items like a web site/cms, svn, shell access, wiki and so forth. Userids in LDAP will belong to one or more group determining what level of access they have to various services. 
This document describes the groups, and the types of access they imply. 
# EndUser: The lowest level of permissions. This is someone who can be identified and is allowed to do general public type stuff like edit in the wiki, subscribe to mailing lists, etc.
# OSGeoMember: A properly registered member of OSGeo. Gets to vote in polls. Should have contact information (postal address etc) on file. Otherwise essentially the same as EndUser.
# Committer_<project>: A distinct group will be required for each software project using OSGeo SVN services. Being a member of this group allows SVN commit access on that projects repository.
# Shell: Someone allowed shell login access on low security systems. This would be given out on an as needed basis to software developers, committee folks, and so forth so people can do testing, setup cron jobs, etc. 
# Administrator: Someone allowed shell access, and sudo priviledges on all OSGeo systems. Some other priviledged functions, such as WikiSysop, Bugzilla admin and so forth might also be setup to use this group. This will only be provided to a tight cadre of trusted individuals. Perhaps 5-10 people.
= Notes / Issues = 
* Do we want to even further limit direct access to our most secure system (used for LDAP server primarily) to a more limited set of people? SeniorAdministrator or perhaps KeyMaster? In fact, it might be better to *not* have the LDAP's systems authentication running against LDAP in case things break, just use conventional logins for a very short list of people allowed shell access. 
* We might need a Member_<project> set of groups so that projects can limit access to some functions to folks considered to be members in their project without actually being full committers. Stuff like bug database update, etc. I'd prefer to avoid this if practical though.
= CMS Groups =
This is just to sketch out the required groups, so far, for effectively running the content management system. These overlap with the above roles, but use language that is specific to the CMS side of things:
# Anonymous: Similar to EndUser above
# Authenticated: Similar to OSGeoMember above
# Committer_<project>: Allowed to contribute content to <project>'s portion of site
# Manager_<project>: Has administrative control over a <project>'s portion of site
# Shell: Similar to above, shell login access to CMS system area
# Administrator: site-wide CMS management access
* Most of these are normal access rights: Anonymous, authenticated, administrator. The others are more complex, particularly anything to do with Project-specific content groups. 
* Need more discussion on how CMS modules can interact/authenticate against LDAP
Category:Infrastructure
SAC:Setup OCS

OCS is the Open Conference Systems software (installed on osgeo1)
* Download OCS 2.0 tarball or from CVS
* See Install README
* Save to /var/www/ocs/htdocs and create /var/www/ocs/files for uploads, etc. outside of public web access
* Copy default config to main:
 sudo cp /var/www/ocs2/htdocs/config.TEMPLATE.inc.php /var/www/ocs2/htdocs/config.inc.php
* Create httpd conf.d file /etc/httpd/conf.d/ocs.conf:
 Alias /ocs "/var/www/ocs2/htdocs"
 <Directory "/var/www/ocs2/htdocs">
 Options None
 AllowOverride None
 Order allow,deny
 Allow from all
 </Directory>
* restart httpd
* Set permissions in /var/www/ocs2/htdocs
 sudo chown apache.apache config.inc.php public cache cache/t_cache cache/t_config cache/t_compile cache/_db
* Set permissions for files upload location
 sudo chown apache.apache /var/www/ocs2/files
* Create new mysql database called "ocs", set user ocs to have full rights to the db
* Web based installer should launch now: http://www.osgeo.org/ocs/
** Set Connection and Database character encoding to Unicode UTF-8
** Change directory for uploads to /var/www/ocs/files
** Change password encryption type to SHA1
** Enter an admin account for OCS
** Enter MySQL account info, turn off "create new database" option
** Set "OAI repository identifier" to "ocs.osgeo.org"
Category: Infrastructure
SAC:Standard System Setup

This document pertains how to setup a new VM at OSU OSL. 
= Request a new VM =
A support request should be made to OSU OSL support after discussion and agreement within SAC. 
Details will be needed on the disk space, memory and the machine on which it should be established. See SAC Service Status to get a sense of the machines available and what is already running on them. The support request should be made to support at osuosl.org.
= Base VM = 
New VMs are made by cloning the "Base VM", and reconfiguring the memory and disk space. The 
Base VM is not normally running, but when it is it will be at base.osgeo.osuosl.org. When policy changes are made on how the base system should be configured for all VMs, they should also be applied to this base VM.
= First Login = 
New VMs will only allow root logins by SAC Primary Administrators with the correct ssh keys setup, but they should also support regular LDAP logins for anyone in the "sac" shell group with sudo access preconfigured for primary administrators.
= Enable LDAP = 
See SAC:LDAP for information on how the OSGeo LDAP server works. 
By default new VMs should support login by members of the "SAC" LDAP Shell group. Allowed groups can be changed primarily
by editing the /etc/ldap/ldap.conf file and modifying the line that looks like:
 pam_groupdn cn=sac,ou=Shell,dc=osgeo,dc=org
The "cn" value can be changed to other LDAP shell groups. Currently this includes "telascience" which is a very broad set of OSGeo folks suitable for shared project servers, or the "qgis" group used only on the qgis server now. 
For very secure servers (like the "secure" server) we would likely want to disable LDAP access. I'm not exactly sure how to do that.
Note that proper functioning of LDAP service also depends on having the proper SSL certificates installed as described in SAC:SSLCert. Normally this should be setup on the base vm, and copied to new VMs. 
= Setting up Backups =
... to be added ...
= Enabling munin =
... to be added ...
= File System Layout =
We typically try to put OSGeo stuff under a /osgeo directory broken down by project or service. 
= Recommended Options =
== Fail2ban ==
A tool to prevent excessive scanning for user/passwords in the system, for preventing brute force ssh logins, for catching nasty Apache requests and the like.
See SAC:fail2ban
== Awstats ==
See ? page on server usage tracking.
Category:Infrastructure
SAC:Weblate

Weblate is an instance of the Weblate server that runs in an LXD container in Osgeo9 and provides document translation servers for OSGeo community software. .
It can be accessed via https://weblate.osgeo.org/ (login with your OSGeo Userid)
= Location and configuration =
The application runs in LXD container called weblate on OSGeo9.
It is run within that application using various docker containers launched with docker compose under the account weblate.
Data is in a PostgreSQL database.
The configs are in /home/weblate/weblate-docker-compose
= Administration =
At the moment Regina Obe (creator of the container) and Sandro Santilli are admin users, although from the web UI this seems to provide no useful settings.
For maintenance and changes, administrators can access the container directly using
 ssh ldap_account@osgeo7-weblate
= Hosting your own project =
Those who want to host their own project should put in a ticket in [Ticket]
to be granted project creation permissions.
Aside from general request, how you automate weblate use within your app depends on how you are hosted.
The step generally includes:
1. Setting up a webhook in your project to notify weblate of changes:
** Gitea add in webhooks section of your project: https://weblate.osgeo.org/hooks/gitea/ (you may specify filter of branches in branch config)
** Github add in webhooks section of your project: https://weblate.osgeo.org/hooks/github/ (you may specify filter of branches in branch config)
** GitLab add in webhooks section of your project: https://weblate.osgeo.org/hooks/gitlab/ (you may specify filter of branches in branch config)
2. You can have weblate push changes to your repo in one of two ways
Directly or via Pull requests
a) Directly Giving Weblate commit access (for direct commits)
In the https://weblate.osgeo.org/settings/<your-project>/<main-component>/#vcs (replace <your-project> <your-component> with your specifics) choose Git for Version Control System 
** Gitea add ssh pubkey as a deployment key in your gitea project
** Github Invite the osgeoweblate github account to your project.
** Gitlab TBD
or 
b) via pull requests
In the https://weblate.osgeo.org/settings/<your-project>/<main-component>/#vcs (replace <your-project> <your-component> with your specifics) choose 
** Gitea choose Gitea Pull Request for Version Control System # currently this doesn't work
** Github choose Github Pull Request for Version Control System - in this model weblate creates a fork of your project under https://github.com/osgeoweblate and will create pull requests against your project with that fork
** Gitlab choose Gitlab Merge Request for Version Control System # not tested
Category:Infrastructure
Category:Services
SAC 2007 Annual Report

= Systems Administration Committee =
* Period covered by report: Jan-Dec 2007
* Contact name: Howard Butler
* Members: Howard Butler (chair), Norman Vine, John Graham, Gary Sherman, Daniel Morissette, Martin Spott, Wolf Bergenheim, Frank Warmerdam, Shawn Barnes, Who did I forget?
== Key Accomplishments ==
* Completely migrated away from CollabNet and implemented our own infrastructure, which is hosted at Peer1.
* Implemented LDAP, Trac, Subversion, Mediawiki, Mailman, Drupal, Buildbot, download server, Subversion mirror, ...
== Work Areas ==
* Remove the wildcard DNS entry for *.osgeo.org, which greatly complicates and limits our infrastructure maintenance.
* Continue migrating member projects who wish to have critical infrastructure bits like Subversion and Trac be hosted by OSGeo.
* Continue towards single sign-on goal (we have Trac, Subversion and Drupal running off LDAP, need Mediawiki, blade logins?)
* Keep the lights on...
== Outlook for 2008 ==
Category: Reports 2007
SAC 2018 Annual Report

= Systems Administration Committee =
* Period covered by report: Sep 2017 - Aug 2018
== Key Accomplishments ==
* Hosting new OSGeo website
* Purchase new hardware to replace existing
* Enabled SSL certificates for several project sites (GDAL, MapServer, GRASS, lists.osgeo.org. etc.)
* Hosting FOSS4G2018 main website on OSGeo infrastructure
* GeoForAll domains migrated to OSGeo control
* Funtoo donation of containers
* New members
* Established procedure of weekly/bi-weekly meetings
== Ongoing Tasks ==
* Containerization
* Wiki & LDAP identification merge
* Configuring Nextcloud (as dropbox replacement)
* Maintenance of lists, gitea (git ), svn, downloads, drone (for buildbot for gitea)
== Community Involvement ==
* Setup new twitter account to share service updates with community (@OSGeo_SysAdmin)
== Opportunities ==
* Looking for new contributors