CSCWiki - Recent changes [en]

Backups

S23adhik — Mon, 24 Aug 2026 04:40:15 GMT

← Older revision		Revision as of 23:40, 23 August 2026
Line 2:		Line 2:

	Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).		Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).

			== /users Backup ==
			/users primary is held on ranch, whilst it's backup is held on tequila via incremental zfs snapshots

			On Tequila I made a dedicated destination dataset called backup/csc0_backups (backups is a big pool);

			zfs create backup/csc0_backups

			Then on ranch I ran a snapshot, and sent it over;

			zfs snapshot -r csc0@base

			zfs send -R csc0@base \| ssh root@tequila zfs recv -F backup/csc0_backups

			In the future we need to setup incremental sends on ranch

			zfs snapshot -r csc0@snap_$(date +%Y%m%d)

			zfs send -R -i csc0@base csc0@snap_$(date +%Y%m%d) \| ssh root@tequila zfs recv -F backup/csc0_backups

	== MySQL ==		== MySQL ==

Network

R232huan — Sun, 16 Aug 2026 02:29:26 GMT

172.19.134.0/24, 2620:101:f000:4903::/64 (MC VLAN: 425)

← Older revision		Revision as of 21:29, 15 August 2026
Line 47:		Line 47:
	Gateway: 129.97.16.96		Gateway: 129.97.16.96

	=== 172.19.~~134~~.0/24, 2620:101:f000:4903::/64 (MC VLAN: 425) ===		=== 172.19.132.0/22, 2620:101:f000:4903::/64 (MC VLAN: 425) ===

	* cloud.csclub user network		* cloud.csclub user network
	* Routing restricted to University of Waterloo campus		* Routing restricted to University of Waterloo campus
	* NAT for IPv4: ~~172.19.134.254~~		* NAT for IPv4: To be implemented
	* Incoming connections over IPv6 blocked at campus firewall		* Incoming connections over IPv6 blocked at campus firewall

User:K95ma

K95ma — Thu, 13 Aug 2026 03:32:43 GMT

← Older revision		Revision as of 22:32, 12 August 2026
Line 1:		Line 1:
	Termcom ~~guy~~		Termcom person

Vaultwarden

K95ma — Thu, 13 Aug 2026 03:26:46 GMT

