Skip to main content

Update November 2020

Thank you to everyone who signed up for the Spawn Beta. Weโ€™re excited to let you know about the latest updates! If you haven't signed up for our beta yet, click the link below! ๐Ÿ‘‡

๐Ÿ‘‰ Get started

โœจ New features#

๐Ÿค– Spawnctl#

โŒ› Data container lifetimes!#

When creating a data container it is now possible to specify how long the container should live for, before being automatically deleted. See the docs for the new feature Create data-container and Update data-container.

๐Ÿ‘ฅ Organisations#

See all the members of your organisation with the new spawnctl get organisation command. This lets you see exactly who has access to Spawn in your organisation.

โŒ Just show me the logs#

When data image creation fails, did you know that you can run spawnctl logs data-image to see why? Weโ€™ve made this more discoverable by suggesting it whenever an image creation attempt fails. There is also an analogous spawnctl logs data-container command to see the database engine logs for your data containers.

๐Ÿ–– Aliases#

Weโ€™ve added some aliases for the get/create/delete data-container/data-image commands. You can now use di or dc instead of data-image and data-container.

๐Ÿ” No more copy/paste of security codes#

spawnctl now authenticates using the Device Authorization Grant, which means you donโ€™t have to copy/paste a code from the browser anymore. Just log into the browser window, and spawnctl will detect youโ€™ve authenticated.

๐Ÿ“ก Spawn service#

  • ๐Ÿ•ฐ Weโ€™ve made some cluster improvements, meaning more consistent startup times for data containers.

๐Ÿ“ Blog posts#

Development and containers - Gotta go fast!#

Development containers are part of a Visual Studio Code extension that allows you to....

Read more about how to use dev containers and spawn