There is a list_of_known_pokemon.csv maintained somewhere on the internet. It has columns "pokemon_id", and associated characteristics such as "name", "weight", "height" and "class". This list expands as more pokemons are discovered daily.
We want to create a Shiny app that will display this table. We also want the users of the shiny app to be able to indicate that we have caught a pokemon and on which date it was caught.
How should we proceed?
My current thought process would be to maintain a "data/list_of_caught_pokemons.csv" file on the shiny repo. It would have two colums: "pokemon_id" and "date_caught". If we have caught 7 pokemons so far then the file would have 7 rows.
In the shiny app, we display the result of
list_of_known_pokemon %>% left_join(list_of_caught_pokemons)
The shiny user would edit the "date_caught" column in the shiny (HOW?) to indicate a new pokemon has been caught, then press a button that would "export an updated version of 'list_of_caught_pokemons.csv', and commit it to the shiny repo"
I think that would work, but I'm afraid we might run into issues when 2+ users are using the app at the same time.
Just to clarify, that documentation is for shiny-server, not for shinyapps.io specifically, the MySQL service is not running on your app's container on shinyapps.io so you would need to host it elsewhere.
I'm pretty clear on the db commands. ElephantSQL is new to me and awesome.
What I'm not clear on how to implement is how I could display the table in a way that the date_caught column is editable (and that an edit triggers writing to the list_of_caught_pokemons in the DB).
