Using Services

Discover our Public Cloud offer

Shared Hosting for Everyone, imagined by developers, for developers.

Discovering the Public Cloud

Set up a service (i.e. headless running command) in your Administration Panel: Advanced > Services.

The ports' range 8300 to 8499, as well as the hostname services-[account].alwaysdata.net1 are reserved to those services.

Important:

  • It must runs in foreground, not fork and leave 2.
  • When needing to be reached from an external application, bind it to :: (IPv6) and a port from 8300 to 8499.
  • Log files for running services are located at $HOME/admin/logs/services/, containing services' outputs.
    • An extract of these logs is presented in the administration’s interface (Logs - 📄).
  • For Public Cloud users:
    • Services are executed on a distinct servers than SSH and HTTP servers.
    • Their resources use must remain fair.
    • The services will not be available on IPv4, only on IPv6.
  • For Private clouds users (VPS and dedicated servers):
    • Range port 8300 to 8499 are not accessible from the external network. You can expose them to Internet using a firewall rule.

Private clouds users can also bind on another IP than :: and listen on ports outside of the range 8300-8499, but this is not recommended as it may lead to issues during migrations.

Examples

Redis

  • Command: redis-server --bind :: --port 8300
  • Monitoring command: redis-cli -h services-[account].alwaysdata.net -p 8300 ping

  1. [account] to be replaced by the account name. ↩︎

  2. See simple systemd service for use-cases. ↩︎