Honestly I would describe it as Ark-lite. It has base building/taming and that’s pretty fun, and you can also get random encounters at your base. The leveling system is a bit grindy. There are dungeons and bosses in the world to go find and explore. The map is huge, I think I’ve hardly explored a tenth of it.
Been playing about 15 hours or so and enjoyed it, but the game is definitely early access. I’ve had a number of crashes, fell through the world a few times, etc. I’d give it a month or two if that bothers you.
Based on your update you may need to bring the containers down and up to fix the database.
Sometimes when opening LinguaCafe the first time there is an error message about users database table. If this happens, just stop and start your containers again, it should fix the problem.
<span style="color:#323232;">docker compose down
</span><span style="color:#323232;">docker compose up -d
</span>
Since you’ve probably been using the SMB protocol to access the NAS you probably need to understand a few things about the NFS protocol which functions differently. The NFS mount acts like a mapping of the entire system, rather than a specific user. That means that if there are differences in the systems, you may get access errors. For example the default user in Synology has a uid of 1024, but most client systems have a default of 1000. This means your user may not have access to the share or files, even if you have it mounted on the client.
One thing to check is what your Shared Folder’s NFS permissions squash is set to. This is found in Control Panel > Shared Folder the the NFS permissions tab. If it’s set to “no mapping” then uids must match. The easiest setup is to “map all users to admin” but you may encounter issues with that later if you switch back to SMB since new files will be owned by admin.
Sounds about right, just be aware that your LAN and WAN networks need to be different, so you’ll likely need to change your old router’s dhcp subnet. E.g. 192.168.1.1/24 on the WAN and 192.168.0.1/24 on the LAN.
I have used gocryptfs (github.com/rfjakob/gocryptfs) in the past, it creates an overlay mount that encrypts each dir and file separately, so no need to precreate a container. There are some security downsides to this approach though so be aware of that. nuetzlich.net/gocryptfs/threat_model/