- 
                Notifications
    
You must be signed in to change notification settings  - Fork 196
 
Add basic apphosting.yaml in next.js and angular starter templates. #255
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| # Settings for Backend (on Cloud Run). | ||
| # See https://firebase.google.com/docs/app-hosting/configure#cloud-run. | ||
| runConfig: | ||
| minInstances: 0 | ||
| # maxInstances: 100 | ||
| # concurrency: 100 | ||
| # cpu: 2 | ||
                
      
                  taeold marked this conversation as resolved.
               
              
                Outdated
          
            Show resolved
            Hide resolved
         | 
||
| # memoryMiB: 1024 | ||
| 
     | 
||
| # Environment variables and secrets. | ||
| # env: | ||
| # Configure environment variables. | ||
| # See https://firebase.google.com/docs/app-hosting/configure#user-defined-environment. | ||
| # - variable: MESSAGE | ||
| # value: Hello world! | ||
| # availability: | ||
| # - BUILD | ||
| # - RUNTIME | ||
| 
     | 
||
| # Configure secrets | ||
| # See https://firebase.google.com/docs/app-hosting/configure#secret-parameters | ||
| # - variable: API_KEY | ||
| # secret: myApiKeySecret | ||
| Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| # Settings for Backend (on Cloud Run). | ||
| # See https://firebase.google.com/docs/app-hosting/configure#cloud-run. | ||
| runConfig: | ||
| minInstances: 0 | ||
| 
         There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why does Angular comment out all values but Nex.tjs does not? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see that you use the variable in Next.js, but then why not use it in Angular SSR? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I have no idea how to use env vars in angular. If you do, welcoming a PR! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. process.env doesn't work? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. no  | 
||
| # maxInstances: 100 | ||
| # concurrency: 100 | ||
| # cpu: 2 | ||
| # memoryMiB: 1024 | ||
| 
     | 
||
| # Environment variables and secrets. | ||
| env: | ||
| # Configure environment variables. | ||
| # See https://firebase.google.com/docs/app-hosting/configure#user-defined-environment. | ||
| - variable: MESSAGE | ||
| value: Hello world! | ||
| availability: | ||
| - BUILD | ||
| - RUNTIME | ||
| 
     | 
||
| # Configure secrets | ||
| # See https://firebase.google.com/docs/app-hosting/configure#secret-parameters | ||
| # - variable: API_KEY | ||
| # secret: myApiKeySecret | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should have a header explaining the use of environment-specific apphosting.yaml overrides?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'd rather point the users to public doc so we don't have 2 separate places to track documentations on how to use env specific overrides.