Set up a project
A project is your web application, for example a website or a shop. You create it in the interface of your instance (your own development server).
Create a project from a template
Section titled “Create a project from a template”A template is a ready-made example project, for example Laravel or WordPress. The interface shows three steps in a row.
- Open your instance with Open instance on the service page (your page in my.envbay.com).
- Click New project.
- Click Start from a template.
- Click a template.
- Type a name for the project.
- Select a database (storage for your application’s data).
- In the last step, click Create project.
- Wait until the project appears green.
Your project is then reachable at this address:
https://<project>.<customer>.envbay.dev<project> stands for the project name, <customer> for the name of your instance.
The assistant (the helper for creating projects) shows which languages and services your plan includes. Anything your plan does not include is missing from the selection.
What’s next? Do you work with your own editor? Then read SSH and ports (secure connection to the server). Daily work covers everyday tasks.
If something does not work
Section titled “If something does not work”- A template or database is missing: Your plan does not include it. The plans are described in the chapter Plans and limits.
- The project does not turn green: Read the Logs (your application’s log) in the project. The reason is usually written there.
- A large build aborts: Free has 1 GB and Starter 2 GB of memory. Large frontend builds (assembling the interface) need more. The Team plan has 4 GB.
- You cannot get further: Write us a ticket (a message to support). The steps are in the chapter Help.
What applies at Envbay
Section titled “What applies at Envbay”You create projects in Envoryx. The author describes how it works (wizard, sources, envoryx.yml, environment variables and secrets, databases, extra services): Creating projects, Environment and manifest, Databases, Extra services. These additional limits and rules apply at Envbay:
| Topic | Rule |
|---|---|
| Runtimes in Free and Starter | PHP, Node.js, Python and static sites. Go, Ruby, Java and .NET are not provided there. |
| Runtimes in Team and Agency | The plan defines them; the wizard shows what your plan includes. |
| Services in Free and Starter | All except Ollama and OpenSearch (the plan’s service list is an allowlist). |
| Databases | MariaDB, MySQL, PostgreSQL and MongoDB are included in the plan list. The wizard only shows what your plan allows. |
| Address | https://<project>.<customer>.envbay.dev, HTTPS with wildcard certificate, see Projects and addresses |
| Visibility | New projects are private (fixed by the plan). |
| Ports | Services and project ports listen only locally; from outside, you reach them through the interface, a share or an SSH tunnel. |
| Resources | CPU and memory of the whole instance are limited by the plan, see Plans and limits. A single container may have at most the plan limit. |
| Large builds | In Free (1 GB) and Starter (2 GB), large frontend builds sometimes abort with out-of-memory (OOM). Use Team or Agency for them. |
| Backups | Project backups are only stored off-site if the project has a backup schedule, see Backups. |
| Direct mail sending via ports 25, 465 and 587 is blocked. Bulk mailing is not allowed under the terms and conditions. |
Catching mail with Mailpit
Section titled “Catching mail with Mailpit”Mailpit is an extra service in Envoryx that collects your application’s emails in a test mailbox. To do this, send via SMTP to the host mailpit. Mailpit can be selected in all plans. Note: it only catches emails that your application sends there. With any other mail setting in your application, ports 25, 465 and 587 are blocked towards the outside.