veloren VS watchtower

I know that code.org's lessons have a "view the real code" box, helping to ease one into the "here's how to think about problems and structure, but here's the actual JavaScript that underpins it". If you haven't tried that, it may help

I also recently learned that Brilliant uses block-based lessons, too, so there's obviously some there-there

I would guess that a lot of the problem is one of actualization: how does one go from solving "someone else's problems" to one of realizing their own ideas. Based on what I've seen, I'd guess that a Minecraft mod port that maps blockly down into lua would go a long way toward "do some things that materialize change in an environment that is familiar." I haven't used Roblox, but I believe it's similar so if they have a programming language, same-same. I started to suggest using Valoren <https://gitlab.com/veloren/veloren#get-veloren> since it's actual FOSS and thus would be much, much easier to integrate into, but I haven't played it in order to know how much uncanny-valley it would have with any preexisting Minecraft experience

Games (Veloren, or check out this website for updates on other games being developed in Rust)

Firstly, it's open-source. That means that all code associated with the project is freely available (it's right here!) and you're welcome to download, modify, recompile, and make changes to it as you wish. In fact, there have already been a few forks of the project that added new items, abilities, bosses, and other such things. Veloren is also released under GPL v3, a license that pretty much ensures that the code will always be open-source, meaning that anybody can take the existing code and remix it, mod it, or otherwise build upon it.

I found this on the gitlab https://gitlab.com/veloren/veloren/-/issues/1755

sounds like a wayland issue, can you check our https://gitlab.com/veloren/veloren/-/issues list and if you dont find this error, you could help us by opening a bug and giving it a good description: Maybe there is even a workaround in our book:

Trying to replace C with something like Rust, is essentially saying that we should rewrite all kernels in Rust. C is the common language because it talks to the kernel, which talks to the hardware.

Forgetting how much would need to be replaced with objectively much slower code, Rust simply cannot do some things. You cannot always make absolute guarantees about memory safety for example when it comes to low-level programming. Sometimes to be fast, you have to make assumptions and take risks.

I am currently watching the Veloron game [1] as an example of how larger Rust projects may begin to look. I see something like this [2] and it doesn't look all dissimilar from C, just with a new syntax. Has writing this game eliminated all bugs? Nope [3]. Maybe there are less segfaults and bad memory management, but this was just one class of bugs.

[1] https://gitlab.com/veloren/veloren

[2] https://gitlab.com/veloren/veloren/-/blob/master/server/src/...

[3] https://gitlab.com/veloren/veloren/-/issues/?sort=closed_des...

Oh dang, looks like it's open source too. licensed under GPLv3 - https://gitlab.com/veloren/veloren

It's really amazing to see how Veloren has improved over the years. Makes me wonder what we'll see in the future. I was really surprised when I saw the train tracks merge request 😄

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!