Meta tags:
description=Learn what environments on Upsun are and how to take advantage of them.;

Headings (most frequently used words):

environments, manage, environment, paused, resources, upsun, documentation, index, on, this, page, create, default, status, organize, your, push, options, get, started, core, concepts, configure, apps, services, build, deploy, run, projects, observability, metrics, integrations, troubleshooting, hierarchy, workflows, naming, conventions, pause, an, resume, possible, approaches, example, workflow,

Text of the page (most frequently used words):
#environment (96), the (77), you (47), environments (40), and (32), can (32), your (30), upsun (27), parent (17), push (17), for (15), git (13), sprint (11), have (10), create (10), project (9), from (9), development (9), each (9), this (8), developer (8), page (8), status (8), data (8), default (8), resume (8), live (8), branch (8), manage (8), resources (7), cli (7), following (7), paused (7), pause (7), that (7), when (7), one (7), using (6), documentation (6), set (6), its (6), use (6), production (6), staging (6), run (6), console (6), new (6), with (6), services (6), overview (6), are (5), title (5), example (5), how (5), into (5), options (5), source (5), time (5), code (5), also (5), want (5), admin (5), all (5), child (5), may (4), integration (4), command (4), click (4), preview (4), been (4), ticket (4), per (4), naming (4), name (4), organize (4), site (4), feature (4), deployed (4), workflow (4), workflows (4), hierarchy (4), created (4), copy (4), home (3), backup (3), clone_parent_on_create (3), active (3), through (3), type (3), these (3), redeployed (3), automatically (3), any (3), settings (3), convention (3), similar (3), agile (3), work (3), features (3), branches (3), test (3), testing (3), approaches (3), change (3), inactive (3), apps (3), metrics (3), configure (3), assistant (2), linkedin (2), youtube (2), github (2), about (2), blog (2), reference (2), api (2), tutorials (2), docs (2), restore (2), was (2), true (2), activate (2), clone (2), isn (2), which (2), changes (2), actions (2), see (2), available (2), activity (2), tab (2), navigate (2), environment_nam (2), project_i (2), manually (2), select (2), often (2), days (2), types (2), task (2), adopt (2), feature2 (2), feature1 (2), what (2), ways (2), structure (2), conventions (2), complete (2), merged (2), sync (2), review (2), security (2), hotfix (2), needs (2), few (2), own (2), take (2), possible (2), merge (2), after (2), check (2), open (2), them (2), only (2), but (2), might (2), custom (2), tied (2), instance (2), application (2), storage (2), local (2), tests (2), integrations (2), build (2), deploy (2), search (2), free (2), trial (2), index (2), responses, generated, contain, mistakes, built, hosted, mintlify, platform, powered, careers, pricing, company, support, community, changelog, isolation, yes, helpful, last, modified, 2026, terminal, shows, single, remote, location, named, make, sure, adjust, commands, accordingly, init, resource_initialization_strategy, define, minimum, manual, resource, initialization, strategy, environment_type, false, disable, cloning, parent_environment_name, environment_title, action, supports, some, allows, trigger, same, provides, pass, string, server, official, becomes, again, window, pushing, redeploying, resumes, general, under, follow, steps, used, limited, then, abandoned, prevent, unnecessary, consumption, pauses, haven, both, 395, developer2, 593, 526, developer1, prefer, splitting, having, specific, sprint2, feature3, sprint1, choose, represents, many, different, help, introduce, syncs, next, repeat, continue, process, merges, makes, remaining, ensures, their, working, date, latest, done, developed, reviewed, accessing, gives, permission, bug, issue, deployment, operational, user, unit, centric, story, creating, since, customize, decide, best, fits, down, alternatively, organized, featuring, directory, view, information, panel, appear, lighter, list, dropdown, menu, hasn, longer, has, three, statuses, comes, must, give, domain, aren, running, called, demand, even, pull, requests, exact, replicas, case, inherits, includes, databases, network, queues, routing, configurations, existing, two, hierarchical, relationships, think, other, copies, where, without, worrying, damaging, anything, once, completed, they, instantly, seamlessly, include, multiple, divided, least, additional, there, will, ever, contains, app, needed, group, learn, advantage, request, register, glossary, mounts, disks, 502, error, resolutions, troubleshooting, health, notifications, fastly, cdn, scripts, logs, infrastructure, observability, prerelease, object, scaling, compliance, administration, domains, projects, database, management, ssh, tools, variables, routes, languages, common, tasks, effectively, works, core, concepts, pick, stack, setup, guide, quickstart, get, started, navigation, watch, demo, ask, skip, main, content, file, discover, pages, before, exploring, further, fetch, llms, txt,

