You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[ember-learn/ember-help-wanted][7]| List issues across ember repos that need community help | ember app |https://help-wanted.emberjs.com/|
22
+
|[ember-learn/guides-app][17]| TBD | ember app with prember |https://guides.emberjs.com/|
23
+
|[ember-learn/cli-guides-app][18]| new ember-cli docs | ember app with prember |https://ember-cli-guides.netlify.com/|
24
+
16
25
17
26
## On hosting preferences
18
27
19
28
[Heroku][8] sponsors our hosting & [Fastly][9] sponsors our CDN :heart:. While heroku does have [a fastly addon][10], for billing & maintenance reasons its easier to manage one fastly account with multiple service accounts configured in it. Heroku lets us have [pipelines][11] that enables us to have different environments like staging & production. It also lets us have review apps explained in the following section. We have hosted few apps directly on GitHub pages. These are apps where only content of the app is changed by internal teams that they don't require the sophisticated setup that the other apps enjoy.
20
29
21
-
## Heroku review apps
30
+
We've deployed apps prerendered with prember on [Netlify][19].
31
+
32
+
## Review apps
22
33
23
34
Heroku enables us to create [review apps][12] which are same as regular apps but lets us review changes in pull requests. They're automatically created when members with write access of a repo raise a PR (also depends on whether the pipeline is configured to auto-deploy). To create a review app for a PR raised by non-members, go to the heroku pipeline and manually create the review app. Review apps get deleted after few days of inactivity on the PR. They also get deployed only on successful builds on Travis.
24
35
36
+
Creation & maintenance of review apps on netlify is automated & doesn't require manual intervention.
37
+
25
38
## Heroku deployment
26
39
27
40
Heroku deployment doesn't require special deploy section on `.travis.yml` configuration file since we always setup github integration via the [heroku dashboard][13]. The deployment on heroku still checks to ensure that travis builds were successful before autodeploying the changes.
@@ -43,4 +56,7 @@ All our heroku apps are set to autodeploy `master` branch to their staging apps.
0 commit comments