in reply to Cross-platform GUI for UNIX based scripts

Hi,

All the above are pertinent for your problem. The solution you choose depend on the user population you address. I am realizing tailor made application for companies and chose the web-application solution.

Depending on the user population I use JavaScript to improve the user experience. If the user population is made of professionals I validate the data only on the server and do not use JavaScript for this purpose. This lowers the development costs.

My solutions base on:

A good part of my web-app page set up is listed here http://www.perlmonks.org/?node_id=1029920.

The back end of you application can be provided either by the PERL native functions, various PERL modules (i.e. File::Copy) or by the PERL system() instruction (watch your steps with this!).

Hope it helps

K

The best medicine against depression is a cold beer!
  • Comment on Re: Cross-platform GUI for UNIX based scripts

Replies are listed 'Best First'.
Re^2: Cross-platform GUI for UNIX based scripts
by Anonymous Monk on May 24, 2013 at 10:04 UTC

    After reading all the comments I am straying towards your solution as I have experience in web design.

    The server I am currently working on is a secure, proxied one. In your approach do you create a webpage on the server that users connect to through their desktop browser (providing the password etc. if needed)?

    I was thinking about a website that initiates the software after which the user can log off. When logging back the user can see the progress or if the process is done, the results. I don't think it would be difficult to set up?

    Thanks for your advice, it's really helpful.

[reply]

      Hi

      First notice that my solution need a higher development effort than some other listed here. I would recommend to create the web app on an other server for security reasons. You should have a look at the SSL modules on CPAN to pass the UNIX command to the target server.

      I would authenticate the user to the web app with CGI::session and use an PK system to authenticate the web-app to the target server. Eventually jail the account you are using on the target server. Keep the validity time of the cookies of CGI::session short to avoid session theft as far as possible.

      Once the user is authenticated I would prepare the UNIX command on the web-app server and pass it to the UNIX server with SSH. If you build a good system (i.e. PERL best practice!) you will be able to reuse the web-app for several UNIX servers.

      PS: Never assume a user will log out. Keep the validity of the session short. I use for example 10 minutes for a login screen.

      K

      The best medicine against depression is a cold beer!
[reply]
        Thanks, I will keep your advice in mind when developing!
[reply]

In Section Seekers of Perl Wisdom