← Older revision		Revision as of 22:26, 12 August 2026
Line 3:		Line 3:
	You have to manually make an account by pressing 'Create Account'		You have to manually make an account by pressing 'Create Account'

	It's doesn't integrate with OAuth, or LDAP so we can't auto-create the accounts		It's doesn't integrate with OAuth, or LDAP so we can't auto-create the accounts (note: is this true? per https://bitwarden.com/help/directory-sync/ and https://github.com/dani-garcia/vaultwarden#features we should be able to set something up)

			It runs on tahini, as a docker-compose container in a [[Proxmox]] VM. To update its version, get access to it, then edit the docker-compose.yaml to the [https://hub.docker.com/r/vaultwarden/server/tags latest stable version] and pull and up:
	It runs on kubernetes

			<syntaxhighlight lang="bash">
			cd /root/docker/vault
			vim docker-compose.yaml
			docker compose pull
			docker compose up -d
			</syntaxhighlight>

Proxmox

R232huan — Wed, 12 Aug 2026 23:51:59 GMT

← Older revision		Revision as of 18:51, 12 August 2026
Line 1:		Line 1:
	The Proxmox Vitural Environment ~~(as of 2025-11-02)~~ is a cluster hosted on ~~citric-acid~~, tahini and teriyaki. The GUI can be accessed via the hostname of any machine on port 8006, e.g. https://citric-acid.csclub.uwaterloo.ca:8006.		The Proxmox Vitural Environment is a cluster hosted on sorbitol, tahini and teriyaki. The GUI can be accessed via the hostname of any machine on port 8006, e.g. [https://citric-acid.csclub.uwaterloo.ca:8006 https://tahini.csclub.uwaterloo.ca:8006].

	== LDAP ==		== LDAP ==

Matrix

K95ma — Wed, 12 Aug 2026 23:38:33 GMT

Discord: fix

← Older revision		Revision as of 18:38, 12 August 2026
(3 intermediate revisions by the same user not shown)
Line 19:		Line 19:
	We are currently running mautrix-discord. Bridge to IRC via heisenbridge may be added in the future.		We are currently running mautrix-discord. Bridge to IRC via heisenbridge may be added in the future.

	=== Discord ~~Instructions~~ ===		=== Discord ===

			{{code\|@beefbot:csclub.uwaterloo.ca}} is a Matrix account that is used to configure the actual mautrix-discord. It is logged into mautrix-discord via login-token bot (token saved, if it expires, login to CSC Exec and reset it). The login password of beefbot (the matrix account) is stored in the CSC vault on [[Vaultwarden]].

			{{code\|Matrix Bridge#7477}} is the Discord bot that reads the messages on Discord and sends them to Matrix via puppeting. It needs read access to the channels for the Discord -> Matrix part to work properly.

	* Create the Matrix channel to bridge to		* Create the Matrix channel to bridge to
	* Invite ~~{{code\|@beefbot:csclub.uwaterloo.ca}} and~~ {{code\|@discordbot:csclub.uwaterloo.ca}} to the channel		* Invite {{code\|@discordbot:csclub.uwaterloo.ca}} to the channel
			* Invite the Discord bot to the bridged server using {{code\|1=https://discord.com/oauth2/authorize?client_id=...&permissions=309774583872&scope=bot}}. client_id is found by logging in to the CSC Exec account on Discord and going to developer portal to find the ID of the Matrix Bridge bot.
	* Login to User {{code\|beefbot}} (ask syscom for password) on our matrix instance (when we eventually disable password login, you will need to edit the nix config to re-enable it)
			* Login to User {{code\|beefbot}} (password in VaultWarden, idk if there is a better place to put it) on our matrix instance
	* ''Inside'' the matrix channel, send, {{code\|!discord bridge <channel ID>}} (the channel ID on Discord, the Discord bot must be able to see that channel)		* ''Inside'' the matrix channel, send, {{code\|!discord bridge <channel ID>}} (the channel ID on Discord, the Discord bot must be able to see that channel)
	* Create a Discord Webhook URL for that channel on Discord's side, and then DM the discord bot with {{code\|!discord set-relay !26DmcJd3cQ...:csclub.uwaterloo.ca --url https://discord.com/...}} with the first argument replaced by the actual room identifier and the second parameter the webhook URL.		* Create a Discord Webhook URL for that channel on Discord's side, and then DM the discord bot (via beefbot on matrix) with {{code\|!discord set-relay !26DmcJd3cQ...:csclub.uwaterloo.ca --url https://discord.com/...}} with the first argument replaced by the actual room identifier and the second parameter the webhook URL.

Firewall

K95ma — Fri, 07 Aug 2026 03:14:07 GMT

General Use: fix wording

← Older revision		Revision as of 22:14, 6 August 2026
Line 8:		Line 8:

	== General Use ==		== General Use ==

			These ports are allowed:

	* Port 22 (SSH), plus additional SSH ports on taurine (21, 53, 80, 81, 443, 8000, 8080)		* Port 22 (SSH), plus additional SSH ports on taurine (21, 53, 80, 81, 443, 8000, 8080)

Machine List

K95ma — Fri, 07 Aug 2026 03:13:19 GMT

General-Use Servers: +

← Older revision		Revision as of 22:13, 6 August 2026
Line 32:		Line 32:

	For computationally-intensive jobs (CPU/memory bound) we recommend running on high-fructose-corn-syrup, carbonated-water, sorbitol, mannitol, or corn-syrup, listed in roughly decreasing order of available resources. For low-intensity interactive jobs, such as IRC clients, we recommend running on neotame. '''<u>If you have a long-running computationally intensive job, it's good to nice[https://en.wikipedia.org/wiki/Nice_(Unix)] your process, and possibly let syscom know too.</u>'''		For computationally-intensive jobs (CPU/memory bound) we recommend running on high-fructose-corn-syrup, carbonated-water, sorbitol, mannitol, or corn-syrup, listed in roughly decreasing order of available resources. For low-intensity interactive jobs, such as IRC clients, we recommend running on neotame. '''<u>If you have a long-running computationally intensive job, it's good to nice[https://en.wikipedia.org/wiki/Nice_(Unix)] your process, and possibly let syscom know too.</u>'''

			'''Note: [[Firewall#General Use\|firewall]] applies to these servers'''

	== ''corn-syrup'' ==		== ''corn-syrup'' ==