I made the same comment when I saw it was nominated. It’s Fallout 4 in space with both free base building (outposts) and grid base building (ships). The procedural generation of locations is reminiscent of Arena. The class system is a simpler version of Skyrim and Fallout 4. The story is cliche science fiction using mechanics from earlier Bethesda titles. The dogfights are decades old. The drudgery of running around forever for a simple objective hails back to earlier titles like Assassin’s Creed: Odyssey and similar Ubisoft map objectives.
I have no idea what Starfield innovated. It’s just like every other Bethesda game with some new things done better elsewhere. I am in the minority that love it because it is exactly what you would expect from the studio that’s been rereleasing the same game for over a decade.
This is really dependent on whether or not you want to interact with mounted volumes. In a production setting, containers are ephemeral and should essentially never be touched. Data is abstracted into stores like a database or object storage. If you’re interacting with mounted volumes, it’s usually through a different layer of abstraction like Kibana reading Elastic indices. In a self-hosted setting, you might be sidestepping dependency hell on a local system by containerizing. Data is often tightly coupled to the local filesystem. It is much easier to match the container user to the desired local user to avoid constant
sudocalls.I had to check the community before responding. Since we’re talking self-hosted, your advice is largely overkill.