At Nasqueron, I maintain this Phabricator instance, and overview the operations infrastructure.
Website: https://www.dereckson.be/
Individual board: User-Dereckson
At Nasqueron, I maintain this Phabricator instance, and overview the operations infrastructure.
Website: https://www.dereckson.be/
Individual board: User-Dereckson
19:21 < Yousra> Dereckson router-003: IP= 178.32.70.111/30, en fait .111 c'est la broadcast
Copying from Discord:
Clean and straightforward.
This task should be clarified.
We've some work on the wiki too:
https://agora.nasqueron.org/index.php?search=master&title=Special%3ASearch&go=Go
The default branch is master, as that was one of the main use of my remote delete script when we switched repositories to main branch.
Note to spawn process was traditionally the TC2 role. That could clearly benefit of T2228.
So I’d suggest we hold off on adding any donation call-to-action for the moment.
Deployment wasn't up-to-date and families configuration for Agora was missing, that's why fallback was on testwiki.
Yousra asked on #nasqueron-ops22:24:01 < yousra> Dereckson Je me disais que, dans la configuration actuelle, router-004 ne serait utilisé qu’en cas de panne. En fonctionnement normal, une des deux
machines resterait donc presque inactive. Je trouvais que se serait plutôt bien que les deux routeurs travaillent en permanence tout en gardant la redondance.
22:24:02 < yousra> Mais comme on n’a pas vraiment plusieurs VLAN ou réseaux distincts, je ne suis pas sûr que la topologie actuelle permette cette répartition. Est-ce qu’on > pourrait quand même optimiser ça d’une certaine manière ?
Deployed
Reviewed TC2, there are opportunities to start jobs from #nasqueron-ops but current content is out-of-date, so not in scope for that migration.
shebang
rm space-sum
New files
Known issues:
(this version of Channel.tcl is currently live on Libera Daeghrefn bot)
Just a note there is no need to maintain a dictionary between target domain and extractor args: