Devbox Access and Workspace

Open Devbox Access to find the SSH connection details and application URLs for your assigned development environment. The portal is documented as authenticated and team-visible. Obtain the approved portal access and an environment assignment from the platform team; do not assume every environment shown belongs to you.

Get access and choose your environment

Before connecting, you need an assigned environment and your SSH public key registered by the platform team. Keep the private key on your own machine. The portal shows public-key fingerprints and credential-file locations; it does not display private keys or database passwords.

Select your environment and check:

Portal detail	What to use it for
Environment name and owner	Confirm you are entering the workspace assigned to your task.
Runtime status	Distinguish an available environment from sleeping services or an environment that is down.
SSH command	Copy the exact host and port for your environment.
Project URLs	Open the application served from the same workspace you are editing.
Data Access	Identify that environment's database names and credential location when your task requires database access. Never paste credential contents into docs, tickets, or chat.

Use the SSH command shown by the portal. Do not reuse the example port in another guide or a colleague's saved command. Once connected, devbox-help shows the in-environment commands.

Open the project

The documented workspace layout includes /workspace/menzzo, /workspace/logidav, /workspace/logidav-v2, /workspace/rest-menzzo, /workspace/tracking-menzzo, /workspace/chatbot, and /workspace/wrapper. Check which projects are actually provisioned in your assigned environment. Other Menzzo systems may use a different development setup.

Open the owning project's directory and inspect its branch and existing changes. For PHP projects, run php -v from that directory: the Devbox wrappers select the runtime using .php-version. Do not assume the version in a historical example matches your current branch.

For PhpStorm, use the same SSH endpoint in JetBrains Gateway, then open the appropriate /workspace project. Follow the pinned PhpStorm setup guide.

When the application is asleep

The Devbox onboarding guide says app services can sleep while SSH remains available when idle auto-stop is enabled. For your assigned development environment, connect by SSH and follow its wake instruction:

# Inside your assigned development shell, when its app services are sleeping
devbox wake

This starts application services; it is not a read-only diagnostic. If the portal says the entire environment is Down, or SSH is unavailable, ask the platform team to start or diagnose it. Host administration, creating/resetting environments, and changes to other developers' workspaces are not part of the first-change workflow. Production commands still require individual approval.

Project setup and checks

Devbox supplies the development workspace and access details. It does not replace the owning repository's setup, branch, or validation instructions.

• Magento: start with Menzzo Magento and the checkout's README. Shared docs do not yet provide a complete Magento-specific test workflow.
• Logidav: read Local Setup for application requirements and compare them with the provisioned workspace before installing or configuring anything. Use Workflows and Runbooks for the change you are investigating.
• Other projects: use the project directory and its setup links. Missing instructions should be resolved with the owning team, not replaced with a generic command.

Continue with First Change once you can connect to the correct workspace and open its application.

Source and verification

Reviewed Devbox source at af72038b79ed8465dba422ced706c0fb39cafa37: portal address and operator documentation, developer onboarding, and portal environment fields and UI.

These references establish the documented address, connection fields, workspace layout, and developer commands. This update did not log in to the portal, connect to a host, inspect credentials, wake an environment, or verify deployed portal behavior. The exact sign-in method, environment assignment, installed runtime, and available projects must be confirmed for the developer's environment.