Synpse
🤖 Devices⚡ ApplicationsTry Synpse!
  • Intro to Synpse
  • Start here
    • Quick Start (web user)
    • Quick Start (CLI)
  • Agent
    • Install
      • Raspberry Pi
      • Linux (Docker)
      • MacOS
      • NVIDIA Jetson
      • Headless (Ubuntu)
      • BeagleBoard AI
      • Bulk Provisioning
      • 🪄Beta - Universal Synpse image
      • Containerized agent
      • Configuration
    • Uninstall
  • CLI
    • Install & Usage
  • synpse core
    • Devices
      • Device Provisioning
      • HTTPS Tunnel Access
      • SSH Access
      • Device Labels
      • Environment Variables
      • Proxy Application Ports
      • OS & Architectures
      • Operations
      • Device API
    • Applications
      • Deploy
      • Secrets
      • Environment variables
      • Substitution (dynamic templates)
      • Volumes
      • Networking
      • Scheduling
      • Registry authentication
      • Using GPUs
      • Tips & Tricks
      • Logs and status
      • Application specification (API reference)
    • Account
      • Personal Access Tokens
      • Service (Robot) Accounts
      • Teams (Share Devices)
    • Monitoring (beta)
      • Device Monitoring
      • Application Monitoring
  • Manage
    • Projects
    • Namespaces
    • Quotas
  • Examples
    • 🏠Home Automation
      • Gladys Assistant
      • Home Assistant
    • 🛠️Preparing OS Images
      • Synpse CLI Builder
      • Build a custom Raspberry Pi image
      • Cloud-init (advanced)
    • 💡Dynamic Templates
    • ☁️Public Cloud IoT
      • AWS IoT Core
      • Azure IoT Hub
      • GCP IoT Core
    • 🚀Device management
      • VNC to remove devices
      • Ansible
  • On-prem Deployment
    • 🐳Docker Compose
    • 🌤️kubernetes
  • Resources
    • API Documentation
    • Deployment patterns
    • Security & Tech
Powered by GitBook
On this page

Was this helpful?

  1. Manage

Namespaces

Synpse namespaces and how to manage them

PreviousProjectsNextQuotas

Last updated 3 years ago

Was this helpful?

Namespaces are second layer resource within namespaces. The purpose of them is application level isolation. By default, free tier users can have 1 namespace.

Namespaces on their own have a resource quota limitation, which can be changed by upgrading tier.

You can create namespace from Projects section:

You can manage Namespaces by pressing Manage button on the Project. This allows user yo create or delete namespaces.

Same operations can be done via CLI:

synpse project --help
Manage projects

Usage:
  synpse project [flags]
  synpse project [command]

Aliases:
  project, projects

Available Commands:
  create      Create a project
  list        List projects
  select      Select a project
synpse namespace --help
Manage namespaces and their configuration

Usage:
  synpse namespace [flags]
  synpse namespace [command]

Aliases:
  namespace, namespaces

Available Commands:
  create      Create a namespace
  delete      Delete a namespace
  edit        Edit a namespace
  list        List namespaces
  select      Select a namespace
Projects UI