Login

Recent searches

No recent searches

Search options

Not available on mastodon.xyz.
mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

817
active users

mastodon.xyz: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#configuration

2 posts2 participants0 posts today
Public *
Rémi Remouk

🗒️ Allouée, mémoire allouée

Augmenter la mémoire allouée à PHP, dans une config blog WordPress derrière un serveur nginx :

  1. Afficher les messages d’erreur dans WordPress :
    • dans wp-config.php
      • WP_DEBUG à true
      • WP_DEBUG_DISPLAY à true
  2. Trouver le fichier de conf nginx correspondant :
    • /etc/php/8.3/fpm/pool.d/nom_du_site.conf
    • /etc/init.d/php/8.3/fpm/pool.d/nom_du_site.conf
  3. Changer la valeur de :
    • php_admin_value[memory_limit]
  4. Redémarrer le service :
    • /etc/init.d/php8.3-fpm restart

* 8.3 numéro actuel de la version de PHP

#adminSys#configuration#serveur
Public
C.

Guide to Interpreting Security Incident #Announcements:

"extremely sophisticated attack" : The attackers put more time into the attack than we spent designing our defences.

"no evidence customer #data was accessed" : We lack audit records and the logs have been rotated out.

"due to a misconfiguration issue" : We deployed with default #insecure settings.

"possible for only a short window" : We didn't dig too deep to determine how far back the bug existed.

"crafted invalid request data" : We forgot to add input #validation.

"supplementary fix" : We didn't understand the problem as well as we thought, so our previous fix was insufficient.

"may have been exploited" : We're positive they got away with data, but they deleted our #logs.

"multiple threat actors" : Everyone was in our systems before we noticed.

"most customers are unaffected" : There are corner cases that aren't as #vulnerable.

"error in a third-party component" : We forgot to update our dependencies.

"could lead to remote code execution" : You're #p0wned.

"malicious activity has been observed" : The issue has already appeared in the press.

"review equipment inventory to verify if devices require other mitigations" : You need to buy new stuff.

"remotely exploited to allow authentication bypass" : We forgot to require #login for this function.

"not aware of any exploits in the wild" : The attackers aren't bragging on darkweb fora yet.

#InfoSec#security#incident
Public
Soh Kam Yung

I may apply some of these configurations.

"In this post, I’ll go through some of the perhaps obscure Git config settings that I have personally globally enabled and go into them to explain what they do and why they should probably be the default settings.

Also, it turns out that I learned most of these from the people who actually work on the core Git codebase every day."

blog.gitbutler.com/how-git-cor

GitButler · How Core Git Developers Configure GitWhat `git config` settings should be defaults by now? Here are some settings that even the core developers change.
#Git#Software#Configuration
Public
adingbatponder

#Settings in #reticulum #meshchat #reticulummeshchat #rns for #lora #radio #mesh Always set your stationary / radio #rnode #rnodes to be #gateway nodes (#interfaces) for effective #routing in your #mesh. See Sect 6.14 of rns #reticumlumnetworkstack manual
reticulum.network/manual/Retic
(and of course always also as #transport node else message packets from other nodes won't spread) Set the settings in the #configuration file or #update the #meshchat program now & set to gateway in the settings menu.

image of relevant part of rns manual: the default mode is full. In this mode, all discovery, meshing and transport functionality is activated. • The gateway mode (or shorthand gw) also has all discovery, meshing and transport functionality available, but will additionally try to discover unknown paths on behalf of other nodes residing on the gateway interface. If Reticulum receives a path request for an unknown destination, from a node on a gateway interface, it will try to discover this path via all other active interfaces, and forward the discovered path to the requestor if one is found. If you want to allow other nodes to widely resolve paths or connect to a network via an interface, it might be useful to put it in this mode. By creating a chain of gateway interfaces, other nodes will be able to immediately discover paths to any destination along the chain. Please note! It is the interface facing the clients that must be put into gateway mode for this to work, not the interface facing the wider network (for this, the boundary mode can be useful, though)
Public
kalvn

Un guide complet et quasi exhaustif sur `tsconfig.ts` qui sert à paramétrer TypeScript.

🔗 2ality.com/2025/01/tsconfig-js

2ality.comA guide to `tsconfig.json`I never felt confident about my tsconfig.json. To change that, I went through the official documentation, collected all common options, and documented them in this blog post: This knowledge will enable you to write a tsconfig.json that is cleaner and that you’ll fully understand. If you don’t have the time to read the post, you can jump to the summary at the end where I show the tsconfig.json that I use now – along with recommendations for adapting it to different use cases (npm package, app, etc.). I also link to the tsconfig.json recommendations by several well-known TypeScript programmers. (I went through them when I researched this post.) I’m curious what your experiences with tsconfig.json are: Do you agree with my choices?
#typescript#configuration
ExploreLive feeds
About