What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hello, one question regarding deploy file reference. In
Hello,
one question regarding deploy file reference.
In https://documentation.spryker.com/v3/docs/en/deploy-file-reference-version-1-201907 there is no mention of assets
and composer
keys which are defined in https://github.com/spryker-shop/b2c-demo-shop/blob/master/deploy.yml for example.
Is there any documentation on how should it be used and which options are available?
Comments
-
Just to sure: I see your link is a bit different from what I have found: https://documentation.spryker.com/docs/deploy-file-reference-10
0 -
we do aware of this issue that sometimes you can arrive at the older version of the article. For now if you see a βversionβ in the URL - try to find this article via the search, there might be more actual version
0 -
Thank you for the info. I see that, when following your link,
composer
section is present, but still i am missing theassets
section0 -
might be missing for now, true! Do you have maybe a concrete question, so that someone could help you even before the doc will be released?
0 -
we noticed that development mode is used during the build process on our production environment. This is leading to assets not being built for production env (no versioning for example because production config was not used). We investigated it a bit and found out that there is additional
assets
section indeploy.yml
so now i am wondering if this will solve the problem we have. Also what doescompression: gzip: static: true level: 5
mean? Should we keep it like this or can it be left out. Does it have any impact on built assets and how they should be included in the project?
0 -
cc @ULYHPR789
0 -
Documentation is still WIP.
0 -
assets:
section is responsible for 2 things:β’ Building assets
β’ Frontend image
If you use docker/sdk frontend image,assets: compression:
will impact on nginx rules. If you do not use you can skip or neither leave the section.0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 930 Developer Corner
- 788 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 33 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random