Giter Site home page Giter Site logo

spryker / spryker-docs Goto Github PK

View Code? Open in Web Editor NEW
12.0 58.0 91.0 131.67 MB

This repository is for the Spryker documentation available at https://docs.spryker.com.

Home Page: https://docs.spryker.com

Dockerfile 0.09% Ruby 8.64% HTML 15.40% CSS 4.25% JavaScript 12.03% Shell 2.04% SCSS 57.55%

spryker-docs's Introduction

Spryker documentation

This repository contains the documentation for the Spryker documentation portal.

Installation

To build the documentation site locally, see building the documentation site.

Build with Docker

To build the documentation site with Docker, run this command: docker run --rm --volume="$PWD:/srv/jekyll" --volume="$PWD/vendor/bundle:/usr/local/bundle" -p 4000:4000 jekyll/jekyll:4.2.0 jekyll serve --incremental --livereload

Contribute

For the specific Markdown syntax we use in documentation, see Markdown syntax. For the general style, syntax, and formatting rules, see Style, syntax, formatting, and general rules.

To suggest changes, follow the steps:

  1. Fork the repository.
  2. In your forked repository, go to the document you want to edit. The actual documents are in the docs/ directory.
  3. To edit the document, click the pencil icon in the top right menu.
  4. Add the needed changes.
  5. In the Commit changes pane, describe your changes and click Commit changes. This shows the updated document.
  6. To go to the main page of the repository, click Code.
  7. Next to This branch is 1 commit ahead of spryker:master., click Contribute > Open pull request.
  8. Enter a Title.
  9. For Write, enter a description of your changes.
  10. Click Create pull request.
  11. To confirm that the PR is ready to merge, set a label, like in progress, tech review needed, or TW review needed.

That’s it! Your pull request has been created. Once we review and approve the changes, they will be published on the documentation website.

Contributors

Thank you to all our contributors!

spryker-docs's People

Contributors

abitskil avatar alexslawinski avatar andriitserkovnyi avatar artem-png avatar asaulenko avatar asmarovydlo avatar asonunique avatar az-joss avatar danilmoro3 avatar demkos avatar dmiseev avatar dmytroklymanspryker avatar gibmirmilch avatar helen-laktionova avatar ievgen-malykhin avatar ilyakubanov avatar jeremyfourna avatar lenadoc avatar michbeck avatar michelleegan11 avatar nperetyatko avatar profuel avatar romanhavrylko avatar skliarzfort avatar supproduction avatar thomaslehnerspryker avatar tobi-or-not-tobi avatar tobi812 avatar vadymsachenko avatar vladislavstrelchenko avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

spryker-docs's Issues

Fix wrong API term on two pages

These two pages use "Backend API" when it actually should say "Zed API" because they are still using the old API. Only modules that use the new backend API should use "Backend API" in the documentation.

Environment Variable Documentation

We noticed there are ~160 environment variables defined for a spryker project.
May i ask you to provide a documentation in form of a table?

Here some examples:

