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!
Waptserver: Development
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Aguay,
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.
Sincerely,
Denis
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.
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
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
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,
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.
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
