![]() Hosting and running your code for you, while taking care of authentication. ![]() Re-writing with Forge modules is more work, but brings with it the convenience, increased security, and trust of Tutorial, but Connect module equivalents is a good place to start. Option A: Re-writing with Forge modulesĪn in-depth discussion of how to approach swapping your Connect modules for Forge modules is beyond the scope of this You can migrate your Connect app functionality by making use of connectModules, re-writing with new Forge modules,įor more details on states of app migration, Step 2: Migrate your Connect app’s functionality To install your locally-running Connect app on to your development site.Įverything is now in place to begin the migration of your Connect app’s functionality to Forge. If you don’t know how to set up a test site, Install the app on a test site, so that you can test migrating the installation once the app has been migrated on toįorge. Match your internet-facing tunnel URL, then run node connect-app.js If you’re using the sample app, first edit the baseUrl variable value near the top of the connect-app.js file to In a separate terminal window, start your app. ![]() ![]() If you’re using ngrok with the sample app, run ngrok http -bind-tls=true 49998 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |