Daily work

Here you read what you need every day when a project is running. You operate projects in the interface of your instance (your own development server).

Restart project

A restart often helps when an application hangs.

1. Open your project.
2. Click Restart at the top.

Stop halts the project. Open opens the website.

Find errors

1. In the project, open the Logs section (the log of your application).
2. Read the last lines.

It shows what your application reports.

Run commands in the browser

1. In the project, open the Terminal section (a window for commands).

You do not need to install anything. The window works directly in your project.

Test emails

Mailpit (a test mailbox) catches your application’s emails. They then do not go to real recipients. You select Mailpit when you create the project. More in the Envoryx documentation.

Restart the whole instance

If the whole instance hangs, use the service page (your instance page in my.envbay.com). The steps are in the chapter Control instance.

If something does not work

Check in this order:

1. Is the project running?
2. What do the Logs say?
3. Does a restart help?
4. If that does not help, write us a ticket (a message to support). The steps are in the chapter Help.

Where to operate what

What	Where
Start, stop, restart project, logs, terminal, branch environments, health check	Envoryx, interface of your instance
Restart, stop, start whole instance, trigger instance backup	Service page in my.envbay.com, see Control instance

The author describes operating Envoryx, for example Project lifecycle, Terminal, SSH & logs, CLI, API, MCP and Troubleshooting. The actions in the header of a project apply to all containers of the project. The address for CLI, API and MCP is the interface of your instance: https://envoryx.<customer>.envbay.dev.

Limits in daily use

• CPU and memory are limited for the whole instance by the plan; the limit is hard, and all projects share the resources. If memory is not sufficient, the kernel ends processes (out-of-memory). On Free and Starter, this affects large frontend builds. Details under Plans and limits.
• Disk space is soft-limited: when it runs low, Envoryx first stops new projects and backups.
• Container limits per project are set in Envoryx, see Resource limits. A single container may have at most the plan limit.
• Branch environments (a copy of a project on another Git branch) are not included in Free and Starter, see Branch environments.
• Outgoing connections to the internet are allowed, except mail ports 25, 465 and 587. Too many new connections per second are throttled, see Security and fair use.

If something hangs

1. Is the project running, and what do the logs say?
2. Does a restart of the project help?
3. If the whole interface no longer responds, restart the instance on the service page.
4. If the problem remains, open a ticket.