Hello.
I would like to test your WAPT solution to automate our software updates.
I would prefer not to install a new machine but to use it on our existing web server.
Our web server hardware is an Intel i5 with 8GB of DDR3 RAM and a 500GB hard drive.
The operating system is Debian 8 Jessie, which already has Apache2 installed on port 80.
Our intranets are all in child directories of /var/www, so nothing is in mydomain/, but rather mydomain/myintranet.
Would this cause any problems for WAPT or my intranets?
Thank you in advance.
Best regards.
Installing WAPT on a web server that already has Apache
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
Actually, there's no need to change the ports.
`mydomain` redirects to the WAPT main page,
`mydomain/glpi` redirects to my GLPI page,
and `mydomain/wapt` correctly redirects the WAPT executables.
My only problem is that `https://mydomain` returns something else; I must have an .htaccess file to modify in my root directory.
Anyway, thank you, I'll look into the rest of the installation since I have two different networks to manage, and my server is accessible from both.
`mydomain` redirects to the WAPT main page,
`mydomain/glpi` redirects to my GLPI page,
and `mydomain/wapt` correctly redirects the WAPT executables.
My only problem is that `https://mydomain` returns something else; I must have an .htaccess file to modify in my root directory.
Anyway, thank you, I'll look into the rest of the installation since I have two different networks to manage, and my server is accessible from both.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
The most logical approach would be to configure Apache using virtual hosts
: https://httpd.apache.org/docs/2.2/fr/vh ... mples.html
: https://httpd.apache.org/docs/2.2/fr/vh ... mples.html
