Hi All, The docker container created for Hop web currently is as simple as it can get. It is a default tomcat and we have not really exposed any of the options available both for build and for runtime.
One of the things we can add at build and/or runtime is an option to set the session timeout, default is 30 minutes and it's probably set to that value at the moment. We can also add other variables like url/port configuration, where the environments are and so on... That being said, an autosave option that keeps the current working version separately would be awesome both in the regular client as in Hop web. I think we've all run into situations where the application freezes because you want to do a preview or test a connection and you forgot to save your changes beforehand. Then we could ask on restart to "recover" the current working version. Cheers, Hans On Fri, 18 Jun 2021 at 10:34, Matt Casters <[email protected]> wrote: > Hello Hops, > > Over the past couple of weeks we've slowly been fixing the last remaining > (glaringly obvious) bugs in Hop Web and I think we now have full functional > parity on Windows, Linux, OSX and Web. > > That being said, there are particular challenges which still remain for Hop > web. The first and most important issue is IMO a session timeout and the > loss of work. > I've documented possible solutions in HOP-2966 > <https://issues.apache.org/jira/browse/HOP-2966> and I would appreciate it > if you could offer other ideas to fix this issue. Can we make the timeout > configurable? > Please continue to test the latest versions of Hop Web. It's easy with > these commands: > > *docker pull apache/incubator-hop-web:1.0-SNAPSHOT* > *docker run -p 8080:8080 apache/incubator-hop-web:1.0-SNAPSHOT* > > Thanks in advance for your input. > > All the best, > Matt > -- > Neo4j Chief Solutions Architect > *✉ *[email protected] >
