This is to help up “sell” the service: people can look around the demo to see whether it fits them. Of course, everyone should have the same username in the demo. We talked about having the username and password displayed above the form in the template, but i think it makes more sense to give users as little work as necessary. Plus, that means i do not have to write them down while developing. Whether the database is demo or not is not something that directly depends on the environment, but rather on which database we are connected to, thus an environment variable would not make much sense—it has to be something of the database. PostgreSQL has no PRAGMA application_id or PRAGMA user_version as with SQLite to include application-specific values to the database. The equivalent would be customized options[0], intended for modules configuration, but that would require me to execute an ALTER DATABASE in demo.sql with an specific datbase name, or force the use of psql to run script the script, because then i can use the :DBNAME placeholder. I guess that the most “standard” way is to just create a function that returns a know value if the database is demo. Sqitch does not add that function, therefore it is unlikely to be there by change unless it is the demo database. https://www.postgresql.org/docs/15/runtime-config-custom.html
Description
v1
Latest
Languages
PLpgSQL
64.2%
Go
21.4%
CSS
11.6%
JavaScript
2%
Scheme
0.7%