kelseyhightower / nocode

The best way to write secure and reliable applications. Write nothing; deploy nowhere.
Apache License 2.0
60.9k stars 4.72k forks source link

it killed my Tamagotchi! #4008

Open bohrlot opened 4 years ago

bohrlot commented 4 years ago

I've fed my Tamagotchi with it and he died. Please, help me to solve this issue

edge33 commented 4 years ago

Happened the same to me, in order to replicate I used this docker container, just pull it from dockerhub via:

Then run it:

At this point I was able to troubleshoot the issue: It is a matter of changing the environment variable as following:

And your next tamagocthi won't have the same bad luck!

Thing is that, framework is very flexible but it cannot resurrect the dead, but maybe the dev can think of this feature in the next release

bohrlot commented 4 years ago

Thank you! I gave it a try but it appears that something is still missing. I ran the following command:

and it returned this:

I guess that my new tamagotchi is vegan, because it started doing strange things like this:

and this:

I understand that the framework doesn't have the resurrection feature but I'd expect a little more flexibility with just a vegan tamagotchi. Imho, this would come very handy to the new adopters.

ST-Apps commented 4 years ago

Please keep in mind that @edge33's solution works only for some specific versions of the framework.

If you execute it with -v option, you should get an output similar to this one:

where you can clearly see if the environment variable is supported (line of the output above).

For those specific versions where the variable is supported, your line should have the suffix, meaning that your output should look like this one:

I think that this should be added to the documentation, which is clearly lacking when we talk about both vegan tamagotchi and resurrection.

@bohrlot would you mind starting a new PR for this one?

alkhachatryan commented 4 years ago

Happened the same to me, in order to replicate I used this docker container, just pull it from dockerhub via:

Then run it:

At this point I was able to troubleshoot the issue: It is a matter of changing the environment variable as following:

And your next tamagocthi won't have the same bad luck!

Thing is that, framework is very flexible but it cannot resurrect the dead, but maybe the dev can think of this feature in the next release

Didn't work for me.