Open sajiljosephs opened 1 year ago
this is for now hardcoded.
the displayed name is usually stored in the powa archivist catalog, but it's ignored for the local server.
would that field work for you if I made the UI use it? it would make things consistent but the downside is that you would need sql access to modify it with a plain update query (I plan to make stuff configurable via the UI but it will take some time to arrive).
otherwise I could add a new configuration field, like local_server_name, in the powa-web.conf file
otherwise I could add a new configuration field, like local_server_name, in the powa-web.conf file >> This should do it.
Looking at implementing it, I remembered that the local server is displayed as the connection info configured in the config file in the breadcrumb, using declared host/IP:port
. Using that everywhere rather than adding an alias may be a better option. So if you configure e.g.
servers={
'myserver': {
'host': 'production-pg',
'port': 5432,
[...]
},
'myotherserver': {
[...]
},
[...]
}
you would get production-pg:5432
rather than <local>
everywhere.
The problem with a new configuration option is that you can declare multiple servers in the config file, so a single alias would not work.
If you really want an alias rather than the host : port
, maybe an option to display the server alias in the config file rather than the undelrying host and port would work? With the above example it would display myserver
.
Need to change the instance name displayed in powa-web UI. Where should we set up this in conf ?