Hello,
I'm contacting you because I'd like to modify my WAPT architecture.
Currently, I have a Windows Server 2012 running the WAPT server (server + repository).
What I'd like to do (though I don't know if it's possible) is keep my WAPT server on the Windows Server 2012 and have the repository on a Debian server.
Is this possible? And if so, how?
I thought changing the repository address in the "wapt-get.ini" file would be enough, but it isn't.
For those wondering why keep the Windows server, it's simply because we want to maintain the WAPT graphical console on the server.
Thank you in advance for your answers.
Luc
Repository relocated
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
For your information, I asked the same question on the mailing list because I needed a quick answer.
Here is Hubert's answer, thank you to him.
The Debian repository in your case would therefore be a "so-called" secondary repository, that is to say a replication of C:\WAPT\waptserver\repository from Windows to /var/www/ of Debian.
For access to the WaptConsole, the configuration is located in %APPDATA%\..\Local\waptconsole\waptconsole.ini
And it won't work for waptconsole (it would work with manual command-line management...) to have the main wapt repository and the wapt server (which retrieves the inventories) on 2 machines.
When you have a Debian server + repository, the waptconsole works in graphical mode on a Windows machine by launching HTTP requests to the Debian server.
Here is Hubert's answer, thank you to him.
The WAPT server must also act as a repository if you want to continue using the console. This is because the console uploads machine, group, and software packages via the WAPT server process to the local filesystem of the WAPT server (/var/www/wapt on Debian)Hello,
I'm contacting you because I'd like to modify my WAPT architecture.
Currently, I have a Windows Server 2012 running the WAPT server (server + repository).
What I'd like to do (though I don't know if it's possible) is keep my WAPT server on the Windows Server 2012 and have the repository on a Debian server.
The Debian repository in your case would therefore be a "so-called" secondary repository, that is to say a replication of C:\WAPT\waptserver\repository from Windows to /var/www/ of Debian.
This is indeed sufficient for the operation of a client workstation, provided that the Debian repository is properly synchronized with the master repository (Windows 2012 in your case...)Is it possible? And if so, how?
I thought that changing the repository address in the "wapt-get.ini" file would be enough, but no.
For access to the WaptConsole, the configuration is located in %APPDATA%\..\Local\waptconsole\waptconsole.ini
And it won't work for waptconsole (it would work with manual command-line management...) to have the main wapt repository and the wapt server (which retrieves the inventories) on 2 machines.
The console can be launched on any Windows machine, provided that access to the private signing key has been configured.For those wondering why keep the Windows server, it's simply because we want to keep the WAPT graphical console on the server.
When you have a Debian server + repository, the waptconsole works in graphical mode on a Windows machine by launching HTTP requests to the Debian server.