Text of the page (random words):
manage upsun environments upsun developer documentation index fetch the complete documentation index at llms txt use this file to discover all available pages before exploring further skip to main content upsun developer home page search k ask assistant i console watch a demo free trial free trial search navigation manage environments manage upsun environments home docs tutorials ai api cli blog get started quickstart setup guide pick a stack core concepts how upsun works workflow overview using upsun effectively common tasks configure apps services configure apps languages services routes build deploy run build and deploy local development variables development tools ssh database management manage projects overview project settings custom domains administration security compliance manage environments overview backup restore environment settings environment actions manage resources overview how resources work configure resources scaling object storage prerelease observability metrics overview infrastructure metrics application metrics logs integrations overview source integrations activity scripts fastly cdn health notifications troubleshooting 502 error resolutions development disks mounts resources glossary data register request features on this page create environments default environment environment status organize your environments hierarchy workflows possible approaches example workflow naming conventions paused environments pause an environment resume a paused environment push options manage environments manage upsun environments copy page copy page learn what environments on upsun are and how to take advantage of them copy page copy page an upsun environment contains one instance of an app or group of apps with all the services needed for it to run each project can include multiple environments often divided into environment types if you have a live site you have at least a production environment you may also have additional environments of the staging or development environment type but there will only ever be one production environment you can think of other environments as copies of your live site where you can run tests without worrying about damaging anything in production once you have completed your tests you can merge your changes so that they re instantly and seamlessly deployed to production you can create environments for development testing staging review and so on to organize your environments you can create hierarchical relationships create environments you can create new environments in one of two ways push a local branch through git or a source integration branch existing environments using the cli or the console when you branch an environment you might want to create exact replicas of it in this case each new environment inherits all of the data and services from its parent environment this includes databases network storage queues and routing configurations you can create upsun environments on demand each environment is tied to a git branch if you use a source integration you can even have environments created automatically for your pull requests and branches you can also have branches that aren t tied to a running instance of your application these are called inactive environments default environment your default environment comes from your default branch and is a production environment your project must have a default environment but you can name it as you want this environment is your live site you might want to give it a custom domain name environment status your environments can have one of three statuses active a deployed environment with services and data inactive an environment that isn t deployed and has no services or data only code paused an environment that hasn t been redeployed in 14 days or longer you can see the status of your environments in the console or the cli in the console using the cli when you open your project inactive environments appear lighter in the environment list you also can t select them from the environment dropdown menu to check the status of an environment you can also open it and view its information panel to check the status of all your environments from your project directory run the upsun environments command you can change an environment s status at any time organize your environments hierarchy in upsun your environments are organized in a hierarchy featuring parent and child environments when you branch an environment the parent of the new environment is the environment it was created from you can change the environment s parent after it s been created when you push a branch through git or a source integration the parent environment of the new environment is your default environment alternatively you can change the environment s parent after it s been created each child environment can sync code and or data down from its parent and merge code up to its parent you can use child environments for development staging and testing workflows since you can customize your environment hierarchy you can create your own workflows you can decide which structure best fits your needs possible approaches you may want to take one of the following approaches when creating your workflows agile a child environment per sprint each story in the sprint can have its own environment as a child of the sprint environment developer centric one qa environment and a few preview environments per developer per task or similar testing an operational test environment a user test environment and a few unit test environments hotfix one environment for each bug security issue or hotfix that needs deployment example workflow example agile workflow an admin branches the live default environment to create a sprint environment the admin gives each developer permission to branch the sprint environment to create new feature environments feature 1 is developed and work is reviewed by accessing the deployed feature 1 environment when the review is done feature 1 is merged into the sprint environment the remaining features sync with the sprint environment this ensures their working environment is up to date with the latest code when the sprint is complete and all features merged into the sprint environment the admin makes a backup of the live site the admin merges the sprint environment into the live environment the admin syncs the next sprint s environment with the live environment to repeat and continue the development process naming conventions you can organize and work with your preview environments in many different ways it can help to introduce a convention for how you name and structure your environments for each environment choose a name that represents what the environment is for if you use agile for example you can adopt a naming convention similar to the following live sprint1 feature1 feature2 feature3 sprint2 feature1 feature2 if you prefer splitting your environments per developer and having a specific environment for each task or ticket you can adopt a naming convention similar to the following staging developer1 ticket 526 ticket 593 developer2 ticket 395 paused environments preview environments are often used for a limited time and then abandoned to prevent unnecessary consumption of resources upsun automatically pauses preview environments of both development and staging types that haven t been redeployed in 14 days you can pause and resume an environment manually at any time pause an environment to pause an environment follow these steps using the cli in the console run the following command upsun environment pause project project_i d environment environment_nam e navigate to your project and click settings under environments select the environment you want to pause in the general tab click pause environment resume a paused environment pushing new code or redeploying a paused environment automatically resumes it you can also resume it manually at any time using the cli in the console run the following command upsun environment resume project project_i d environment environment_nam e navigate to the paused environment in the activity tab click resume environment in the resume environment window click resume the environment is redeployed and becomes available for use again push options git provides push options to pass a string to the server see the official git documentation upsun supports some of these push options which allows you to push changes to your environment and trigger the following actions at the same time action command activate the environment git push upsun o environment status active set a title for the environment git push upsun o environment title environment_title set the parent environment git push upsun o environment parent parent_environment_name clone the data from the parent environment git push upsun o environment clone_parent_on_create true disable the cloning of the data from the parent environment git push upsun o environment clone_parent_on_create false set the environment type development staging or production git push upsun o environment type environment_type define a resource initialization strategy default manual minimum or parent git push upsun o resources init resource_initialization_strategy if your remote location isn t named upsun make sure you adjust the commands accordingly you can t use push options if you have a source integration set up the following example shows how through a single push you can activate your environment set a title for it set a parent environment for it and clone the data from its parent into it terminal git push upsun o environment status active o environment title my environment title o environment parent my parent environment o environment clone_parent_on_create true last modified on may 27 2026 was this page helpful yes no project isolation backup restore upsun developer home page github youtube x linkedin docs documentation tutorials api reference cli reference resources changelog upsun blog community support company about pricing careers github youtube x linkedin powered by this documentation is built and hosted on mintlify a developer documentation platform assistant responses are generated using ai and may contain mistakes