SampLive compiles on your machine, uploads the .amx over SFTP and reloads
the server over the network, so the remote server's OS doesn't matter.
The remote block in samplive.yaml. The minimum you need:
remote:
enabled: true
host: 203.0.113.10
user: root
password: your-ssh-password # or keyfile: /path/to/key
rcon_password: changeme # the server's rcon_password- Upload the
.amxover SFTP. - Try RCON
changemode. If the server doesn't know the command, fall back to: restart_cmdover SSH.
If both fail, SampLive tells you what's missing.
Before connecting, SampLive checks the server's host key against
~/.ssh/known_hosts. If it's not there:
ssh-keyscan your.server.ip >> ~/.ssh/known_hosts
Or set remote.insecure_skip_host_key: true to skip the check. You usually
don't want that.
Pterodactyl gives every server SFTP credentials. Use those in the remote
block and the same flow works. The panel API part (restarting from the panel)
is planned.
If you don't have a local server folder, set runtime.force to samp or
omp so SampLive knows which runtime to assume.
SampLive funciona perfecto en hosts Linux, siempre que tengas acceso SSH.
El flujo en un VPS:
- Compilás en tu máquina (Windows o lo que sea).
- SampLive sube el
.amxpor SFTP. - Recarga por RCON (
changemode) y, si el server no acepta el comando, por un comando SSH de restart (restart_cmd).
Config mínima en samplive.yaml:
remote:
enabled: true
host: 203.0.113.10
user: root
password: tu-clave-ssh # o keyfile: /ruta/a/llave
rcon_password: cambiemela # el rcon_password del server remotoSi el host solo te da un panel (Pterodactyl y similares), todavía no hay
integración con el panel: no se puede reiniciar desde SampLive. Lo que sí
funciona es usar las credenciales SFTP del panel en el bloque remote para
subir el .amx. La integración del panel está planeada.
La recarga en el lugar (jugadores conectados) hoy existe solo en Windows, porque ahí SampLive le escribe el comando en la consola. En Linux open.mp cae al restart del proceso y todos se desconectan — es un TODO pendiente.