The best starting points for this would be the iproute2 man page [1], superuser [2] and serverfault [3]. There are potentially also Linux namespaces to consider. There are also some youtube videos that can walk you through the 'ip' command and debugging routes. Start with "debug route linux iproute2" in their search. That's a topic probably too big for HN I think. [1] -... - Source: Hacker News / 12 months ago

See the link to serverfault.com above, that seems the closest advice so far but too early to tell. Source: over 1 year ago

I would but the guys here are a bit lazy so I thought of a script - this is from serverfault.com so I need to change the security descriptor to modify. Source: over 1 year ago

Fundamentally, "dev" and "ops" require different skillsets. Dev experience does not translate to ops. An experienced "ops" might be able to rootcause an issue by pattern matching its markers to previous experience. A green "dev" is just that, green, and will usually operate with the handicap of a huge learning curve ahead. Sites like https://serverfault.com make it a bit easier to poke around, but are not a... - Source: Hacker News / almost 2 years ago

Well, there is https://serverfault.com/ for that, which uses the same stackexchange engine. Source: almost 2 years ago

I'm pretty sure, you'll find companies like this one which provide a nice GUI for helping with l10n or this one which offers translation services or this page that offers to convert between different formats, one of which probably has a nice GUI tool. Found them by 20 secs of googling. Source: about 1 year ago

Localise has no problem reading the json files or export to json, we recently started using it in collaboration with external translators. Source: about 1 year ago

Actually I don't have "my" app. But in our app we use https://lokalise.com/ to localize it even to Norwegian. Our team is not the most expensive company in the world btw. And we don't have 1B+ users all over the world. Source: about 1 year ago

Internationalization (i18n) pain for a documentation project is a process problem, not a feature gap. Documentation frameworks are not meant to translate your developer docs for you into the language of your choice. Some frameworks might offer i18n support, like the Crowdin support in Docusauraus v2. With Jekyll, you have to pick a theme like this one. I doubt if the reST or adoc frameworks would differ much from... - Source: dev.to / over 1 year ago

I've been thinking about building a micro saas very similar to this after having so many issues coordinating the localization of several products I manage. The only robust options in the market are incredibly expensive (for example https://lokalise.com/). Source: almost 2 years ago