There is no easy way to know what port snapweb is listening to
Bug #1608572 reported by
Ara Pulido
This bug affects 7 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
After installing snapweb in a snappy system, there is no easy way (i.e. user friendly) to know what port snapweb is listening to.
Ideally, after installing, a message to the user should indicate where to go to open snapweb.
As a minimum, the port the service is listening to should be available in the system logs when the service is started.
| Changed in snappy: | |
| status: | New → Confirmed |
Revision history for this message
| Leo Arias (elopio) wrote | #1 |
| Changed in snappy: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → High |
| importance: | High → Medium |
| affects: | snappy → snapd |
To post a comment you must log in.
This affects all the web service snaps. You install them, then you have no idea of what to do next.
This is true for debs too, but I guess we can do better?
The port is a value that should be configured. Previously, snappy config printed all the values, so maybe this will be solved when we get back the config.
But the config usually prints a lot of things. We used to have snaps with multiline config values that polluted the output.
What about offering the chance to print something after the snap was installed? The URL to open to interact with the snap, a small README, a warning of the insecure bits if the snap is still devmode, a link to the website with full docs, or the indication of the interfaces that the user should connect to get the snap fully working.