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.

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

Add more guidance on manifest/space best practices #438

Closed
afeld opened this issue Sep 29, 2016 · 1 comment
Closed

Add more guidance on manifest/space best practices #438

afeld opened this issue Sep 29, 2016 · 1 comment
Labels
operations Platform operations, development, and support issues

Comments

@afeld
Copy link
Contributor

afeld commented Sep 29, 2016

I wrote this in Slack:

my recommendation these days:

  • have a base manifest that specifies the common configuration that will look the same across all spaces. this should include things like the name(s) for the application(s), the same service instance names, etc.
  • make a manifest per environment that inherits from the base one, specifying the environment-specific things, e.g. routes/hostnames, feature flags, etc.

See that conversation for more background. Could have sworn we had an issue/pull request around this already...apologies if this is a duplicate.

/cc @dogweather @LinuxBozo @cmc333333

@afeld
Copy link
Contributor Author

afeld commented Dec 14, 2016

Related: the relatively-new org creation script now creates dev, staging, and prod spaces by default, which should nudge people into structuring their deployments that way.

@mogul mogul removed the Icebox label Feb 2, 2017
@mogul mogul removed the F317 label Feb 13, 2017
@mogul mogul removed the SkyPorter label Feb 21, 2017
@suprenant suprenant changed the title add more guidance on manifest/space best practices Add more guidance on manifest/space best practices Jun 5, 2017
@brittag brittag added operations Platform operations, development, and support issues and removed Navigator labels Aug 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
operations Platform operations, development, and support issues
Projects
None yet
Development

No branches or pull requests

5 participants