docker re:dash's database init should not rely on the tool used to manage the re:dash's container

[gissehel]

The philosophy behind "not putting postgresql into containers", is to let you use any postgres server (either one dedicated to re:dash within a docker-compose, or one already used for other databases on your infrastructure).

The fact that, in order to init the database, you HAVE to use docker-compose doesn't provide that flexibility having postgres outside of the container should bring you.

[gissehel]

I'll try to make something else based on the current image.

The best way would be to have an init script into the redash image that can be called the first time instead of supervisor.

The problem:

• It would require to have psql installed on the redash image, and it's not.

The possible solutions:

• Install psql on the image
  • pro: Simple only 1 image
  • con: Install psql while not needed except for once for init
• Use an "init redash" image, that derive from the redash image and that contain psql.
  • pro: The init database use a container that launched with barely the same configuration that the redash image
  • con: Need one more image
• Don't use psql and use python script to execute basic queries
  • pro: Simple only 1 image, no big useless installation, just small python script
  • con: May be a bit more complex to write (have no idea what modules are installed)

[gissehel]

I'll try to make a POC for the 3rd or the 2nd solution.

[arikfr]

You have a very good point. I like the 1st and 3rd solution. The 3rd should be quite easy to implement considering that Python used for the largest chunk of that script (creating tables).

[gissehel]

pull request #629 implement the 3rd solution.

[arikfr]

Fixed in #1530.