-p, --port <PORT>
          The port where the HTTP app is available. ...
          [env: ATOMIC_PORT=8139]
          [default: 9883]

atomic-server show-config

Config {
    server_url: "http://localhost:8139",
    opts: Opts {
        command: Some(
            ShowConfig,
        ),
        initialize: false,
        rebuild_indexes: false,
        development: false,
        domain: "localhost",
        port: 8139,
        port_https: 9884,
        ip: ::,
        https: false,
        https_dns: false,
        email: None,
        script: "",
        config_dir: Some(
            "/atomic-storage/config",
        ),
        data_dir: Some(
            "/atomic-storage/data",
        ),
        public_mode: false,
        server_url: None,
        log_level: Info,
        trace: Stdout,
        slow_mode: false,
    },
    config_dir: "/atomic-storage/config",
    key_path: "/atomic-storage/config/https/key.pem",
    cert_path: "/atomic-storage/config/https/cert.pem",
    https_path: "/atomic-storage/config/https",
    config_file_path: "/atomic-storage/config/config.toml",
    static_path: "/atomic-storage/data/static",
    store_path: "/atomic-storage/data/store",
    uploads_path: "/atomic-storage/data/uploads",
    search_index_path: "/root/.cache/atomic-data/search_index",
    initialize: false,
}

Create, share and model Atomic Data with this graph database server. Run atomic-server without any arguments to start the server. Use --help to learn about the options.

Usage: atomic-server-bin [OPTIONS] [COMMAND]

Commands:
  export
          Create and save a JSON-AD backup of the store
  import
          Import a JSON-AD file or stream to the store. By default creates Commits for all changes, maintaining version history. Use --force to allow importing other types of files
  generate-dotenv
          Creates a `.env` file in your current directory that shows various options that you can set
  show-config
          Returns the currently selected options, based on the passed flags and parsed environment variables
  reset
          Danger! Removes all data from the store
  help
          Print this message or the help of the given subcommand(s)

Options:
      --initialize
          Recreates the `/setup` Invite for creating a new Root User. Also re-runs various populate commands, and re-builds the index
          
          [env: ATOMIC_INITIALIZE=]

      --rebuild-indexes
          Re-builds the indexes. Parses all the resources. Do this when updating requires it, or if you have issues with Collections / Queries / Search
          
          [env: ATOMIC_REBUILD_INDEX=]

      --development
          Use staging environments for services like LetsEncrypt
          
          [env: ATOMIC_DEVELOPMENT=]

      --domain <DOMAIN>
          The origin domain where the app is hosted, without the port and schema values
          
          [env: ATOMIC_DOMAIN=localhost]
          [default: localhost]

  -p, --port <PORT>
          The port where the HTTP app is available. Set to 80 if you want this to be available on the network
          
          [env: ATOMIC_PORT=8139]
          [default: 9883]

      --port-https <PORT_HTTPS>
          The port where the HTTPS app is available. Set to 443 if you want this to be available on the network
          
          [env: ATOMIC_PORT_HTTPS=]
          [default: 9884]

      --ip <IP>
          The IP address of the server. Set to :: if you want this to be available to other devices on your network
          
          [env: ATOMIC_IP=]
          [default: ::]

      --https
          Use HTTPS instead of HTTP. Will get certificates from LetsEncrypt fully automated
          
          [env: ATOMIC_HTTPS=]

      --https-dns
          Initializes DNS-01 challenge for LetsEncrypt. Use this if you want to use subdomains
          
          [env: ATOMIC_HTTPS_DNS=]

      --email <EMAIL>
          The contact mail address for Let's Encrypt HTTPS setup
          
          [env: ATOMIC_EMAIL=]

      --script <SCRIPT>
          Custom JS script to include in the body of the HTML template
          
          [env: ATOMIC_SCRIPT=]
          [default: ]

      --config-dir <CONFIG_DIR>
          Path for atomic data config directory. Defaults to "~/.config/atomic/""
          
          [env: ATOMIC_CONFIG_DIR=/atomic-storage/config]

      --data-dir <DATA_DIR>
          Path for atomic data store folder. Contains your Store, uploaded files and more. Default value depends on your OS
          
          [env: ATOMIC_DATA_DIR=/atomic-storage/data]

      --public-mode
          CAUTION: Skip authentication checks, making all data publicly readable. Improves performance
          
          [env: ATOMIC_PUBLIC_MODE=]

      --server-url <SERVER_URL>
          The full URL of the server. It should resolve to the home page. Set this if you use an external server or tunnel, instead of directly exposing atomic-server. If you leave this out, it will be generated from `domain`, `port` and `http` / `https`
          
          [env: ATOMIC_SERVER_URL=]

      --log-level <LOG_LEVEL>
          How much logs you want. Also influences what is sent to your trace service, if you've set one (e.g. OpenTelemetry)
          
          [env: RUST_LOG=]
          [default: info]
          [possible values: warn, info, debug, trace]

      --trace <TRACE>
          How you want to trace what's going on with the server. Useful for monitoring performance and errors in production. Combine with `log_level` to get more or less data (`trace` is the most verbose)
          
          [env: ATOMIC_TRACING=]
          [default: stdout]

          Possible values:
          - stdout:
            Log to STDOUT in your terminal
          - chrome:
            Create a file in the current directory with tracing data, that can be opened with the chrome://tracing/ URL
          - opentelemetry:
            Log to a local OpenTelemetry service (e.g. Jaeger), using default ports

      --slow-mode
          Introduces random delays in the server, to simulate a slow connection. Useful for testing
          
          [env: ATOMIC_SLOW_MODE=]

  -h, --help
          Print help information (use `-h` for a summary)

  -V, --version
          Print version information

/atomic-storage/data/store
/atomic-storage/data/store/blobs
/atomic-storage/data/store/conf
/atomic-storage/data/store/db
/atomic-storage/data/store/snap.000000000081ADA0

thread 'main' panicked at server/src/bin.rs:118:17:
/work/.env already exists

thread 'main' panicked at server/src/bin.rs:100:14:
called `Result::unwrap()` on an `Err` value: IO(Custom { kind: NotConnected, error: "not a terminal" })

server = "http://localhost:8139"
agent = "http://localhost:8139/agents/uuIgCqY79Wq1tHIisGWmdSkHC2oAsGaioFANg="
private_key = "aKyy/8Ij6aOibh6LhozEweJELzmo6seGLjxtFBQaw5U="

[Service]
Environment=ATOMIC_DOMAIN=notes.example.com
Environment=ATOMIC_PORT=8139
Environment=ATOMIC_HTTPS=
Environment=ATOMIC_EMAIL=ops@example.com
Environment=ATOMIC_CONFIG_DIR=/srv/atomic/config
Environment=ATOMIC_DATA_DIR=/srv/atomic/data
Environment=RUST_LOG=info
Environment=ATOMIC_TRACING=stdout
ExecStart=/usr/local/bin/atomic-server
Restart=unless-stopped