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

AngularJS - HTML enhanced for web apps!

58861 0 0 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			`{`
			`"hosting": {`
chore(ci): copy deployment files inside the respective Firebase directories We have the `scripts/{code,docs}.angularjs.org-firebase/` directories, which contain the necessary code and config for deploying built files to the `code-angularjs-org` and `docs-angularjs-org` Firebase projects respectively. Previously, some of the files that needed to be deployed to Firebase (or Google Cloud) were placed outside these directories (e.g. in `deploy/{code,docs}/`). Since these files are only used for deploying to Firebase/Google Cloud, this commit changes the deployment process to instead copy the files inside the directories. In a subsequent commit, this will allow simplifying the deployment process, by running it from inside each directory instead of having to copy the `firebase.json` files to the repository root (and adjust the paths). These are the destination directory changes: \| Before \| After \| \|--------------\|---------------------------------------------\| \| deploy/code/ \| scripts/code.angularjs.org-firebase/deploy/ \| \| deploy/docs/ \| scripts/docs.angularjs.org-firebase/deploy/ \| 2021-02-05 20:45:13 +02:00			`"public": "deploy",`
chore(errors.angularjs.org): add project with redirects to docs.angularjs.org 2018-01-18 13:35:55 +01:00			`"redirects": [`
			`{`
			`"source": "/error/:namespace\\::error*",`
			`"destination": "/error/:namespace/:error*",`
			`"type": 302`
			`}`
			`],`
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			`"rewrites": [`
			`{`
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			`"source": "*/!(.@(jpg\|jpeg\|gif\|png\|html\|js\|map\|json\|css\|svg\|ttf\|txt\|woff\|woff2\|eot\|xml))",`
			`"function": "sendFile"`
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): allow crawling but not indexing of partials/ The sitemap.xml might also prevent the indexing, as the partials are not listed. Related to #16432 Closes #16457 2018-02-15 11:54:14 +01:00			`],`
			`"headers": [`
chore(docs.angularjs.org): add csp headers for csp example Fixes #16270 2018-03-01 12:03:51 +01:00			`{`
			`"source": "/examples/*.csp/.html",`
			`"headers": [{`
			`"key": "Content-Security-Policy",`
			`"value": "default-src 'self'"`
			`}]`
			`},`
chore(docs.angularjs.org): allow crawling but not indexing of partials/ The sitemap.xml might also prevent the indexing, as the partials are not listed. Related to #16432 Closes #16457 2018-02-15 11:54:14 +01:00			`{`
chore(docs.angularjs.org): allow crawling of examples, don't deploy e2e test files 2018-02-18 20:32:04 +01:00			`"source": "/Error404.html",`
			`"headers" : [{`
			`"key" : "X-Robots-Tag",`
			`"value" : "noindex"`
			`}]`
			`},`
			`{`
			`"source": "/@(partials\|examples)/**",`
chore(docs.angularjs.org): allow crawling but not indexing of partials/ The sitemap.xml might also prevent the indexing, as the partials are not listed. Related to #16432 Closes #16457 2018-02-15 11:54:14 +01:00			`"headers" : [{`
			`"key" : "X-Robots-Tag",`
			`"value" : "noindex"`
			`}]`
			`}`
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			`}`