Added dark display theme to the Render Dashboard
The Render Dashboard now provides a dark display theme:
![The Render Dashboard's dark display theme](https://cdn.sanity.io/images/hvk0tap5/production/bf901b81573f47b98ac14a4999aadd81be55cb20-1938x1222.png?w=1200&q=95&fit=max&auto=format)
Additionally, you can toggle a high contrast mode to more prominently highlight certain interactive elements.
Quickly set your theme from the account menu in the top-right corner of the dashboard:
![Setting a display theme in the Render Dashboard](https://cdn.sanity.io/images/hvk0tap5/production/df0837c07f4e76b64a93caaf1d8de507cb683e0c-472x766.png?w=1200&q=95&fit=max&auto=format)
To also toggle high contrast, open your account settings and scroll down to the Theme section:
![Theme settings on the account settings page](https://cdn.sanity.io/images/hvk0tap5/production/213455d6eb39e4546997a0566c4398b0444ad34f-1204x580.png?w=1200&q=95&fit=max&auto=format)
API endpoints for datastores, logs, environments, Blueprints, and more
The Render API has added over 50 new endpoints to support much more extensive integration with the Render platform.
Endpoints are now available for the following resources that were previously unsupported by the API:
- Datastores (PostgreSQL, Redis, and persistent disks)
- Service logs
- Environment groups
- Blueprints
- Projects and environments
- Notification settings
New endpoints are also available for certain resources that are already supported by the API, such as redirect/rewrite rules for static sites.
With these additions, the API supports almost all functionality available in the Render Dashboard. There are no breaking changes to existing API endpoints.
The OpenAPI spec for the Render API is available in JSON format at this URL. You can use this spec to create your own custom clients and other tooling.
Learn more in the API reference.
Redis instances now emit service logs
Redis instances now emit service logs. As with logs for other service types, Redis logs are available in the Render Dashboard and via any configured log stream.
![Redis logs in the Render Dashboard](https://cdn.sanity.io/images/hvk0tap5/production/e5146e284871bb872925bf9872257b63b1c9ea49-1514x916.png?w=1200&q=95&fit=max&auto=format)
Learn more about logging in the documentation.
Default Node.js version updated to 20.15.1
Newly created Node.js services now use Node.js 20.15.1 by default. You can always specify a different version.
Existing Node.js services keep their original default version to prevent breaking changes.
Audit logs for Organization and Enterprise plans
Teams with an Organization or Enterprise plan can now export audit logs of material events that occurred in the account over a given time frame. This includes events related to:
- Team member management
- Project and environment management
- Service creation/deletion
Team admins can export audit log data in the Render Dashboard, from the Audit Logs section of the Team Settings page:
![Exporting audit log data in the Render Dashboard](https://cdn.sanity.io/images/hvk0tap5/production/e0ac7e317fd602f8ebd672766a87aefa99fe3aee-1216x496.png?w=1200&q=95&fit=max&auto=format)
For a list of all audit log event types, see the documentation.
Note the following about data availability:
- For existing Organization and Enterprise accounts, audit log data is available starting from June 24, 2024.
- For a new Organization or Enterprise account, audit log data is available starting from the date of account creation.
- If you upgrade an account to Organization or Enterprise, audit log data is available starting from the date of the upgrade.
Learn more in the documentation.
Pull and deploy private images from Google Artifact Registry
You can now pull and deploy your private Docker images from Google Artifact Registry. Add your credentials in the Render Dashboard during service creation:
![Adding a Google Artifact Registry credential in the Render Dashboard](https://cdn.sanity.io/images/hvk0tap5/production/931fc24b82d764eac72b31a989293bf2b9e38097-964x594.png?w=1200&q=95&fit=max&auto=format)
With this addition, Render now supports pulling private images from the following registries:
- Docker Hub
- GitHub Container Registry
- GitLab Container Registry
- Google Artifact Registry
Learn more in the documentation.
Quickly deploy PostgreSQL admin apps from the Render Dashboard
Render now provides simplified deployment for popular PostgreSQL admin apps in the Render Dashboard.
![Deploying PostgreSQL admin apps in the Render Dashboard](https://cdn.sanity.io/images/hvk0tap5/production/cc460bf600a559afe9bf39dfcae1061c3d272af7-1424x576.png?w=1200&q=95&fit=max&auto=format)
With a few clicks, you can deploy each app as a standalone web service that's automatically configured to connect to your database.
The following apps are currently supported:
- pgAdmin
- PgHero
Learn more in the documentation.
Official Render Terraform provider now available in early access
Render's official Terraform provider is now available in early access. You can use this provider to manage your Render services alongside other systems in your organization's infrastructure.
- The provider and its documentation are available in the Terraform Registry.
- Please submit any issues on GitHub.
Note that breaking changes might be introduced during the early access period. Any such changes will be noted in accompanying release notes.
Change an existing service's runtime via API or Blueprint
You can now change the native runtime for an existing service in any of the following ways:
- Make an HTTP call to the Render API’s Update service endpoint.
- Specify a new
runtime
via theserviceDetails
parameter you provide in your request.
- Specify a new
- If you’re managing your service with Render Blueprints, update the service’s
runtime
field in yourrender.yaml
file, then sync your Blueprint.
Changing a service's runtime in the Render Dashboard is not currently supported.
Learn more in the documentation.
Free PostgreSQL instances now expire after 30 days (previously 90)
As of 2024-05-20, newly created Free Render PostgreSQL databases expire after 30 days (previously 90 days). Free databases created prior to this date retain their original expiration date.
The following Free database policies remain unchanged:
- Each individual and team account is limited to one Free database at a time.
- After your Free database expires, you have an additional 14 days to upgrade it to a paid instance type before your data is deleted.
- After your Free database expires, you can create a new Free database.
Learn more about Free PostgreSQL limitations in the documentation.