Blame: scripts/docs.angularjs.org-firebase/readme.firebase.docs.md - angular/angular.js

AngularJS - HTML enhanced for web apps!

0 0 5 JavaScript

chore(*): deploy (docs\|code) .angularjs.org to Firebase via Travis - code.angularjs.org and docs.angularjs.org are two separate Firebase projects - both are automatically deployed via Travis config - Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy stage runs a single job with both deployments (actual deployment depends on the state of the commit) - docs. is deployed directly to Firebase hosting - code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the files - jenkins builds still push the code builds to the code.angularjs.org Github repository Closes #9674 Closes #16093 2017-07-13 11:14:55 +02:00			`Firebase for docs.angularjs.org`
			`===============================`

chore(docs.angularjs.org): serve snapshots for googlebot This commit restores serving the plain partials (content) when a docs page is accessed with ?_escaped_fragment_=. The Google Ajax Crawler accesses these urls when the page has `<meta type="fragment" content="!">` is set. During the migration to Firebase, this was lost, which resulted in Google dropping the docs almost completely from the index. We are using a Firebase cloud function to serve the partials. Since we cannot access the static hosted files from the function, we have to deploy them as part of the function directory instead, from which they can be read. Related to #16432 Related to #16417 2018-02-12 10:49:19 +01:00			`# Continuous integration`

chore(ci): move over to CircleCi config This commit gets rid of all references to Travis and, belatedly, Jenkins. Now all CI is done on CircleCI and releases are run locally. The CI no longer updates the docs and code.angularjs.org for jobs that are not on the `master` branch. During releases, the docs and code should be uploaded manually. 2020-05-21 09:13:46 +01:00			`The docs are deployed to Google Firebase hosting via a CI deployment config, which expects`
			`firebase.json to be in the repository root, which is done by a Grunt task`
			(`firebaseDocsJsonForCI` which is included in `prepareDeploy`).
			The `firebaseDocsJsonForCI` task modifies the paths in the `firebase.json` and copies it to the
			`repository root.`
chore(docs.angularjs.org): serve snapshots for googlebot This commit restores serving the plain partials (content) when a docs page is accessed with ?_escaped_fragment_=. The Google Ajax Crawler accesses these urls when the page has `<meta type="fragment" content="!">` is set. During the migration to Firebase, this was lost, which resulted in Google dropping the docs almost completely from the index. We are using a Firebase cloud function to serve the partials. Since we cannot access the static hosted files from the function, we have to deploy them as part of the function directory instead, from which they can be read. Related to #16432 Related to #16417 2018-02-12 10:49:19 +01:00
chore(ci): move over to CircleCi config This commit gets rid of all references to Travis and, belatedly, Jenkins. Now all CI is done on CircleCI and releases are run locally. The CI no longer updates the docs and code.angularjs.org for jobs that are not on the `master` branch. During releases, the docs and code should be uploaded manually. 2020-05-21 09:13:46 +01:00			`See .circleci/config.yml for the complete deployment config and build steps.`
chore(docs.angularjs.org): serve snapshots for googlebot This commit restores serving the plain partials (content) when a docs page is accessed with ?_escaped_fragment_=. The Google Ajax Crawler accesses these urls when the page has `<meta type="fragment" content="!">` is set. During the migration to Firebase, this was lost, which resulted in Google dropping the docs almost completely from the index. We are using a Firebase cloud function to serve the partials. Since we cannot access the static hosted files from the function, we have to deploy them as part of the function directory instead, from which they can be read. Related to #16432 Related to #16417 2018-02-12 10:49:19 +01:00
			`# Serving locally:`

			- Run `grunt:prepareDeploy`.
			`This copies docs content files into deploy/docs and the partials for Search Engine AJAX`
			`Crawling into ./functions/content.`
chore(*): deploy (docs\|code) .angularjs.org to Firebase via Travis - code.angularjs.org and docs.angularjs.org are two separate Firebase projects - both are automatically deployed via Travis config - Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy stage runs a single job with both deployments (actual deployment depends on the state of the commit) - docs. is deployed directly to Firebase hosting - code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the files - jenkins builds still push the code builds to the code.angularjs.org Github repository Closes #9674 Closes #16093 2017-07-13 11:14:55 +02:00
chore(docs.angularjs.org): serve snapshots for googlebot This commit restores serving the plain partials (content) when a docs page is accessed with ?_escaped_fragment_=. The Google Ajax Crawler accesses these urls when the page has `<meta type="fragment" content="!">` is set. During the migration to Firebase, this was lost, which resulted in Google dropping the docs almost completely from the index. We are using a Firebase cloud function to serve the partials. Since we cannot access the static hosted files from the function, we have to deploy them as part of the function directory instead, from which they can be read. Related to #16432 Related to #16417 2018-02-12 10:49:19 +01:00			- Run `firebase serve --only functions,hosting`
			`Creates a server at localhost:5000 that serves from deploy/docs and uses the local function`
chore(*): deploy (docs\|code) .angularjs.org to Firebase via Travis - code.angularjs.org and docs.angularjs.org are two separate Firebase projects - both are automatically deployed via Travis config - Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy stage runs a single job with both deployments (actual deployment depends on the state of the commit) - docs. is deployed directly to Firebase hosting - code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the files - jenkins builds still push the code builds to the code.angularjs.org Github repository Closes #9674 Closes #16093 2017-07-13 11:14:55 +02:00
			`See /scripts/code.angularjs.org-firebase/readme.firebase.code.md for the firebase deployment to`
chore(docs.angularjs.org): install firebase dependencies before deploying Firebase is trying to execute our functions code locally in order to parse the triggers. Install npm dependencies to avoid errors like: ``` Error: Error parsing triggers: Cannot find module 'firebase-functions' ``` Closes #16453 2018-02-13 01:25:34 +02:00			`code.angularjs.org`