Tranquil IT Forum

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

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.

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 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)
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.

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.

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...)
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.

For those wondering why keep the Windows server, it's simply because we want to keep the WAPT graphical console on the server.

The console can be launched on any Windows machine, provided that access to the private signing key has been configured.
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.