Page 1 of 1
Waptserver: Development
Published: May 22, 2018 - 2:01 PM
by Aguay
Hello,
I tried launching the WAPT server in development mode. There are a lot of hardcoded paths, some custom methods, etc., and I thought there might be a trick.
Do you have any documentation or tutorials for launching the server in development mode?
Thanks in advance!
Re: Waptserver: Development
Published: May 22, 2018 - 3:53 PM
by dcardon
Hello Aguay,
Aguay wrote: ↑May 22, 2018 - 2:01 PM
I tried to launch the WAPT server in development mode, there are many hardcoded paths, some custom methods etc., and I thought there might be a trick.
For your information, development is primarily done on Windows with a WAPT path in c:\tranquilit\wapt... This is neither the new standard path (c:\program files\wapt) nor the old one (c:\wapt, which also works), and in fact, you can install WAPT 1.5 pretty much anywhere you want (there was a bug in the past when it was installed on a different drive) as long as it's based on a drive letter (C:, D:, etc.). Indeed, I don't believe UNC paths are supported everywhere in the configuration, however.
So saying that there are hard-coded paths is in my opinion a misinterpretation... As for custom methods, yes the code to properly manage installations under Windows is not trivial, but it remains quite clean, Hubert is constantly refactoring.
Aguay wrote: ↑May 22, 2018 - 2:01 PM
Do you have any documentation/tutorials for launching the server in development mode?
I don't think we have that, but if you'd like to write one, we'd be happy to include it in the overall documentation.
Sincerely,
Denis
Re: Waptserver: Development
Published: May 23, 2018 - 3:59 PM
by Aguay
Thank you for the quick reply!
So, is it not possible, or only with greater difficulty, to launch the WAPT server in development mode under Linux?
Aguay
dcardon wrote: ↑May 22, 2018 - 3:53 PM
Hello Aguay,
Aguay wrote: ↑May 22, 2018 - 2:01 PM
I tried to launch the WAPT server in development mode, there are many hardcoded paths, some custom methods etc., and I thought there might be a trick.
For your information, development is primarily done on Windows with a WAPT path in c:\tranquilit\wapt... This is neither the new standard path (c:\program files\wapt) nor the old one (c:\wapt, which also works), and in fact, you can install WAPT 1.5 pretty much anywhere you want (there was a bug in the past when it was installed on a different drive) as long as it's based on a drive letter (C:, D:, etc.). Indeed, I don't believe UNC paths are supported everywhere in the configuration, however.
So saying that there are hard-coded paths is in my opinion a misinterpretation... As for custom methods, yes the code to properly manage installations under Windows is not trivial, but it remains quite clean, Hubert is constantly refactoring.
Aguay wrote: ↑May 22, 2018 - 2:01 PM
Do you have any documentation/tutorials for launching the server in development mode?
I don't think we have that, but if you'd like to write one, we'd be happy to include it in the overall documentation.
Sincerely,
Denis