Why someone keeps chasing the latest gadgets when the old ones work just fine is beyond me.
Nobody is waiting every year for the brand new line of washing machines. Why is there a need to swap phones this frequently?
Other places where you can find me
Why someone keeps chasing the latest gadgets when the old ones work just fine is beyond me.
Nobody is waiting every year for the brand new line of washing machines. Why is there a need to swap phones this frequently?
I imagine it wouldn’t take long until someone finds a way to disable that LED.
Yes the interface is a mess. But it’s ridiculously deep once you get into it.
The CEO of Unity was also CEO, COO, and president of EA. So, is anyone surprised?
Or even better: buy soon to expire put options just before the announcement. 10x your money.
You’re welcome!
I can have a look in my free time for fun. Will let you know if I manage to do it. 😅
Damn… that’s rough.
Hopefully they’ll backpedal on this decision for now (they are already getting a lot of flack). But I guess the message has been sent. Wouldn’t be surprised if Unity starts bleeding users after this.
Best of luck!
For the studios releasing a game in a few months, it’s probably too late to ditch unity, but would make sense to start looking at alternatives for their next projects.
Wouldn’t be surprised if Godot explodes in popularity in the next 5 years.
According to the article, it’s not retroactively charged, but still bad if your game is about to come out and you haven’t accounted for this.
The margins on the gamedev industry are not that large, you should read some testimonies from veterans. It’s a ruthless industry.
Games take years to make, and you can’t change engines now if your game is about to come out.
Sorry for the delay in the reply.
No need to apologize! Thank you for working on this. :)
The only issue is that the app requires that the config file and blocklist and allowlists should be included within the docker hub. So the issue is that if a prebuilt image is provided, then is it possible to edit it within the docker container ?? If so then it is ok, otherwise it would still be good, but it would limit the usage to users who are by default satisfied by the default config. While others would still need to build the image manually, which is not very great.
I’m not familiar with the websurfix codebase, but I don’t see why it wouldn’t work.
I’m currently self-hosting SearXNG on a VPS, but I started by having it just locally. The important bit of that blog post is this:
docker run -d --rm \
-d -p 8080:8080 \
-v "${HOME}/searxng:/etc/searxng" \
-e "BASE_URL=http://localhost:8080/" \
searxng/searxng
I use the -v
flag to mount a directory in my home to the config directory inside the docker container. SearXNG then writes the default config files there, and I can just edit them normally on ~/searxng/
.
By using a mounted volume like this, the configs are persistent, so I can restart the docker container without losing them.
Ah cool, thanks!
Will definitely try it now. It’s good to have options (Searx just recently became unmaintained).
Are there any plans to have an official docker hub image? I’m asking because my workflow involves keeping the containers up to date with watchtower.
Genuinely curious, what would the advantages be?
Also, what if the Linux distro does not have systemd?
Yes.
All my self hosted containers are bound to some volume (since they require reading settings or databases).
True.
But I assume OP was already running docker from that user, so they are comfortable with those permissions.
Maybe should have made it clearer. Added to my other post. Thanks!
Interesting, I’ll be keeping an eye on this. Thanks for sharing!
I’m currently self hosting SearXNG. The must-have features for me are the custom filters and the actively maintained docker image. Will definitely give it a go if they get implemented.
You shouldn’t need sudo to run docker, just can create a docker
group and add your user to it. This will give you the steps on how to run docker without sudo
.
Edit: as pointed out below, please make sure that you’re comfortable with giving these permissions to the user you’re adding to the docker group.
For the littering part, just type crontab -e
and add the following line:
@daily docker system prune -a -f
Someone should keep an eye on Linus.