Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Next-build server running per Tugboat environment #10068

Closed
1 of 10 tasks
Tracked by #10903
jkalexander7 opened this issue Aug 4, 2022 · 1 comment
Closed
1 of 10 tasks
Tracked by #10903

Next-build server running per Tugboat environment #10068

jkalexander7 opened this issue Aug 4, 2022 · 1 comment
Labels
Accelerated Publishing DevOps CMS team practice area Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages.

Comments

@jkalexander7
Copy link

jkalexander7 commented Aug 4, 2022 •
edited
Loading

Description

Tugboat CMS instances will need a next-build 'dev' server running in order to provide preview to the CMS. Note that "dev" in this context does not mean the dev environment, i.e. dev.cms.va.gov, but rather, a running next-build server running in 'dev' mode (yarn dev) that is available to provide preview of next-build output to the CMS.

Implementation details

The server must be available at a secure URL. next-build itself is responsible for starting itself as a secure server.

The CMS needs to be able to either construct the URL to the next-build preview server, or it needs to be provided that URL via an environment variable.

Preview servers should refresh according to the rules of the given environment. IOW:

  • Tugboat preview servers should refresh on a nightly basis, along with the nightly rebuild process.

Acceptance Criteria

  • A next-build dev server is available at a secure domain for each environment
  • The base url/domain is either known or can be provided to the corresponding CMS environment.
  • Environment variables are added to next-build in accordance to the environment it is running in

CMS Team

Please check the team(s) that will do this work.

  • Program
  • Platform CMS Team
  • Sitewide Crew
  • ⭐️ Sitewide CMS
  • ⭐️ Public Websites
  • ⭐️ Facilities
  • ⭐️ User support
@TheBoatyMcBoatFace TheBoatyMcBoatFace added the next-build FE Repository that will replace content-build. Uses NextJS, builds static pages. label Dec 23, 2022
@jilladams jilladams added the CMS Team CMS Product team that manages both editor exp and devops label Jan 25, 2023
@EWashb EWashb added the Icebox Deprioritized for now label Feb 16, 2023
@timcosgrove timcosgrove removed the CMS Team CMS Product team that manages both editor exp and devops label Jun 9, 2023
@timcosgrove timcosgrove mentioned this issue Jun 9, 2023
Open
@timcosgrove timcosgrove added Needs refining Issue status and removed Icebox Deprioritized for now labels Sep 12, 2023
@tjheffner
Copy link
Contributor

This is complete as of #15936

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Accelerated Publishing DevOps CMS team practice area Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@timcosgrove @tjheffner @TheBoatyMcBoatFace @jilladams @EWashb @jkalexander7