├── .gitattributes ├── .mailmap ├── AUTHORS ├── LICENSE ├── code-of-conduct.md ├── contributing.md ├── package.json ├── readme.md └── tools └── update-authors.js /.gitattributes: -------------------------------------------------------------------------------- 1 | * text=auto 2 | readme.md merge=union 3 | -------------------------------------------------------------------------------- /.mailmap: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/aws-amplify-jp/awesome-aws-amplify-ja/b8240865d53b961dda15752d947bc2f73b03b42b/.mailmap -------------------------------------------------------------------------------- /AUTHORS: -------------------------------------------------------------------------------- 1 | # Authors ordered by first contribution. 2 | 3 | Daijiro Wachi 4 | Wataru Oguchi 5 | Yuhei Okazaki 6 | cohe aoki 7 | jaga 8 | AdachiShohei <41992406+adachishohei@users.noreply.github.com> 9 | MURAKAMI Masahiko 10 | 11 | # Generated by tools/update-authors.js 12 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of experience, 9 | nationality, personal appearance, race, religion, or sexual identity and 10 | orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at daijiro.wachi@gmail.com. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at [http://contributor-covenant.org/version/1/4][version] 72 | 73 | [homepage]: http://contributor-covenant.org 74 | [version]: http://contributor-covenant.org/version/1/4/ 75 | -------------------------------------------------------------------------------- /contributing.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | Please note that this project is released with a 4 | [Contributor Code of Conduct](code-of-conduct.md). By participating in this 5 | project you agree to abide by its terms. 6 | 7 | --- 8 | 9 | Ensure your pull request adheres to the following guidelines: 10 | 11 | - Make sure you take care of this 12 | - And this as well 13 | - And don't forget to check this 14 | 15 | Thank you for your suggestions! 16 | 17 | 18 | ## Updating your PR 19 | 20 | A lot of times, making a PR adhere to the standards above can be difficult. 21 | If the maintainers notice anything that we'd like changed, we'll ask you to 22 | edit your PR before we merge it. There's no need to open a new PR, just edit 23 | the existing one. If you're not sure how to do that, 24 | [here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) 25 | on the different ways you can update your PR so that we can merge it. 26 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "private": "true", 3 | "name": "awesome-aws-amplify-ja", 4 | "version": "1.0.0", 5 | "description": "日本語で書かれているAWS Amplifyのツール、チュートリアル、記事などのリンク集", 6 | "main": "index.js", 7 | "scripts": { 8 | "build": "tools/update-authors.js" 9 | }, 10 | "repository": { 11 | "type": "git", 12 | "url": "git+https://github.com/watilde/awesome-aws-amplify-ja.git" 13 | }, 14 | "keywords": [], 15 | "author": "Daijiro Wachi", 16 | "license": "MIT", 17 | "bugs": { 18 | "url": "https://github.com/watilde/awesome-aws-amplify-ja/issues" 19 | }, 20 | "homepage": "https://github.com/watilde/awesome-aws-amplify-ja#readme" 21 | } 22 | -------------------------------------------------------------------------------- /readme.md: -------------------------------------------------------------------------------- 1 | # Amplify学習リソース集 2 | > [![Awesome](https://awesome.re/badge.svg)](https://awesome.re)
3 | > 日本語で書かれているAWS Amplifyのツール、チュートリアル、記事などのリンク集です。
4 | > 英語版はこちら: https://github.com/dabit3/awesome-aws-amplify 5 | 6 | ## 追加方法 7 | 8 | PRにて受け付けています。[ガイドライン](https://github.com/aws-amplify-jp/awesome-aws-amplify-ja/blob/main/contributing.md) をご一読の上、[こちら](https://github.com/aws-amplify-jp/awesome-aws-amplify-ja/pulls)よりお送りください。 9 | 10 | ## イベント 11 | - [Amplify Boost Up](https://aws-amplify-jp.connpass.com/) 12 | 13 | ## Discord 14 | - [Amplify Japan User Group](https://discord.gg/2wVQ2D53Na) 15 | 16 | ## Amplifyとは 17 | - [スタートアップが AWS Amplify を使うべき3つの理由](https://aws.amazon.com/jp/blogs/startup/techblog-3reasons-amplify/) 18 | - [フロントエンドエンジニアに捧げるAWS Amplify Console](https://dev.classmethod.jp/articles/aws-amplify-console-guide-lines-for-frontend-engineer/) 19 | - [フロントエンドエンジニアのためのAWSアーキテクチャ](https://speakerdeck.com/tmizuma/hurontoentoensiniafalsetamefalseawsakitekutiya) 20 | - [AmplifyとAppSyncでモダンでイケてるWebサービスを爆速で立ち上げようぜ](https://dev.classmethod.jp/articles/amplify-appsync-bakusoku-devio2020/) 21 | - [AWS Amplify で始める、サクッとアプリ開発](https://aws.amazon.com/jp/builders-flash/202103/amplify-app-development/) 22 | 23 | ## 公式ワークショップ 24 | - [AWS で React アプリケーションを構築する](https://aws.amazon.com/jp/getting-started/hands-on/build-react-app-amplify-graphql/) 25 | - [CI/CD による React アプリの AWS へのデプロイ](https://aws.amazon.com/jp/getting-started/hands-on/deploy-react-app-cicd-amplify/) 26 | - [Flutter アプリケーションを構築する](https://docs.amplify.aws/flutter/start/quickstart/) 27 | 28 | ## 事例 29 | 30 | - [コーポレートサイトを誰にも気づかれず静的化したときの技術選択について](https://developer.hatenastaff.com/entry/2020/07/22/120000) 31 | - [AWS Amplify で実現する DX 時代のマインドチェンジ](https://speakerdeck.com/ksukenobe/aws-amplify-deshi-xian-suru-dx-shi-dai-falsemaindotienzi) 32 | - [Amplifyで実現した開発期間15日の路面電車乗務員勤務管理システムのフィールドテスト事例について](https://pages.awscloud.com/rs/112-TZM-766/images/EV_awsamplify-meetup-0731_Jul-2020_LT1.pdf) 33 | - [Amplify 山あり、谷あり奮闘記](https://speakerdeck.com/jyamamoto/amplifyshan-ari-gu-arifen-dou-ji) 34 | - [Amplify Meetup #01 わたしが AWS Amplify を使い続ける理由](https://speakerdeck.com/ksukenobe/amplify-meetup-number-01-watasiga-aws-amplify-woshi-isok-keruli-you) 35 | - [Amplify Console のビルド通知をSlackで受け取るためにやったこと](https://speakerdeck.com/youta1119/amplify-console-falsebirudotong-zhi-woslackdeshou-kequ-rutameniyatutakoto) 36 | - [AWS Amplify Console + CDKを用いて短納期・少人数・フルリモートで作る管理画面](https://dev.classmethod.jp/articles/showcase2020day2aws-amplify-console-cdk/) 37 | - [LabBase Nowの応募サイトをAWS Amplifyで爆速開発してみた](https://zenn.dev/guevara/articles/049324cc70f984d62dfe) 38 | 39 | ## Tips 40 | 41 | ### セキュリティ 42 | - [痒いところに手が届くAmplify](https://speakerdeck.com/yuukiyo/yang-itokoronishou-gajie-kuamplify) 43 | 44 | ### API 45 | - [AmplifyのAPI機能を使う際のTips](https://dev.classmethod.jp/articles/amplify-meetup-01-taewoo/) 46 | 47 | ### Amplify Console 48 | - [Amplify Consoleの通知をSlackに流す](https://qiita.com/fossamagna/items/70e4e399de59984ad3bb) 49 | 50 | 51 | ## チュートリアル 52 | 53 | ### React 54 | 55 | - [React+Amplify+AppSyncでリアルタイム掲示板アプリを15分で作り上げる](https://qiita.com/G-awa/items/a5b2cc7017b1eceeb002) 56 | - [AmplifyでReactアプリのデプロイ、CI/CDをする公式チュートリアルをやってみた](https://dev.classmethod.jp/articles/amplify-react-cicd-tutorial/) 57 | - [React + Amplify + AppSync + DynamoDB でサーバレスなWebアプリを作成する公式チュートリアルをやってみた](https://dev.classmethod.jp/articles/react-amplify-appsync-dynamodb-tutorial/) 58 | 59 | ### Vue.js 60 | - [AWS Amplify と Vue.js を用いた管理画面のサンプルプロジェクト](https://github.com/aws-amplify-jp/amplify-vue-management-console-example) 61 | - [AWS Amplify（Cognito）でLINEへソーシャルログインする](https://qiita.com/takeshi_hirosue/items/7de213590f6e9f9f6838) 62 | - [AWS Amplify と Vue.js を使って、基本的な認証と CRUD 操作ができる Web アプリケーションを作る](https://aws.amazon.com/jp/builders-flash/202008/amplify-crud-app/) 63 | - [AWS Amplify + Vue.js で簡単WEBアプリ作成](https://www.cresco.co.jp/blog/entry/11142/) 64 | - [AWS AmplifyをVue.jsで使い倒したい！（セットアップ・認証編）](https://qiita.com/jre233kei/items/d719159c6b0b44b3980d) 65 | - [AWS AmplifyをVue.jsで使い倒したい！（API編）](https://qiita.com/jre233kei/items/b47656059e1718363245) 66 | - [AWS AmplifyのUI Componentsを利用する](https://zenn.dev/ssshun/articles/e6c827f46640a9a657ed) 67 | - [Amplify で開発してみる #1 / API (GraphQL) その1 テーブル一つの実装](https://www.northdetail.co.jp/blog/905/) 68 | - [Amplify で開発してみる #2 / API (GraphQL) その2 テーブル連携した実装](https://www.northdetail.co.jp/blog/930/) 69 | - [Amplify で開発してみる #3 / Authentication と API (GraphQL) を連携した実装](https://www.northdetail.co.jp/blog/1039/) 70 | - [Amplify で開発してみる #4 / Subscriptions を使った API (GraphQL) のリアルタイムデータ連携](https://www.northdetail.co.jp/blog/1086/) 71 | - [AWS AmplifyとAmplify UI VueとVue.jsでログイン機能を構築してみた](https://qiita.com/dayjournal/items/d67529cf62efd055617b) 72 | 73 | ### Angular 74 | - [AWS AmplifyとAngular8を使ってCognitoでAWS Management Consoleにログインするページを作ってみる](https://dev.classmethod.jp/articles/aws-management-console-login-with-cognito-user-using-amplify-and-angular8/) 75 | - [AWS AmplifyとAngular8を使ってCognitoでQuickSightにログインするページを作ってみる](https://dev.classmethod.jp/articles/quicksight-login-with-cognito-user-using-amplify-and-angular8/) 76 | 77 | ### Next.js 78 | - [Next.js x Amplify boilerplate](https://github.com/kazukinagata/next-amplify-template) 79 | - [AmplifyがNext.jsとNuxt.jsを利用したSSR（Server Side Rendering）に対応しました](https://dev.classmethod.jp/articles/amplify-javascript-adds-server-side-rendering-support-frameworks-next-js-nuxt-js/) 80 | - [Next.js+TypeScript+AWS Amplify+RecoilでToDoリストを作る](https://qiita.com/Y_uuu/items/249dfcc794f101129b09) 81 | 82 | ### Amplify Hosting 83 | - [AWS Amplify CLI から AWS Amplify コンソールでアプリをホストする](https://aws.amazon.com/jp/blogs/news/host-your-apps-with-aws-amplify-console-from-the-aws-amplify-cli/) 84 | - [AWS Amplifyの公開設定を色々とためしてみた](https://qiita.com/dayjournal/items/c6e4ca20887a093560a0) 85 | - [AWS Amplifyで独自ドメインホスティング環境を構築してみた](https://qiita.com/dayjournal/items/57cb0a8232d11c6c99af) 86 | - [AWS AmplifyでGoogle Domainsの独自ドメインホスティング環境を構築してみた](https://qiita.com/dayjournal/items/bdeaa4a5bca42c4cfe9b) 87 | 88 | ### Amplify DataStore 89 | - [Amplify DataStore – GraphQL でオフラインアプリの開発を簡素化](https://aws.amazon.com/jp/blogs/news/amplify-datastore-simplify-development-of-offline-apps-with-graphql/) 90 | 91 | ### Flutter 92 | - [Amplify Flutterがリリースされました](https://dev.classmethod.jp/articles/what-new-amplify-flutter/) 93 | - [AWS AmplifyとFlutterでログイン機能を構築してみた](https://qiita.com/dayjournal/items/092d51dfb463bf8b8837) 94 | 95 | ### Amplify Studio 96 | - [AWS Amplify Studio – 最小限のプログラミングでFigmaからフルスタックのReactアプリを実現](https://aws.amazon.com/jp/blogs/news/aws-amplify-studio-figma-to-fullstack-react-app-with-minimal-programming/) 97 | - [アプリを爆速で開発 ! AWS Amplify Studio で出来ること](https://aws.amazon.com/jp/builders-flash/202203/amplify-studio-flash-development/) 98 | 99 | ### Amplify Geo 100 | - [Amplify GeoとVue.jsを組み合わせてマップアプリケーションを構築してみた](https://qiita.com/dayjournal/items/2aa8a29adc208739c375) 101 | - [Amplify Geoで住所検索機能を構築してみた](https://qiita.com/dayjournal/items/ecf954bcf43206f1b093) 102 | - [Amplify GeoとMapLibre GL Geocoderを組み合わせて住所検索機能を構築してみた](https://qiita.com/dayjournal/items/5383e6c72bb87877188a) 103 | - [Amazon Location Serviceの新マップスタイルをシンプルに表示してみた](https://qiita.com/dayjournal/items/f81d083126ddd51219a9) 104 | 105 | ## 動画 106 | 107 | ### Amplifyとは 108 | - [【AWS Black Belt Online Seminar】AWS Amplify](https://www.youtube.com/watch?v=A4HOzn7ERqE) 109 | - [AWS Startup Day 2020 技術系セッション | これからはじめる AWS Amplify](https://www.youtube.com/watch?v=zreoLmhFulA) 110 | - [AWS Startup Day 2020 技術系セッション | AWS Amplify 実践編](https://www.youtube.com/watch?v=2PNKAWgo_-c) 111 | 112 | ### React.js 113 | - [Amplify Week Day1 | AWS Startup Day](https://www.youtube.com/watch?v=mNs1naRRQRU) 114 | - [Amplify Week Day2 | AWS Startup Day](https://www.youtube.com/watch?v=_yxV2cnGPdk) 115 | - [Amplify Week Day3 | AWS Startup Day](https://www.youtube.com/watch?v=sIcWRERgJME) 116 | 117 | ## 記事検索 118 | 119 | - [はてなブックマーク](https://b.hatena.ne.jp/search/tag?q=Amplify) 120 | - [Qiita](https://qiita.com/tags/amplify) 121 | - [Zenn](https://zenn.dev/topics/amplify) 122 | - [Twitter](https://twitter.com/search?q=lang%3Aja%20AWSAmplify&src=typed_query&f=live) 123 | -------------------------------------------------------------------------------- /tools/update-authors.js: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env node 2 | // https://github.com/nodejs/node/blob/81fee0131071f916b244d6bdf2a3c5d48754371a/tools/update-authors.js 3 | // Usage: tools/update-author.js [--dry] 4 | // Passing --dry will redirect output to stdout rather than write to 'AUTHORS'. 5 | 'use strict'; 6 | const { spawn } = require('child_process'); 7 | const path = require('path'); 8 | const fs = require('fs'); 9 | const readline = require('readline'); 10 | 11 | class CaseIndifferentMap { 12 | _map = new Map(); 13 | 14 | get(key) { return this._map.get(key.toLowerCase()); } 15 | set(key, value) { return this._map.set(key.toLowerCase(), value); } 16 | } 17 | 18 | const log = spawn( 19 | 'git', 20 | // Inspect author name/email and body. 21 | ['log', '--reverse', '--format=Author: %aN <%aE>\n%b'], { 22 | stdio: ['inherit', 'pipe', 'inherit'] 23 | }); 24 | const rl = readline.createInterface({ input: log.stdout }); 25 | 26 | let output; 27 | if (process.argv.includes('--dry')) 28 | output = process.stdout; 29 | else 30 | output = fs.createWriteStream('AUTHORS'); 31 | 32 | output.write('# Authors ordered by first contribution.\n\n'); 33 | 34 | const mailmap = new CaseIndifferentMap(); 35 | { 36 | const lines = fs.readFileSync(path.resolve(__dirname, '../', '.mailmap'), 37 | { encoding: 'utf8' }).split('\n'); 38 | for (let line of lines) { 39 | line = line.trim(); 40 | if (line.startsWith('#') || line === '') continue; 41 | 42 | let match; 43 | // Replaced Name 44 | if (match = line.match(/^([^<]+)\s+(<[^>]+>)$/)) { 45 | mailmap.set(match[2], { author: match[1] }); 46 | // 47 | } else if (match = line.match(/^<([^>]+)>\s+(<[^>]+>)$/)) { 48 | mailmap.set(match[2], { email: match[1] }); 49 | // Replaced Name 50 | } else if (match = line.match(/^([^<]+)\s+(<[^>]+>)\s+(<[^>]+>)$/)) { 51 | mailmap.set(match[3], { 52 | author: match[1], email: match[2] 53 | }); 54 | // Replaced Name Original Name 55 | } else if (match = 56 | line.match(/^([^<]+)\s+(<[^>]+>)\s+([^<]+)\s+(<[^>]+>)$/)) { 57 | mailmap.set(match[3] + '\0' + match[4], { 58 | author: match[1], email: match[2] 59 | }); 60 | } else { 61 | console.warn('Unknown .mailmap format:', line); 62 | } 63 | } 64 | } 65 | 66 | const seen = new Set(); 67 | 68 | // Support regular git author metadata, as well as `Author:` and 69 | // `Co-authored-by:` in the message body. Both have been used in the past 70 | // to indicate multiple authors per commit, with the latter standardized 71 | // by GitHub now. 72 | const authorRe = 73 | /(^Author:|^Co-authored-by:)\s+(?[^<]+)\s+(?<[^>]+>)/i; 74 | rl.on('line', (line) => { 75 | const match = line.match(authorRe); 76 | if (!match) return; 77 | 78 | let { author, email } = match.groups; 79 | 80 | const replacement = mailmap.get(author + '\0' + email) || mailmap.get(email); 81 | if (replacement) { 82 | ({ author, email } = { author, email, ...replacement }); 83 | } 84 | 85 | if (seen.has(email) || 86 | /@chromium\.org/.test(email) || 87 | email === '') { 88 | return; 89 | } 90 | 91 | seen.add(email); 92 | output.write(`${author} ${email}\n`); 93 | }); 94 | 95 | rl.on('close', () => { 96 | output.end('\n# Generated by tools/update-authors.js\n'); 97 | }); 98 | --------------------------------------------------------------------------------