Update user_guide.md with upgrade instructions
This commit is contained in:
@@ -15,6 +15,7 @@
|
|||||||
- [Connecting BAP Beckn Adapter to BAP Software](#connecting-bap-beckn-adapter-to-bapbuyer-side-software)
|
- [Connecting BAP Beckn Adapter to BAP Software](#connecting-bap-beckn-adapter-to-bapbuyer-side-software)
|
||||||
- [Connecting BPP Beckn Adapter to BPP Software](#connecting-bpp-beckn-adapter-to-bppseller-side-software)
|
- [Connecting BPP Beckn Adapter to BPP Software](#connecting-bpp-beckn-adapter-to-bppseller-side-software)
|
||||||
- [Running Beckn-ONIX locally](#running-beckn-onix-locally)
|
- [Running Beckn-ONIX locally](#running-beckn-onix-locally)
|
||||||
|
- [Upgrading to a new version](#upgrading-to-a-new-version)
|
||||||
- [Appendix A - subdomain/domain name configuration](#appendix-a---registering-or-adding-domain-or-subdomains)
|
- [Appendix A - subdomain/domain name configuration](#appendix-a---registering-or-adding-domain-or-subdomains)
|
||||||
- [Appendix B - Nginx reverse proxy configuration](#appendix-b---nginx-reverse-proxy-configuration)
|
- [Appendix B - Nginx reverse proxy configuration](#appendix-b---nginx-reverse-proxy-configuration)
|
||||||
|
|
||||||
@@ -242,6 +243,15 @@ Refer to the [core specification](https://github.com/beckn/protocol-specificatio
|
|||||||
|
|
||||||
- In order for people new to Beckn who want to try out Beckn on their own machine, choose the option to "Set up a network on your local machine" in the main screen. The all in one installation has preconfigured values for variables and so pretty much does not ask for any input.
|
- In order for people new to Beckn who want to try out Beckn on their own machine, choose the option to "Set up a network on your local machine" in the main screen. The all in one installation has preconfigured values for variables and so pretty much does not ask for any input.
|
||||||
|
|
||||||
|
## Upgrading to a new version
|
||||||
|
- The following commands illustrate upgrade of the docker image for Protocol Server (here BPP). Use similar process for other components
|
||||||
|
|
||||||
|
```
|
||||||
|
docker compose -f docker-compose-bpp.yml down
|
||||||
|
docker rmi fidedocker/protocol-server
|
||||||
|
docker compose -f docker-compose-bpp.yml up -d
|
||||||
|
```
|
||||||
|
|
||||||
## Appendix A - Registering or adding domain or subdomains
|
## Appendix A - Registering or adding domain or subdomains
|
||||||
|
|
||||||
All the components of Beckn network need to be publicly accessible. Using domain names for them is the easiest. There are two options for domain names. One is a separate domain name for each component(e.g. registrybp.io). Second is to use subdomains for the individual componetns (e.g. onix-registry.becknprotocol.io , onix-gateway.becknprotocol.io etc). Which one of these two to use depends on the business requirement. For example if an organization is the network facilitator, they might go for a domain name for the registry instead of subdomain. In the examples given above we have primarily used subdomain approach.
|
All the components of Beckn network need to be publicly accessible. Using domain names for them is the easiest. There are two options for domain names. One is a separate domain name for each component(e.g. registrybp.io). Second is to use subdomains for the individual componetns (e.g. onix-registry.becknprotocol.io , onix-gateway.becknprotocol.io etc). Which one of these two to use depends on the business requirement. For example if an organization is the network facilitator, they might go for a domain name for the registry instead of subdomain. In the examples given above we have primarily used subdomain approach.
|
||||||
|
|||||||
Reference in New Issue
Block a user