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
{{ message }}
This repository was archived by the owner on Oct 1, 2025. It is now read-only.
! <li>{{ visit.timestamp.ctime }} from {{ visit.visitor }}</li>
271
-
{% endfor %}
272
-
</ul>
273
-
274
-
--- 8,14 ----
275
-
<h3>Last 10 visits</h3>
276
-
<ul>
277
-
{% for visit in visits %}
278
-
! <li>{{ visit.timestamp.ctime() }} from {{ visit.visitor }}</li>
279
-
{% endfor %}
280
-
</ul>
281
-
282
-
In the next step, we will migrate from App Engine NDB to Google Cloud NDB, a key step because after you complete *that*, you can either stop there or be presented with a variety of options to choose from.
205
+
## Next
206
+
207
+
[**Step 2:**](/step2-flask-cloudndb-py2) The next tutorial involves migrating from App Engine NDB to Google Cloud NDB, a key step because after you switch to the Cloud library, many options become available to you.
Copy file name to clipboardExpand all lines: step2-flask-cloudndb-py2/README.md
+8-96Lines changed: 8 additions & 96 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,7 @@ App Engine services have blossomed into their own products, and App Engine's Dat
18
18
1. Update `requirements.txt` to include the Cloud NDB library (`google-cloud-ndb`).
19
19
1. Update `app.yaml` to reference a pair of 3rd-party bundled packages: `grpcio` and `setuptools`
20
20
1. Update `appengine_config.py` to use the `pkg_resources` tool (which comes with `setuptools`) so App Engine can access [3rd-party libraries already available on Google servers](https://cloud.google.com/appengine/docs/standard/python/tools/built-in-libraries-27) so users don't have to list them in `requirements.txt` nor `pip install` them.
21
+
1. Similarly, [gRPC](http://grpc.io) is used by all [*Google Cloud* client libraries](https://cloud.google.com/apis/docs/cloud-client-libraries), and `grpcio` is the gRPC package for Python and thus required.
21
22
1. Switch application code to use the Cloud NDB client library
22
23
23
24
### Configuration
@@ -155,99 +156,10 @@ def fetch_visits(limit):
155
156
156
157
---
157
158
158
-
## Summary
159
-
160
-
For this migration step, here are the contextual `diff`s:
Common subdirectories: step1-flask-gaendb-py2/templates and step2-flask-cloudndb-py2/templates
247
-
248
-
From here, you have some flexibility as to your next move. You can...
249
-
250
-
- Continue to use NDB but migrate your app to a container executing serverlessly on Cloud Run (see `step2a-flask-cloudndb-py2-cloudrun`)
251
-
- Port your app to Python 3 (see `step2-flask-cloudndb-py3`)
252
-
- Combine both of the above steps (migrate to Python 3 *and* Cloud Run; no example provided but extrapolate from above)
253
-
- Further modernize Datastore access from Cloud NDB to the (official) Cloud Datastore library (how users *outside of* App Engine access Cloud Datastore) (see `step3-flask-datastore-py2`)
159
+
## Next
160
+
161
+
From here, there's flexibility as to your next move. Choose any of these options:
162
+
163
+
- [**Step 2:**](/step2-flask-cloudndb-py3) Port your app to Python 3 to get you on the next generation App Engine runtime as Python 2 has reached its end-of-life.
164
+
- [**Step 4:**](/step4-cloudndb-cloudrun-py2) Continue to use NDB but migrate your app to a container executing serverlessly on Cloud Run.
165
+
- [**Step 3:**](/step3-flask-datastore-py2) Further modernize Datastore access from Cloud NDB to the (official) Cloud Datastore library (how users *outside of* App Engine access Cloud Datastore).
0 commit comments