Environment Variables

  1. 'SPRYKER_LOG_STDERR'
  2. 'SPRYKER_LOG_STDOUT'
  3. 'SPRYKER_BE_HOST'
  4. 'SPRYKER_FE_HOST'
  5. 'DEVELOPMENT_CONSOLE_COMMANDS'
  6. 'SPRYKER_TRUSTED_HOSTS'
  7. 'SPRYKER_ZED_REQUEST_TOKEN'
  8. 'SPRYKER_OAUTH_KEY_PRIVATE'
  9. 'SPRYKER_OAUTH_KEY_PUBLIC'
  10. 'SPRYKER_OAUTH_ENCRYPTION_KEY'
  11. 'SPRYKER_OAUTH_CLIENT_IDENTIFIER'
  12. 'SPRYKER_OAUTH_CLIENT_SECRET'
  13. 'SPRYKER_OAUTH_CLIENT_CONFIGURATION'
  14. 'SPRYKER_ZED_REQUEST_TOKEN'
  15. 'SPRYKER_DB_ENGINE'
  16. 'SPRYKER_DB_HOST'
  17. 'SPRYKER_DB_PORT'
  18. 'SPRYKER_DB_USERNAME'
  19. 'SPRYKER_DB_PASSWORD'
  20. 'SPRYKER_DB_DATABASE'
  21. 'SPRYKER_DB_REPLICAS'
  22. 'SPRYKER_SEARCH_HOST'
  23. 'SPRYKER_SEARCH_PROTOCOL'
  24. 'SPRYKER_SEARCH_PORT'
  25. 'SPRYKER_SEARCH_BASIC_AUTH'
  26. 'SPRYKER_SEARCH_INDEX_PREFIX'
  27. 'SPRYKER_KEY_VALUE_STORE_ENGINE'
  28. 'SPRYKER_KEY_VALUE_STORE_PROTOCOL'
  29. 'SPRYKER_KEY_VALUE_STORE_HOST'
  30. 'SPRYKER_KEY_VALUE_STORE_PORT'
  31. 'SPRYKER_KEY_VALUE_STORE_PASSWORD'
  32. 'SPRYKER_KEY_VALUE_STORE_NAMESPACE'
  33. 'SPRYKER_KEY_VALUE_STORE_SOURCE_NAMES'
  34. 'SPRYKER_KEY_VALUE_STORE_CONNECTION_OPTIONS'
  35. 'SPRYKER_SESSION_FE_PROTOCOL'
  36. 'SPRYKER_SESSION_FE_HOST'
  37. 'SPRYKER_SESSION_FE_PORT'
  38. 'SPRYKER_SESSION_FE_PASSWORD'
  39. 'SPRYKER_SESSION_FE_NAMESPACE'
  40. 'SPRYKER_SESSION_BE_PROTOCOL'
  41. 'SPRYKER_SESSION_BE_PORT'
  42. 'SPRYKER_SESSION_BE_PASSWORD'
  43. 'SPRYKER_SESSION_BE_NAMESPACE'
  44. 'SPRYKER_ZED_SESSION_COOKIE_SAMESITE'
  45. 'SPRYKER_LOG_STDERR'
  46. 'SPRYKER_BROKER_API_HOST'
  47. 'SPRYKER_BROKER_API_PORT'
  48. 'SPRYKER_BROKER_API_USERNAME'
  49. 'SPRYKER_BROKER_API_PASSWORD'
  50. 'SPRYKER_BROKER_NAMESPACE'
    1. 'SPRYKER_BROKER_PASSWORD'
  51. 'SPRYKER_BROKER_USERNAME'
  52. 'SPRYKER_BROKER_HOST'
  53. 'SPRYKER_BROKER_PORT'
  54. 'SPRYKER_BROKER_PASSWORD'
  55. 'SPRYKER_BROKER_USERNAME'
  56. 'SPRYKER_BROKER_CONNECTIONS'
  57. 'SPRYKER_JENKINS_CSRF_PROTECTION_ENABLED'
  58. 'SPRYKER_SCHEDULER_PROTOCOL'
  59. 'SPRYKER_SCHEDULER_HOST'
  60. 'SPRYKER_SCHEDULER_PORT'
  61. 'SPRYKER_JENKINS_TEMPLATE_PATH'
  62. 'SPRYKER_SMTP_HOST'
  63. 'SPRYKER_SMTP_PORT'
  64. 'SPRYKER_SMTP_ENCRYPTION'
  65. 'SPRYKER_SMTP_AUTH_MODE'
  66. 'SPRYKER_SMTP_USERNAME'
  67. 'SPRYKER_SMTP_PASSWORD'
  68. 'SPRYKER_MAIL_SENDER_EMAIL'
  69. 'SPRYKER_MAIL_SENDER_NAME'
  70. 'SPRYKER_ZED_SSL_ENABLED'
  71. 'SPRYKER_ZED_PORT'
  72. 'SPRYKER_ZED_HOST'
  73. 'SPRYKER_FE_PORT'
  74. 'SPRYKER_GLUE_APPLICATION_CORS_ALLOW_ORIGIN'
  75. 'SPRYKER_GLUE_BACKEND_HOST'
  76. 'SPRYKER_GLUE_STOREFRONT_HOST'
  77. 'SPRYKER_DEBUG_ENABLED'
  78. 'SPRYKER_DEBUG_PROPEL_ENABLED'
  79. 'SPRYKER_TESTING_ENABLED'
  80. 'DEVELOPMENT_CONSOLE_COMMANDS'
  81. 'SPRYKER_DEBUG_DEPRECATIONS_ENABLED'
  82. 'SPRYKER_BROKER_HOST'
  83. 'SPRYKER_BROKER_PORT'
  84. 'SPRYKER_BROKER_PASSWORD'
  85. 'SPRYKER_BROKER_USERNAME'
  86. 'SPRYKER_SSL_ENABLE'
  87. 'SPRYKER_BE_HOST'
  88. 'SPRYKER_API_HOST'
  89. 'SPRYKER_API_PORT'
  90. 'APPLICATION_ENV'

After Performing Step Getting error

[zed-backoffice] [backoffice_us] - [2022-08-28T06:56:02.464722+00:00] defaultLogger.ERROR: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'spy_customer.description' in 'field list' [] []

Inconsistent examples for Glue Resource Plugin implementation

On the page
https://docs.spryker.com/docs/scos/dev/glue-api-guides/202204.0/decoupled-glue-infrastructure/how-to-guides/routing/how-to-create-a-storefront-resource.html
it shows how to implement \Pyz\Glue\ModuleRestApi\Plugin\JsonConventionModuleResource

