[RESOLVED] Evolution - Packet Loading

[flipflip]

Hello everyone,

Today I am noticing a rather surprising, or rather, not very optimized, way of working.

I manage my network either on-site or remotely from home. When I'm on-site, I have a 100Mbps fiber connection, so I don't have any issues. From home, I connect to my network via VPN using an ADSL connection (yes, they still exist). This works perfectly for everyday tasks (very well, in fact), except when it comes to downloading a new package or updating an existing one.

From my console, I start the download, and then it's made available on the server and the local repository. With a decent internet connection, there's no problem, but in my case, with ADSL, you can imagine the hassle when I have to update Acrobat, which is 650MB... I have plenty of time to go drink coffee, and above all, my internet connection drops completely.

Is it planned for the future that the console will only launch commands and that the server will do everything else?

Just for fun

wapt-1.png (14.5 KB) Viewed 30287 times

[vcardon]

Hello flipflip.

The signing key is local to your WAPT administration machine. This is WAPT's security model, and it's the most secure.

To sign a package, you have to download it to the administration machine, then sign it, and finally upload it back to the repository.

So, indeed, there aren't many ways at the moment to speed up signing a large package if you have a slow internet connection.

One solution would be to export the display from your administration machine hosted on your production network to your home PC, but be careful to secure it properly.

[flipflip]

Hello,

Yes, I understand the process and this constraint much better now. It makes sense.

Thank you.