Group Details Private

FAF Server Admin

The ones who must not be pinged

Member List
  • RE: What's the history of FAF?

    And this is the proper link to Lu_Xun's post https://forums.faforever.com/viewtopic.php?f=2&t=5566&start=20

    posted in General Discussion
  • RE: What's the history of FAF?

    Here is a potential starting place on the old forums https://forums.faforever.com/viewtopic.php?f=2&t=8569

    posted in General Discussion
  • RE: Open Review of FAF Moderation

    Another thing to consider from my touchpoints with the mod team is the following:
    Each case is an individual case. Especially with regards to punishment, it strongly depends on your moderation history. From first warning over last warning, from shirt ban to unlimited ban the range is huge. Many question come down to: Why do I get punished for this, but others aren't? These kind of questions lead to nowhere. The moderation will never reveal the history of a user to others and such a comparison of cases is usually pointless.

    So it makes sense to discuss the rules itself if there is a greater demand, it makes very little sense to publicly discuss individual moderation actions.

    posted in General Discussion
  • RE: 413 Payload Too Large from POST https://api.faforever.com/mods/upload

    It would be helpful if the author could upload the current folder zipped to a Google drive or somewhere.

    posted in FAF support (client and account issues)
  • The k8s journey: Milestone achieved

    Better late than never.

    With our server update 10 days ago (3rd November) we moved the last piece of the FAF production server to Kubernetes. Despite having hiccups on the migration, these were actually not relevant to the migration. From now on, we do not run anything on our faf-stack anymore.

    Looking back into experimental repositories, the first Kubernetes related commit appeared on the 1st December 2021 (and work actually started before that). That makes 3 years! 3 astonishing years of exploring, failing and succeeding. And while we were exploring options, the k8s world came up with other solutions too and we had to re-evaluate a lot.

    Time to reconsider what is in for us (admins), for developers and of course for you (the players).

    The admin benefits

    • No more logging in to the server to run updates.
    • Application state synchronized with git using ArgoCD
    • Zero-Downtime updates (except for core components such as databases)
    • Auto-updating capabilities on the git repository

    Developer benefits

    • For maintainers: New releases are automatically picked up as pull request for the gitops-stack
    • Lookup exact app configuration in git and change app configuration via pull request

    Player benefits

    • Less downtimes when deploying certain parts of the infrastructure.
    • Less work for the admins means more time for them to focus on other issues 🙂

    Downside and dark spots
    Well unfortunately the change brought some downsides that we will need to improve on in the future:

    • Higher entry barrier for developers compared to faf-stack. All documentation points to "just run a few services in Docker", but this is no longer maintained. We are working on alternative solutions with other tools (tilt.dev).
    • The faf-stack was "simple enough" to launch at least some parts of it (website, api) inside our CI pipeline and run some basic test cases like "Does registration work?". These tests could not be reproduced so far. But it's basically the same problem as for the devs.
    • Shortcuts taken: In order to get it finished faster, we commited ourselves to a single-cluster setup storing all data once again directly mounted on the host. We did the same setup on docker and it just works good. However it removes some flexibility. Yet, there is no urgent need to change this.

    In the end we can say, our journey has not ended. But the biggest milestone lies behind us and a bright future in front of us 😄

    posted in Blogs
  • RE: 413 Payload Too Large from POST https://api.faforever.com/mods/upload

    Also the problem is not the single file, but this:

    image.png

    That is 10 versions alone within 1 1/2 months eating 2 Gigabyte of disk space. Now if your uploads get bigger an bigger it would be 6GB or more if your file size keeps to grow like this... and we only have limited disk space available.

    posted in FAF support (client and account issues)
  • RE: 413 Payload Too Large from POST https://api.faforever.com/mods/upload

    And your last file was just 223mb...

    posted in FAF support (client and account issues)
  • RE: 413 Payload Too Large from POST https://api.faforever.com/mods/upload

    The maximum file size is currently 350mb. That limit was last touched 4 years ago.

    posted in FAF support (client and account issues)
  • RE: Reputation: cant write chat, cant vote

    Downvoting your post is an expression of opinion onto your statement inside a post. Nobody downvoted you directly. You are the first user who started with such negative votes 🙈

    The reputation system is there to avoid spam. I relaxed the rules for chat now for you, but you should try to avoid fishing for more downvotes 😛 .
    But "can't use forum" is obviuously wrong, how else did you post here then? So you should explain what is not working otherwise I can not help you.

    posted in Suggestions