There are 2 problems with that:

  1. It implements JsonApiResourceInterface which is not present in any use section and doesn't exist in the codebase at all
  2. It conflicts with the approach that is used in the https://docs.spryker.com/docs/scos/dev/glue-api-guides/202204.0/glue-api-tutorials/implement-a-rest-api-resource.html#route-requests-to-your-controller for WishlistsResourceRoutePlugin

By the way the approach from second points implements \Spryker\Glue\GlueApplicationExtension\Dependency\Plugin\ResourceRoutePluginInterface so it's not clear what should I use.

Thanks

Tutorial Checkout

Guys i get this error...
From this Tutorial

YVES Exception
ErrorException - FATAL ERROR - Access level to Pyz\Yves\CheckoutPage\Plugin\Router\CheckoutPageRouteProviderPlugin::CHECKOUT_VOUCHER must be public (as in class SprykerShop\Yves\CheckoutPage\Plugin\Router\CheckoutPageRouteProviderPlugin)
in /data/src/Pyz/Yves/CheckoutPage/Plugin/Router/CheckoutPageRouteProviderPlugin.php (7)

Url:/en/checkout/address

Trace:

#0 /data/vendor/spryker/error-handler/src/Spryker/Shared/ErrorHandler/ErrorHandlerEnvironment.php(107): Spryker\Shared\ErrorHandler\ErrorHandler->handleFatal()
#1 [internal function]: Spryker\Shared\ErrorHandler\ErrorHandlerEnvironment->Spryker\Shared\ErrorHandler\{closure}()
#2 {main}

after i change die CONST to public i get this...

ErrorException - FATAL ERROR - Could not check compatibility between Pyz\Yves\CheckoutPage\Plugin\Router\CheckoutPageRouteProviderPlugin::addRoutes(Pyz\Yves\CheckoutPage\Plugin\Router\RouteCollection $routeCollection): Pyz\Yves\CheckoutPage\Plugin\Router\RouteCollection and SprykerShop\Yves\CheckoutPage\Plugin\Router\CheckoutPageRouteProviderPlugin::addRoutes(Spryker\Yves\Router\Route\RouteCollection $routeCollection): Spryker\Yves\Router\Route\RouteCollection, because class Pyz\Yves\CheckoutPage\Plugin\Router\RouteCollection is not available
in /data/src/Pyz/Yves/CheckoutPage/Plugin/Router/CheckoutPageRouteProviderPlugin.php (21)

Url:/en/checkout/address

Trace:

#0 /data/vendor/spryker/error-handler/src/Spryker/Shared/ErrorHandler/ErrorHandlerEnvironment.php(107): Spryker\Shared\ErrorHandler\ErrorHandler->handleFatal()
#1 [internal function]: Spryker\Shared\ErrorHandler\ErrorHandlerEnvironment->Spryker\Shared\ErrorHandler\{closure}()
#2 {main}

i fix this with use Spryker\Yves\Router\Route\RouteCollection;
after i get this

An exception has been thrown during the rendering of a template ("None of the chained routers were able to generate route: Route 'checkout-test' not found, Route 'Route 'checkout-test' not found' not found").

Guys u need to Update your Docs πŸ‘

File resolver updates are missing from S3 Import documentation

If the file you're trying to import from the S3 Bucket doesn't exist in the local folder the import process will throw an error. This is due to a validation vendor/spryker/data-import/src/Spryker/Zed/DataImport/Business/Model/DataReader/FileResolver/FileResolver.php:63 that checks if the file exists in the file system.

The FileResolver.php file also needs to be overridden and replaced with a function to check whether the file exists in the S3 Bucket or not.

Wrong hosts entry for Backoffice and missing credentials

Dear,
using docker-sdk in Linux it automatically give the entries to be added in /etc/hosts:

sudo bash -c "echo '127.0.0.1 backend-api.at.spryker.local backend-api.de.spryker.local backend-api.us.spryker.local backend-gateway.at.spryker.local backend-gateway.de.spryker.local backend-gateway.us.spryker.local backoffice.at.spryker.local backoffice.de.spryker.local backoffice.us.spryker.local glue.at.spryker.local glue.de.spryker.local glue.us.spryker.local mail.spryker.local queue.spryker.local scheduler.spryker.local spryker.local swagger.spryker.local yves.at.spryker.local yves.de.spryker.local yves.us.spryker.local' >> /etc/hosts

It is different of what written in doc and miss the zed.* entries.
The same problem with Endpoint table.
I don't know which is the correct endpoints, if it is a doc mistake or sdk error.
On the same doc page there is no indication on how to get the credential for acceding Backoffice endpoint (found in src/Pyz/Zed/User/UserConfig.php).
Thanks.
Ivan

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.