You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're excited to announce Encore v1.23 with several new features! As always, upgrade with encore version update.
Infrastructure Namespaces
Encore now allows you to create and switch between multiple, independent infrastructure namespaces. Infrastructure namespaces are isolated from each other, and each namespace contains its own independent data.
Create and switch to a new namespace with encore ns switch --create NAME . Commands like encore run, encore db shell and so on automatically use the active infrastructure namespace (override this with -n).
Infrastructure namespaces makes it trivial to switch tasks, confident your old state and data will be waiting for you when you return. If you've ever worked on a new feature that involves making changes to the database schema, only to context switch to reviewing a Pull Request and had to reset your database, you know the feeling.
Databases provisioned by Encore now support the popular [pgvector](https://github.com/pgvector/pgvector) and [PostGIS](https://postgis.net/) extensions! This is powered by the new encoredotdev/postgres:15 docker image. The extensions are supported across the board: for local development; in Encore's CI/CD pipeline when running tests; in new databases provisioned in Encore Cloud; and in cloud databases in AWS and GCP.
Let us know over on Slackif there are any more extensions you would like to see!
We rely on the community to improve Encore, and we continue to be overwhelmed by your support and encouragement.
Thank you Juan Álvarez, Will Demaine, Jakob Nordfeldt, MaxD, and Jamie MacLeod for your ideas in the new #suggestions Slack channel! ✨
What’s next
Right now we're working on adding support for deploying to Kubernetes on AWS, gRPC, and much more. Remember to vote on your favorite feature on the roadmap!
As always, if you have questions or feedback, tell us on Slack or just email us at hello@encore.dev.
We’re excited to hear your feedback! ❤️
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're excited to announce Encore v1.23 with several new features! As always, upgrade with
encore version update
.Infrastructure Namespaces
Encore now allows you to create and switch between multiple, independent infrastructure namespaces. Infrastructure namespaces are isolated from each other, and each namespace contains its own independent data.
Create and switch to a new namespace with
encore ns switch --create NAME
. Commands likeencore run
,encore db shell
and so on automatically use the active infrastructure namespace (override this with -n).Infrastructure namespaces makes it trivial to switch tasks, confident your old state and data will be waiting for you when you return. If you've ever worked on a new feature that involves making changes to the database schema, only to context switch to reviewing a Pull Request and had to reset your database, you know the feeling.
[Read the docs](https://encore.dev/docs/develop/infra-namespaces) to learn more about infrastructure namespaces, and let us know what you think over on Slack!
pgvector + PostGIS support
Databases provisioned by Encore now support the popular [pgvector](https://github.com/pgvector/pgvector) and [PostGIS](https://postgis.net/) extensions! This is powered by the new
encoredotdev/postgres:15
docker image. The extensions are supported across the board: for local development; in Encore's CI/CD pipeline when running tests; in new databases provisioned in Encore Cloud; and in cloud databases in AWS and GCP.Let us know over on Slackif there are any more extensions you would like to see!
Bugfixes and other improvements
sqldb.NewDatabase
([#822](v2/app: allow dbs to be defined outside svcs #822))--example=empty
([#821](cli: support '--example=empty' to create empty app #821))encore gen wrappers
to better work with first-time use during CI/CD workloads ([#815](cli: bump 'encore gen wrappers timeout' #815))Thanks to all contributors!
We rely on the community to improve Encore, and we continue to be overwhelmed by your support and encouragement.
Thank you Juan Álvarez, Will Demaine, Jakob Nordfeldt, MaxD, and Jamie MacLeod for your ideas in the new #suggestions Slack channel! ✨
What’s next
Right now we're working on adding support for deploying to Kubernetes on AWS, gRPC, and much more. Remember to vote on your favorite feature on the roadmap!
As always, if you have questions or feedback, tell us on Slack or just email us at hello@encore.dev.
We’re excited to hear your feedback! ❤️
Catch you in the cloud,
The Encore team
This discussion was created from the release Infrastructure Namespaces.
Beta Was this translation helpful? Give feedback.
All reactions