And I thought FF containers were great! FF have their problems but always good to see where priorities are.
eternaldeiwos
joined 1 year ago
Depends on how you're currently set up. My intention was to use something like k3s + https://cloudnative-pg.io to handle most of the details for me.
I prefer to version my configs so this approach serves my MO better, even if it is a little more work initially.
Personally I would go with /c/csharp to keep the community on-topic. Could also easily have /c/fsharp et al. That said I probably won't subscribe to those.
/c/loud on the other hand I would definitely prefer to be /c/cloud to prevent the inevitable 🤨 when mentioning inline.
This is not a bad idea. This is how the Fediverse is supposed to work.
I responded in your DB optimization thread as well but can you share the improvements you made?
As with /c/sharp making a cool URL is one thing but this would be referred to inline as !loud
The URL might be /c/sharp but it would be referred to inline as !sharp.
Could you share what you did? pgbouncer and a much larger pool of available connections comes to mind.
Set up my instance to come here to report that I am not lurking o7
Was reading about this earlier, in theory they are fully compatible but Kbin’s implementation is better.
I was unable to successfully subscribe to the same magazine as you tried.
view more: next ›
Microsoft aren’t exactly big on implementing “the latest” stuff. Not at a keyboard currently but I’d be willing to bet GH doesn’t support TLS1.3 either.