> ## Documentation Index
> Fetch the complete documentation index at: https://developer.upsun.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Configure environments
> Configure your environments including their name, status, and visibility.
export const SyncIcon = () => ;
export const SettingsIcon = () => ;
export const MoreIcon = () => ;
export const MergeIcon = () => ;
export const BranchIcon = () => ;
From your project's main page in the Console, you can see all your environments as a list or a project tree:
In this overview, the names of inactive environments are lighter.
Selecting an environment allows you to see details about it,
such as its [activity feed](#activity-feed), [services](#service-information),
[metrics](/docs/observability/metrics), and [backups](/docs/environments/backup).
## Activity Feed
When you access an environment in the Console, you can see its [activity feed](/docs/observability/logs/access-logs#activity-logs).
This allows you to check which activities have happened or are currently happening on the selected environment:
You can filter activities by type (such as merge, sync, or redeploy).
## Actions on environments
Each environment offers ways to keep environments up to date with one another:
* [ **Branch**](/docs/glossary#branch) to create a new child environment.
* [ **Merge**](/docs/glossary#merge) to copy the current environment into its parent.
* [ **Sync**](/docs/glossary#sync)
to copy changes from its parent environment into the current environment.
There are also additional options:
* **Settings** to [configure the environment](#environment-settings).
* **More** to get more options.
* **URLs** to access the deployed environment from the web.
* **SSH** to access your project using SSH.
* **Code**
* **CLI** for the command to get your project set up locally with the [Upsun CLI](/cli).
* **Git** for the command to clone the codebase via Git.
If you're using Upsun as your primary remote repository, the command clones from the project.
If you have set up an [external integration](/docs/integrations/source),
the command clones directly from the integrated remote repository.
If the project uses an external integration to a repository that you haven't been given access to,
you can't clone until your access has been updated.
See how to [troubleshoot source integrations](/docs/integrations/source/troubleshoot).
## Environment URL
When you access an environment in the Console, you can view its URL. While the environment is loading in the Console, a `Waiting for URL...` message is displayed instead of the URL. If this message isn't updated once your [default environment](/docs/environments#default-environment)'s information is loaded, follow these steps:
1. Check that [you have defined routes](/docs/routes) for your default environment.
2. Verify that your [application](/docs/configure-apps/app-reference/single-runtime-image), [services](/docs/add-services), and [routes](/docs/routes) configurations are correct.
3. Check that your default environment is [active](/docs/environments/deactivate-environment#reactivate-an-environment).
## Environment settings
To access the settings of an environment, click **Settings** within that environment.
### Environment name
Under **Environment name**, you can edit the name and type of your environment and view its parent environment:
### Status
Under **Status**, you can check whether or not your environment is [active](/docs/glossary#active-environment).
For preview environments, you can [change their status](/docs/environments/deactivate-environment).
### Outgoing emails
Under **Outgoing emails**, you can allow your environment to [send emails](/docs/development/email):
### Hide from search engines
Under **Hide from search engines**, you can tell [search engines to ignore the site](/docs/environments/search-engine-visibility):
### HTTP access control
Under **HTTP access control**, you can [control access to your environment using HTTP methods](/docs/environments/http-access-control):
### Variables
Under **Variables**, you can define [environment variables](/docs/development/variables):
## Service information
For each environment, you can view information about how your routes, services, and apps are currently configured.
To do so, click **Services**.
By default, you see configured routes.
### Routes
The **Router** section shows a list of all the [routes configured on your environment](/docs/routes).
You can see each route's type and check if caching and server side includes have been enabled for it.
To view the configuration file where your routes are set up, click **Configuration**.
### Applications
To see detailed information about an app container,
select it in the tree or list on the left-hand side:
The **Overview** tab gives you information about your app.
You can see:
* The language version, the container size, the amount of persistent disk,
the number of cron jobs, and the command to SSH into the container.
* A summary of [metrics for the environment](/docs/observability/metrics).
* All cron jobs with their name, frequency, and command.
* All workers with their name, size, amount of persistent disk, and command to SSH into the container.
To view [the configuration file where your app is set up](/docs/configure-apps/), click **Configuration**.
### Services
To see detailed information about a [running service](/docs/add-services),
select it in the tree or list on the left-hand side:
The **Overview** gives you information about the selected service.
You can see the service version, the container size, and the disk size, if you've configured a persistent disk.
You can also see a summary of [metrics for the environment](/docs/observability/metrics).
To view the configuration file where your services are set up, click **Configuration**.
In this overview, the names of inactive environments are lighter.
Selecting an environment allows you to see details about it,
such as its [activity feed](#activity-feed), [services](#service-information),
[metrics](/docs/observability/metrics), and [backups](/docs/environments/backup).
## Activity Feed
When you access an environment in the Console, you can see its [activity feed](/docs/observability/logs/access-logs#activity-logs).
This allows you to check which activities have happened or are currently happening on the selected environment:
You can filter activities by type (such as merge, sync, or redeploy).
## Actions on environments
Each environment offers ways to keep environments up to date with one another:
* [
### Environment name
Under **Environment name**, you can edit the name and type of your environment and view its parent environment:
### Status
Under **Status**, you can check whether or not your environment is [active](/docs/glossary#active-environment).
For preview environments, you can [change their status](/docs/environments/deactivate-environment).
### Outgoing emails
Under **Outgoing emails**, you can allow your environment to [send emails](/docs/development/email):
### Hide from search engines
Under **Hide from search engines**, you can tell [search engines to ignore the site](/docs/environments/search-engine-visibility):
### HTTP access control
Under **HTTP access control**, you can [control access to your environment using HTTP methods](/docs/environments/http-access-control):
### Variables
Under **Variables**, you can define [environment variables](/docs/development/variables):
## Service information
For each environment, you can view information about how your routes, services, and apps are currently configured.
To do so, click **Services**.
By default, you see configured routes.
### Routes
The **Router** section shows a list of all the [routes configured on your environment](/docs/routes).
You can see each route's type and check if caching and server side includes have been enabled for it.
To view the configuration file where your routes are set up, click **Configuration**.
### Applications
To see detailed information about an app container,
select it in the tree or list on the left-hand side:
The **Overview** tab gives you information about your app.
You can see:
* The language version, the container size, the amount of persistent disk,
the number of cron jobs, and the command to SSH into the container.
* A summary of [metrics for the environment](/docs/observability/metrics).
* All cron jobs with their name, frequency, and command.
* All workers with their name, size, amount of persistent disk, and command to SSH into the container.
To view [the configuration file where your app is set up](/docs/configure-apps/), click **Configuration**.
### Services
To see detailed information about a [running service](/docs/add-services),
select it in the tree or list on the left-hand side:
The **Overview** gives you information about the selected service.
You can see the service version, the container size, and the disk size, if you've configured a persistent disk.
You can also see a summary of [metrics for the environment](/docs/observability/metrics).
To view the configuration file where your services are set up, click **Configuration**.