Subuser
0.6
  • Features!
  • Screenshots
  • Security
  • Installing subuser
  • Download source
  • Using subuser - a quick tutorial
  • Packaging programs to run with subuser
  • The Subuser Standard
    • Image source identifier paths
    • Subuser names
    • Special files found within the subuser image
    • Subuser repositories
    • What the subuser program serializes to disk
      • The config.json file format
      • The installed-images.json file format
      • Depricated:
      • Runtime cache
      • Service lock files
      • The subuser registry
      • The locked-subusers.json file format
    • Subuser standard licence
  • Developers Corner
  • News
  • Press
  • Use cases
  • Presentations
  • Community
  • Community guidelines
  • Related projects
  • Design flaws/bugs in subuser
Subuser
  • Docs »
  • The Subuser Standard »
  • What the subuser program serializes to disk
  • View page source

What the subuser program serializes to diskΒΆ

The subuser program serialzes data about which subusers are installed, which repositories are tracked, which Docker images have been installed through subuser ect. It also accesses user set and system wide configuration files.

  • The config.json file format
    • Properties
  • The installed-images.json file format
  • Depricated:
  • Runtime cache
  • Service lock files
    • Services
      • xpra service containers
  • The subuser registry
    • The registry.lock file format
    • The subusers.json file format
    • The repositories.json file format
      • Properties
      • Example repositories.json file
    • The repository-states.json file format
      • Properties
    • The permissions.json and permissions-template.json files
  • The locked-subusers.json file format
Next Previous

© Copyright Creative Commons Attribution - Timothy Hobbs

Built with Sphinx using a theme provided by Read the Docs.