Your first Volyx server
Once your hosting service is ready, most of your work happens inside the server workspace. This page explains how that workspace is organized and where to go for each type of task.
Understanding the server workspace
Every server has its own workspace. Instead of placing every feature on one screen, Volyx separates server management into focused sections.
The workspace is organized into four main groups: Server, Tools, Resources, and Management.
For most new projects, start with Overview, Console, Files, Config, and Secrets. The other tools become useful as your project grows.
Start with the server state
Before changing files or configuration, check whether the server is available and whether the application is currently running.
The server workspace can show information such as its current state, resource activity, and recent process output depending on the page you are viewing.
Make sure provisioning or preparation has completed.
Check Overview and Console before assuming the application itself is healthy.
Console output is normally the first place to look when something fails during startup.
Server
These are the core pages you will use to control and configure the server itself.
Your starting point for server information, current state, and important details.
View live application output and interact with the running process when supported.
Browse, create, upload, download, and edit project files.
Configure runtime-related values, project entry settings, and supported startup options.
Server-level settings and management options that do not belong to your project files.
Tools
Tools are focused on development, visibility, automation, and working with your application.
Inspect server resource activity such as CPU and memory behavior.
Work with project commands, dependencies, builds, and other terminal-based tasks.
Get help understanding errors, configuration, and development tasks using server context when available.
Work with supported deployment workflows for updating your application.
Store sensitive environment values separately from normal project files.
Resources
Resource pages connect your application to networking, storage, databases, and recovery features.
Review the network allocations available to your server.
Connect supported domains to applications that need public web access.
Create and manage supported database resources for your application.
Create recovery points before important project or configuration changes.
Management
Management pages control who can work with the server, scheduled actions, history, and supported access methods.
Manage other users who are allowed to work with the server.
Configure supported server tasks to run automatically on a schedule.
Review recorded actions and important changes related to the server.
View supported external access information for working with the server.
Recommended setup order
A predictable setup order makes configuration easier and prevents you from debugging several unrelated problems at once.
Confirm that you opened the correct server and that it is ready.
Upload or create the application files your project needs.
Set the correct runtime, version, entry file, and other required project options.
Add private environment values without placing them directly in public source files.
Use Smart Terminal when your project requires package installation or a build process.
Start the project and read its output while it initializes.
Check Metrics, Ports, Domain, and Databases if your application uses them.
Once the setup works, create a recovery point when the feature is available.
Make changes safely
When your server is working, avoid changing many unrelated settings at the same time. Small, controlled changes are easier to test and reverse.
Before a major update, dependency change, migration, or configuration rewrite, create a backup when possible and keep a copy of important configuration values.
- Change one major thing at a time.
- Read Console output after restarting the project.
- Do not publish Secrets or access credentials.
- Confirm the application works before making the next change.
When the server does not work
A server showing a problem does not always mean the hosting system itself has failed. Application configuration, missing dependencies, incorrect environment values, or project errors can also stop a service from starting correctly.
Find the first meaningful startup error.
Confirm runtime, version, entry file, and startup values.
Confirm required files actually exist in the expected location.
Verify required packages or build steps completed.
Confirm required environment values are present and correctly named.
Use AI Chat, troubleshooting documentation, or a support ticket when additional help is needed.
First server checklist
Next step
You now know how the server workspace is organized. Continue with Server Overview to learn the main information and controls available when opening a Volyx server.