Answers: <p>There are tools around the web for saving desktops. Still best solution I found out to be running a set of virtual machines on your computer, having one setup in one vm.</p>
  
  <p>That takes some space, but you can save the state of vm upon vm shut down and come back to exactly same state when you come back. Maybe sessions have died but the windows certainly are as you left them.</p>
  
  <p>Solution is stated on <a href="http://www.makeuseof.com/tag/save-restore-windows-session/" rel="nofollow noreferrer">http://www.makeuseof.com/tag/save-restore-windows-session/</a> and it is for windows but I suppose the same will apply for Linux vm too. </p>
  
Answers: CC BY-SA 3.0
Answers: 2017-09-29T16:18:26.650Z
Answers: 2017-09-29T16:18:26.650Z
Answers: mico
Body: <p>Working with DevOps toolchains requires switching contexts between code, dashboards and command line terminals (local and remote). That is just for one project - and many of us work in more than one.</p>
  
  <p>To reduce switching and navigating, folks and me too use more and more monitors - 4K (UHD) is a welcomed technology.</p>
  
  <p>Say altogether, a set of windows and terminals for a context is a DevOps viewport (or maybe there is a better word).</p>
  
  <p>Now, what are - if any - convenient means to "script" windows/terminals configurations as a CasC (Configuration as Code) artefact so you could easily load and switch your CI/CD environment viewports? </p>
  
  <ul>
  <li>Windows 10 environment?</li>
  <li>Ubuntu Linux environent?</li>
  </ul>
  
Comments: CC BY-SA 3.0
Comments: 2017-09-29T13:06:26.897Z
Comments: Care to elaborate on what you mean by a CaSC like artifact? I have never heard the term before.
Comments: Preston Martin
Comments: CC BY-SA 3.0
Comments: 2017-09-29T15:09:39.757Z
Comments: @PrestonM **C**onfiguration as **C**ode
Comments: Tensibai
Tags: <automation><casc>
Title: Workplace viewport scripting
UserDisplayName: Ta Mu
ThreadText: # Workplace viewport scripting
  
  (Asked by: username_0 on 2017-09-29)
  
  Working with DevOps toolchains requires switching contexts between code, dashboards and command line terminals (local and remote). That is just for one project - and many of us work in more than one.
  
  To reduce switching and navigating, folks and me too use more and more monitors - 4K (UHD) is a welcomed technology.
  
  Say altogether, a set of windows and terminals for a context is a DevOps viewport (or maybe there is a better word).
  
  Now, what are - if any - convenient means to "script" windows/terminals configurations as a CasC (Configuration as Code) artefact so you could easily load and switch your CI/CD environment viewports?
  
  * Windows 10 environment?
  * Ubuntu Linux environent?
  
  **Tags:** automation, casc
  
  > **Comments:**
  > **username_1**: Care to elaborate on what you mean by a CaSC like artifact? I have never heard the term before.  
  > **username_2**: @PrestonM **C**onfiguration as **C**ode  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2017-09-29. Score: 1
  
  There are tools around the web for saving desktops. Still best solution I found out to be running a set of virtual machines on your computer, having one setup in one vm.
  
  That takes some space, but you can save the state of vm upon vm shut down and come back to exactly same state when you come back. Maybe sessions have died but the windows certainly are as you left them.
  
  Solution is stated on <http://www.makeuseof.com/tag/save-restore-windows-session/> and it is for windows but I suppose the same will apply for Linux vm too.
  
  
  ---
  
  