docs: migrated images to cloudinary from imgur (#2569)
This commit is contained in:
Shahed Nasser
@@ -34,27 +34,27 @@ The first step is to create an Algolia app for your Medusa server. To create one
|
||||
|
||||
On the Applications page, click on the New application button at the top right.
|
||||
|
||||
|
||||
|
||||
|
||||
In the new page that opens, optionally enter a name for the application and choose a subscription plan. You can choose the Free plan for now, but it’s recommended to switch to the Pay-as-you-go plan as your business grows.
|
||||
|
||||
|
||||
|
||||
|
||||
Once you’re done, click on the Next Step button. If you picked Pay as you go service, you’ll need to enter billing details before you proceed.
|
||||
|
||||
Then, you’ll be asked to pick a region for your application. Once you’re done, click on Review Application Details.
|
||||
|
||||
|
||||
|
||||
|
||||
In the last step, you’ll see a summary of your order. If all looks good, check the checkboxes at the end of the form to indicate that you agree to the terms and conditions. Then, click on the Create Application button.
|
||||
|
||||
|
||||
|
||||
|
||||
## Retrieve API Keys
|
||||
|
||||
To retrieve the API keys that you’ll use in the next sections, go to Settings, then choose API Keys in the Team and Access section.
|
||||
|
||||
|
||||
|
||||
|
||||
On this page, you’ll find the Application ID, Search-Only API Key, and Admin API Key. You’ll need the Application ID and Admin API Key for the Medusa server. As for the storefront, you’ll need the Application ID and Search-Only API Key.
|
||||
|
||||
@@ -64,7 +64,7 @@ If you have more than one application in your Algolia account, make sure you’r
|
||||
|
||||
:::
|
||||
|
||||
|
||||
|
||||
|
||||
## Install the Algolia Plugin
|
||||
|
||||
@@ -128,7 +128,7 @@ npm run start
|
||||
|
||||
The quickest way to test that the integration is working is by sending a `POST` request to `/store/products/search`. This endpoint accepts a `q` body parameter of the query to search for and returns in the result the products that match this query.
|
||||
|
||||
|
||||
|
||||
|
||||
You can also check that the products are properly indexed by opening your Algolia dashboard and choosing Search from the left sidebar. You’ll find your products that are on your Medusa server added there.
|
||||
|
||||
@@ -138,7 +138,7 @@ If you have more than one application on your Algolia account, make sure you’r
|
||||
|
||||
:::
|
||||
|
||||
|
||||
|
||||
|
||||
### Add or Update Products
|
||||
|
||||
@@ -211,7 +211,7 @@ To make sure the Next.js storefront properly displays the products in the search
|
||||
|
||||
:::
|
||||
|
||||
|
||||
|
||||
|
||||
## Add to Gatsby and React-Based Storefronts
|
||||
|
||||
@@ -325,7 +325,7 @@ And add the `Search` component in the returned JSX before `RegionPopover`:
|
||||
|
||||
If you run your Gatsby storefront while the Medusa server is running, you should find a search bar in the header of the page. Try entering a query to search through the products in your store.
|
||||
|
||||
|
||||
|
||||
|
||||
## What’s Next
|
||||
|
||||
|
||||
@@ -118,31 +118,31 @@ This runs the Contentful migration in that file and makes the necessary changes
|
||||
|
||||
To check if the above migration worked, in your Contentful Space dashboard go to Content Models from the navigation bar. You should see the new content model Rich Text.
|
||||
|
||||
|
||||
|
||||
|
||||
The above migration also allows you to add Rich Text content to pages. To test this out, go to Content from the navigation bar and choose Page in the select field next to the search bar. This shows the available pages in your Contentful Space.
|
||||
|
||||
|
||||
|
||||
|
||||
Choose one of the pages. For example, the About page. Then, scroll down to the Add content button. If you click on it, you should be able to choose Rich Text under New Content.
|
||||
|
||||
|
||||
|
||||
|
||||
Click on Rich Text and a new form will open to create new Rich Text content. It has the same fields that you defined in the migration file.
|
||||
|
||||
|
||||
|
||||
|
||||
After adding the content you want, click on the Publish button on the right then go back to the About page editor.
|
||||
|
||||
|
||||
|
||||
|
||||
Similarly, in the About page editor, click on the Publish Changes button on the right to view these changes later in the storefront.
|
||||
|
||||
|
||||
|
||||
|
||||
Similarly, you can add Rich Text content to any product page.
|
||||
|
||||
|
||||
|
||||
|
||||
## Render New Content Models in the Storefront
|
||||
|
||||
@@ -238,7 +238,7 @@ npm run start
|
||||
|
||||
This runs the Gatsby storefront on `localhost:8000`. Go to the storefront in your browser and open the About page. You should see the Rich Text content you added.
|
||||
|
||||
|
||||
|
||||
|
||||
### Render Component in a Product Page
|
||||
|
||||
@@ -306,7 +306,7 @@ This loops over `contentModules` and if the type of the content is Rich Text, it
|
||||
|
||||
Restart the Gatsby storefront then open a product that you added Rich Text content to. You should see the Rich Text component at the end of the page.
|
||||
|
||||
|
||||
|
||||
|
||||
## What’s Next
|
||||
|
||||
|
||||
@@ -52,15 +52,15 @@ Set the value for `CONTENTFUL_ENV` to `master`.
|
||||
|
||||
To retrieve the value of `CONTENTFUL_SPACE_ID`, go to your [Contentful Space dashboard](https://app.contentful.com/). Then, choose Settings in the navigation bar and select API keys from the dropdown.
|
||||
|
||||
|
||||
|
||||
|
||||
On the APIs page, click Add API Key.
|
||||
|
||||
|
||||
|
||||
|
||||
In the form, enter a name for the API key and click Save.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, copy the value of Space ID and set it as the value of `CONTENTFUL_SPACE_ID`.
|
||||
|
||||
@@ -68,11 +68,11 @@ Then, copy the value of Space ID and set it as the value of `CONTENTFUL_SPACE_ID
|
||||
|
||||
Go back to the API Keys page and click on the Content management tokens tab.
|
||||
|
||||
|
||||
|
||||
|
||||
Click on Generate personal token. A pop-up will open where you have to enter a name for the token.
|
||||
|
||||
|
||||
|
||||
|
||||
Once you click Generate, a personal access token will be generated. Use it to set the value of `CONTENTFUL_ACCESS_TOKEN`.
|
||||
|
||||
@@ -141,7 +141,7 @@ npm run migrate:contentful
|
||||
|
||||
Once this command finishes executing, in your Contentful Space dashboard click on Content Model in the navigation bar. You should see a list of new content models added.
|
||||
|
||||
|
||||
|
||||
|
||||
### Seed Content to Contentful
|
||||
|
||||
@@ -155,7 +155,7 @@ npm run seed:contentful
|
||||
|
||||
After this command finishes running, in your Contentful Space dashboard click on Content in the navigation bar. You should see a list of new content added.
|
||||
|
||||
|
||||
|
||||
|
||||
### (Optional) Seed Medusa Database
|
||||
|
||||
@@ -177,7 +177,7 @@ npm run start
|
||||
|
||||
If you seeded the database with demo data, you should see that events related to the products are triggered.
|
||||
|
||||
|
||||
|
||||
|
||||
The Contentful integration ensures a two-way sync between the Medusa server and Contentful. So, when new products are added to Medusa, these products will be added to your Contentful Space as well.
|
||||
|
||||
@@ -195,7 +195,7 @@ To do that, open your Contentful Space Dashboard and click on Content in the Nav
|
||||
|
||||
Click on the checkbox at the top of the table to select all products then click Publish to publish these products.
|
||||
|
||||
|
||||
|
||||
|
||||
### Added Featured Products
|
||||
|
||||
@@ -203,19 +203,19 @@ On the homepage of the storefront, there’s a featured products tile that shows
|
||||
|
||||
To do that, open your Contentful Space Dashboard and click on Content in the Navigation bar. Make sure the select field next to the search bar is set to Any and search for Featured Products. You should find one content of the type Tile Section.
|
||||
|
||||
|
||||
|
||||
|
||||
Click on it. You should find on the page an empty Tiles section where you can add tiles and products.
|
||||
|
||||
|
||||
|
||||
|
||||
Click on Add content then on Add existing content and pick some of the products you want to show on the homepage.
|
||||
|
||||
|
||||
|
||||
|
||||
Once you’re done adding products, click on Publish changes in the right sidebar.
|
||||
|
||||
|
||||
|
||||
|
||||
## Setup Gatsby Storefront
|
||||
|
||||
@@ -250,7 +250,7 @@ To retrieve the value of `CONTENTFUL_ACCESS_TOKEN`, on your Contentful Space das
|
||||
|
||||
You should find the field "Content Delivery API - access token”. Copy its value and set it as the value of `CONTENTFUL_ACCESS_TOKEN`.
|
||||
|
||||
|
||||
|
||||
|
||||
### Start Storefront
|
||||
|
||||
@@ -262,7 +262,7 @@ npm run start
|
||||
|
||||
This starts the storefront at `localhost:8000`. Open it in your browser and you should see on the homepage the Featured Product section with the products you chose on Contentful.
|
||||
|
||||
|
||||
|
||||
|
||||
## Make Changes to Content
|
||||
|
||||
|
||||
@@ -80,11 +80,11 @@ Try sending a `POST` request to `/mailchimp/subscribe` with the following JSON b
|
||||
|
||||
If the subscription is successful, a `200` response code will be returned with `OK` message.
|
||||
|
||||
|
||||
|
||||
|
||||
If you check your Mailchimp dashboard, you should find the email added to your Audience list.
|
||||
|
||||
|
||||
|
||||
|
||||
### With Additional Data
|
||||
|
||||
@@ -173,7 +173,7 @@ export default function NewsletterForm() {
|
||||
|
||||
This will result in a subscription form similar to the following:
|
||||
|
||||
|
||||
|
||||
|
||||
If you try entering an email and clicking Subscribe, the email will be subscribed to your Mailchimp newsletter successfully.
|
||||
|
||||
|
||||
@@ -89,11 +89,11 @@ npm run start
|
||||
|
||||
The quickest way to test that the integration is working is by sending a `POST` request to `/store/products/search`. This endpoint accepts a `q` body parameter of the query to search for and returns in the result the products that match this query.
|
||||
|
||||
|
||||
|
||||
|
||||
You can also check that the products are properly indexed by opening the MeiliSearch host URL in your browser, which is `http://127.0.0.1:7700/` by default. You’ll find your products that are on your Medusa server added there.
|
||||
|
||||
|
||||
|
||||
|
||||
### Add or Update Products
|
||||
|
||||
@@ -170,7 +170,7 @@ To make sure the Next.js storefront properly displays the products in the search
|
||||
|
||||
:::
|
||||
|
||||
|
||||
|
||||
|
||||
### Add to Gatsby and React-Based Storefronts
|
||||
|
||||
@@ -284,7 +284,7 @@ And add the `Search` component in the returned JSX before `RegionPopover`:
|
||||
|
||||
If you run your Gatsby storefront while the Medusa server and the MeiliSearch instance are running, you should find a search bar in the header of the page. Try entering a query to search through the products in your store.
|
||||
|
||||
|
||||
|
||||
|
||||
## What’s Next
|
||||
|
||||
|
||||
@@ -32,19 +32,19 @@ minio server ~/minio --console-address :9090 --address :9001
|
||||
|
||||
After installing MinIO and logging into the Console, click on “Create Bucket” to create a new bucket that will store the files of your Medusa server.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, in the form, enter a name for the bucket and click on Create Bucket. By MinIO’s requirement, the name can only consist of lower case characters, numbers, dots (`.`), and hyphens (`-`).
|
||||
|
||||
|
||||
|
||||
|
||||
After creating the bucket, click on the cog icon at the top right to configure the bucket.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, click on the edit icon next to Access Policy. This will open a pop-up.
|
||||
|
||||
|
||||
|
||||
|
||||
In the pop-up, change the selected value to “public” and click Set.
|
||||
|
||||
@@ -58,15 +58,15 @@ Changing the Access Policy to public will allow anyone to access your bucket. Av
|
||||
|
||||
From the sidebar of your MinIO console, click on Identity then Service Accounts.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, click on Create Service Account.
|
||||
|
||||
|
||||
|
||||
|
||||
This will generate a random Access Key and Secret Key for you.
|
||||
|
||||
|
||||
|
||||
|
||||
Click on Create. A pop-up will then show the value for your Access Key and Secret Key. Copy them to use in the next section.
|
||||
|
||||
@@ -119,7 +119,7 @@ If you have multiple storage plugins configured, the last plugin declared in the
|
||||
|
||||
Run your Medusa server alongside the [Medusa Admin](../admin/quickstart.md) to try out your new file service. Upon editing or creating products, you can now upload thumbnails and images, that are stored in a MinIO server.
|
||||
|
||||
|
||||
|
||||
|
||||
## Private Buckets
|
||||
|
||||
|
||||
@@ -127,7 +127,7 @@ Make sure to replace `<YOUR_CLIENT_ID>` with your PayPal Client ID.
|
||||
|
||||
Now, if you run your Medusa server and your storefront, on checkout you’ll be able to use PayPal].
|
||||
|
||||
|
||||
|
||||
|
||||
You can test out the payment with PayPal using your sandbox account.
|
||||
|
||||
@@ -276,7 +276,7 @@ That’s all you need to integrate PayPal into the Gatsby storefront.
|
||||
|
||||
Now, start the Medusa server and the Gatsby storefront server. Try adding an item into the cart and proceeding to checkout. When you reach the payment step, you should see the PayPal button.
|
||||
|
||||
|
||||
|
||||
|
||||
You can test out the payment with PayPal using your sandbox account.
|
||||
|
||||
@@ -382,13 +382,13 @@ You can then import this component where you want to show it in your storefront.
|
||||
|
||||
If you run the Medusa server and the storefront server, you should see the PayPal button on checkout.
|
||||
|
||||
|
||||
|
||||
|
||||
## Capture Payments
|
||||
|
||||
After the customer places an order, you can see the order on the admin panel. In the payment information under the “Payment” section, you should see a “Capture” button.
|
||||
|
||||
|
||||
|
||||
|
||||
Clicking this button lets you capture the payment for an order. You can also refund payments if an order has captured payments.
|
||||
|
||||
|
||||
@@ -22,23 +22,23 @@ You need to [create an AWS account](https://console.aws.amazon.com/console/home?
|
||||
|
||||
On your AWS Console, search for S3 in the search box at the top. Then, choose the first result you see which should be S3 under the Services category.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, on the new page that opens, click on Create Bucket button at the top right of the Buckets table.
|
||||
|
||||
|
||||
|
||||
|
||||
The Create Bucket form will open. In the General Configuration section enter a name for the bucket and choose a region for the bucket. Both of the values of these fields are important as you’ll use them throughout the documentation.
|
||||
|
||||
|
||||
|
||||
|
||||
Next, in the Object Ownership section, choose ACLs enabled. Then, two radio buttons will show below it. Choose Bucket owner preferred.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, in the “Block Public Access settings for this bucket” section, uncheck the “Block all public access” checkbox. This shows a warning message at the bottom of the section with another checkbox. Check the checkbox to ensure you understand that objects in the bucket are publicly accessible.
|
||||
|
||||
|
||||
|
||||
|
||||
You can leave the rest of the fields in the form as is and scroll down to the end of the page. Then, click on the Create Bucket button.
|
||||
|
||||
@@ -46,7 +46,7 @@ You can leave the rest of the fields in the form as is and scroll down to the en
|
||||
|
||||
On the page of the bucket you just created, click on the Permissions tab. Then, scroll down until you find the Bucket policy section. Click on Edit in that section.
|
||||
|
||||
|
||||
|
||||
|
||||
In the Edit Bucket Policy page, enter the following in the field:
|
||||
|
||||
@@ -142,11 +142,11 @@ Then, you can either test the plugin using the [REST APIs](https://docs.medusajs
|
||||
|
||||
On the Medusa Admin, create a new product and, in the Images section, upload an image then click Save. If the integration was successful, the product image will be uploaded successfully.
|
||||
|
||||
|
||||
|
||||
|
||||
You can also check that the image was uploaded on the S3 bucket’s page.
|
||||
|
||||
|
||||
|
||||
|
||||
## Next.js Storefront Configuration
|
||||
|
||||
|
||||
@@ -52,23 +52,23 @@ You need to [create a Segment account](https://app.segment.com/signup/) to follo
|
||||
|
||||
On your Segment dashboard, choose Catalog from the sidebar under Connections.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, in the catalog list find the Server category and choose Node.js from the list.
|
||||
|
||||
|
||||
|
||||
|
||||
This opens a new side menu. In the side menu, click on Add Source.
|
||||
|
||||
|
||||
|
||||
|
||||
This opens a new page to create a Node.js source. Enter the name of the source then click Add Source.
|
||||
|
||||
|
||||
|
||||
|
||||
On the new source dashboard, you should find a Write Key. You’ll use this key in the next section after you install the Segment plugin on your Medusa server.
|
||||
|
||||
|
||||
|
||||
|
||||
### Optional: Add Destination
|
||||
|
||||
@@ -76,11 +76,11 @@ After you create the Segment source, you can add destinations. This is where the
|
||||
|
||||
To add a destination, on the same Segment source page, click on Add Destination in the Destinations section.
|
||||
|
||||
|
||||
|
||||
|
||||
You can then choose from a list of destinations such as Google Universal Analytics or Facebook Pixel.
|
||||
|
||||
|
||||
|
||||
|
||||
The process of integrating each destination is different, so you must follow the steps detailed in Segment for each destination you choose.
|
||||
|
||||
@@ -126,7 +126,7 @@ Then, try triggering one of the [mentioned events earlier in this document](#eve
|
||||
|
||||
After you place an order, on the Segment source that you created, click on the Debugger tab. You should see at least one event triggered for each order you place. If you click on the event, you can see the order details are passed to the event.
|
||||
|
||||
|
||||
|
||||
|
||||
If you added a destination, you can also check your destination to make sure the data is reflected there.
|
||||
|
||||
@@ -183,7 +183,7 @@ The `SegmentServer` also provides the method `identify` to tie a user to their a
|
||||
|
||||
After adding the above subscriber, run your server again if it isn’t running and create a customer using the REST APIs or one of the Medusa storefronts. If you check the Debugger in your Segment source, you should see a new event “Customer Created” tracked. If you click on it, you’ll see the data you passed to the `track` method.
|
||||
|
||||
|
||||
|
||||
|
||||
## What’s Next
|
||||
|
||||
|
||||
@@ -3959,7 +3959,7 @@ If you don’t have a storefront installed, check out the [Gatsby](../starters/g
|
||||
|
||||
You can also track analytics related to emails sent from the SendGrid dashboard.
|
||||
|
||||
|
||||
|
||||
|
||||
## What’s Next
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ The first step is to create a Slack app. This app will be connected to your work
|
||||
|
||||
Go to [Slack API](https://api.slack.com/) and click Create app. This will take you to a new page with a pop-up. In the pop-up, choose From scratch.
|
||||
|
||||
|
||||
|
||||
|
||||
You’ll then need to enter some info like the App name and the workspace it will be connected to. Once you’re done, the app will be created.
|
||||
|
||||
@@ -49,17 +49,17 @@ You’ll then need to enter some info like the App name and the workspace it wil
|
||||
|
||||
To activate Incoming Webhooks, choose Features > Incoming Webhooks from the sidebar. At first, it will be disabled so make sure to enable it by switching the toggle.
|
||||
|
||||
|
||||
|
||||
|
||||
### Add New Webhook
|
||||
|
||||
After activating Incoming Webhooks, on the same page scroll down and click on the Add New Webhook to Workspace button.
|
||||
|
||||
|
||||
|
||||
|
||||
After that, choose the channel to send the notifications to. You can also choose a DM to send the notifications to. Once you’re done click Allow.
|
||||
|
||||
|
||||
|
||||
|
||||
This will create a new Webhook with a URL which you can see in the table at the end of the Incoming Webhooks page. Copy the URL as you’ll use it in the next section.
|
||||
|
||||
|
||||
@@ -28,15 +28,15 @@ You need to [create a DigitalOcean account](https://cloud.digitalocean.com/regi
|
||||
|
||||
In your DigitalOcean account, click on the Create button at the top right, then choose Spaces from the dropdown.
|
||||
|
||||
|
||||
|
||||
|
||||
In the Create a Space form, you can choose any of the regions listed. You can alternatively leave all settings as they are and scroll down to the Finalize and Create section.
|
||||
|
||||
|
||||
|
||||
|
||||
In the Finalize and Create section, enter a name for the field “Choose a unique name”. You’ll use this name later in the integration with Medusa. Also, select the project you want to add the new Space to.
|
||||
|
||||
|
||||
|
||||
|
||||
Once you’re done, click on the Create a Space button. This creates the Space and redirects you to the Space’s page.
|
||||
|
||||
@@ -44,15 +44,15 @@ Once you’re done, click on the Create a Space button. This creates the Space a
|
||||
|
||||
Choose API from the bottom of the sidebar.
|
||||
|
||||
|
||||
|
||||
|
||||
This opens the Application & API page. Scroll down to Spaces Access Keys and click the Generate New Key button.
|
||||
|
||||
|
||||
|
||||
|
||||
This shows a table with the Name field editable. Enter a name for the Access Keys and click on the checkmark button to save and generate the Spaces access keys.
|
||||
|
||||
|
||||
|
||||
|
||||
Then, two keys will be available under the Key column of the table. The first one is the Access Key ID and the second is the Secret Access Key. Copy both as you’ll use them later.
|
||||
|
||||
@@ -84,12 +84,12 @@ Where:
|
||||
|
||||
1. `<YOUR_SPACE_URL>` is the URL of your Space which you can find on the Space’s page below the Space’s name.
|
||||
|
||||
|
||||
|
||||
|
||||
2. `<YOUR_SPACE_NAME>` is the name of your Space.
|
||||
3. `<YOUR_SPACE_ENDPOINT>` is your Space’s endpoint which can be found by going to your Space’s page, clicking on the Settings tab, and scrolling to the Endpoint section.
|
||||
|
||||
|
||||
|
||||
|
||||
4. `<YOUR_ACCESS_KEY_ID>` and `<YOUR_SECRET_ACCESS_KEY>` are the keys you created in the previous section.
|
||||
|
||||
@@ -129,11 +129,11 @@ Then, you can either test the plugin using the [REST APIs](https://docs.medusaj
|
||||
|
||||
On the Medusa Admin, create a new product and, in the Images section, upload an image then click Save. If the integration was successful, the product image will be uploaded successfully.
|
||||
|
||||
|
||||
|
||||
|
||||
You can also check that the image was uploaded on the Space’s page.
|
||||
|
||||
|
||||
|
||||
|
||||
## Next.js Storefront Configuration
|
||||
|
||||
|
||||
@@ -36,7 +36,7 @@ This creates the Strapi project in the directory `strapi-medusa`.
|
||||
|
||||
Once the installation is finished, the Strapi development server will run on `localhost:1337`. A new page will also open in your default browser to create a new admin user and log in.
|
||||
|
||||
|
||||
|
||||
|
||||
Once you log in, you can access the Strapi dashboard.
|
||||
|
||||
@@ -44,11 +44,11 @@ Once you log in, you can access the Strapi dashboard.
|
||||
|
||||
The Strapi plugin in Medusa requires the credentials of a Strapi user. To create a new user, go to Content Manager, then choose User under Collection Types.
|
||||
|
||||
|
||||
|
||||
|
||||
Click on the Create new entry button at the top right. This opens a new form to enter the user’s details.
|
||||
|
||||
|
||||
|
||||
|
||||
Enter the user’s username, email, and password. Once you’re done, click on the Save button at the top right.
|
||||
|
||||
@@ -58,7 +58,7 @@ By default, created users have the “Authenticated” role. Before you start us
|
||||
|
||||
On your Strapi dashboard, go to Settings → Roles → Authenticated. Then, under the Permissions section, expand the accordion of each content model type and check the Select All checkbox.
|
||||
|
||||
|
||||
|
||||
|
||||
Once you’re done, click the Save button at the top right.
|
||||
|
||||
|
||||
@@ -131,7 +131,7 @@ Make sure to replace `<YOUR_PUBLISHABLE_KEY>` with your Stripe Publishable Key.
|
||||
|
||||
Now, if you run your Medusa server and your storefront, on checkout you’ll be able to use Stripe.
|
||||
|
||||
|
||||
|
||||
|
||||
### Add to Gatsby Storefront
|
||||
|
||||
@@ -151,7 +151,7 @@ You might find this environment variable already available so you can just repla
|
||||
|
||||
Now, if you run your Medusa server and your storefront, on checkout you’ll be able to use Stripe.
|
||||
|
||||
|
||||
|
||||
|
||||
### Add to Custom Storefront
|
||||
|
||||
@@ -344,13 +344,13 @@ Once the promise resolves you can handle the errors, if there are any. If not, y
|
||||
|
||||
If you run your server and storefront now, you’ll see the Stripe UI element and you’ll be able to make orders.
|
||||
|
||||
|
||||
|
||||
|
||||
## Capture Payments
|
||||
|
||||
After the customer places an order, you’ll be able to see the order on the admin panel. In the payment information under the “Payment” section, you should see a “Capture” button.
|
||||
|
||||
|
||||
|
||||
|
||||
Clicking this button allows you to capture the payment for an order. You can also refund payments if an order has captured payments.
|
||||
|
||||
|
||||
@@ -120,7 +120,7 @@ If you’re on a Twilio trial make sure that the phone number you entered on che
|
||||
|
||||
:::
|
||||
|
||||
|
||||
|
||||
|
||||
## What’s Next
|
||||
|
||||
|
||||
Reference in New Issue
Block a user