Action notifications and other updates

This update makes it easier to follow what is happening across your resources, understand your costs, and move through the console with less friction.

What's new

Resource action notifications

Get notified as your resource actions move through the queue, run, succeed, or fail. Open Notifications from the account menu to see recent activity, then click an item to jump straight back to the affected resource.

Clearer invoices and cost breakdowns

Invoices and project costs now show more useful detail:

• Billing-period dates are visible alongside current and past costs.
• Project-tier charges and resource costs are broken out separately.
• Resource costs can be expanded to review instance usage.
• Open invoices are labelled Current for easier scanning.

When an invoice is settled, Viduli now emails the organization owner a PDF copy. If a payment fails, the owner receives an alert with the relevant invoice attached.

Improved resource setup

Creating a resource is more focused. Choose your framework or engine first, see your selection while you configure it, and avoid changing fields that are already determined by that choice.

Better instance status and uptime

Resources with instances that are still starting now show a dedicated Pending status. Once an instance is running, its displayed uptime begins from the container start time for a more accurate view.

Easier configuration and navigation

• Long resource configuration pages now include an in-page section menu on larger screens.
• Resource details, project tabs, and console panels scroll more predictably.
• Reserved example domains such as example.com cannot be added to projects.

A more reliable shell

The browser shell now keeps its terminal size in sync when you connect and resize the window, fixing the rendering of command output.

Deployment and monitoring polish

• Django apps can opt into WSGI startup with AUTO_USE_WSGI=1.
• Deployments continue if Django static-file collection fails, so optional static assets do not block a build.
• Deployment logs now more clearly distinguish successful, informational, warning, and error messages.
• Monitoring charts and resource controls have received readability improvements.