Hansie211

joined 1 year ago
[–] [email protected] 9 points 2 days ago (5 children)

Exactly. If it’s true, it’s horrific—but it would also be incredibly easy to mistranslate these words on purpose.

[–] [email protected] 1 points 3 months ago* (last edited 3 months ago)

It should work that way. If you use the recommended Docker Compose scripts for immich, you'll notice that only a few volumes are mounted to store your data. These volumes don't include information about running instances. If you take snapshots of these volumes, back them up, remove the containers and volumes, then restore the data and rerun the Compose scripts, you should be right where you left off, without any remnants from previous processes. That's a pro of container process isolation

[–] [email protected] 5 points 3 months ago (1 children)

Your description of the problem makes sense. If you think improving the user experience in this way is worthwhile, then go for it. Just remember, most users don't pay attention to the address bar.

For implementation, I suggest creating a new table, something like 'tb_user_category_index,' with userId as a foreign key and an integer that increments each time it's used. Automating this process in the database would be ideal: set it up once and let it run on its own, keeping things simple.

However, don't confuse this cosmetic index with a primary key. The primary key should only serve as a unique identifier for a record and hold no other information.

[–] [email protected] 1 points 4 months ago

Did you ever find a solution? I'm on mobile, and the Pastebin formatting is a bit off, so I can't read the compose file very well. However, I suspect the error is related to this line:

24 # - WEBDRIVER_URL=http://browser-chrome:4444/wd/hub

Since a colon (':') is used to indicate a volume, it makes sense that the error is about a missing volume. Try wrapping the line in double quotes like this:

24 # - "WEBDRIVER_URL=http://browser-chrome:4444/wd/hub"

to see if that fixes the error.

[–] [email protected] 1 points 4 months ago

You are correct. Its quiet a find but I can reproduce this. I suspect the issue lies in the piece of code that tries to make sure you don't get the same animal twice when you select a random animal. You can also follow the steps until there is only the Newt and then press the dice below it's name. Now there are no animals.

The random selector subtracts one from the total options and adds that one back if the new number is greater or equal to the precious number. So in case of only a single option it gets 0 at random, which equals the previous index and does +1, which doesn't exist.

There should be a failsafe that prevents this logic if there is only one animal in total 🤷‍♂

 

Hey everyone!

I wanted to share a little side project I’ve been working on: a Planet Zoo Animal Picker. It’s a simple tool designed to help you choose a random animal for your Planet Zoo game.

I know there are already tools out there, and mine isn't necessarily better, but it's something I created and I’m proud of it. It's just a fun little project I wanted to share with the community.

It's written in Vue/Quasar, src

Feel free to check it out, and for anyone that plays the game: Happy zookeeping! 🦁🐘

[–] [email protected] 5 points 4 months ago (1 children)

Not sure what your question is or how people will respond, but in my opinion, asking for advice from someone with more experience isn't as shameful or 'dumb' as you might think.

[–] [email protected] 3 points 5 months ago (1 children)

I have no knowledge of this specific issue but 403 means unauthorized and the "Just a moment" response is usually because the server sends a JavaScript challenge to verify that you are a 'real' browser/user. It's an anti bot verification and you're not passing.