You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently hardcore the APISIX version in the blog or doc, which has misled some newcomers when they read an old blog version. This also makes updating the latest APISIX version in the doc harder, because we need to change several places.
Desired State
Let's add a static file containing the version numbers, and provide a simple one-liner command to get the version number in the doc. The one-liner should be very simple so that we can copy & paste it everywhere.
The text was updated successfully, but these errors were encountered:
We could maybe make a shell script which installs APISIX. It could have flags that user can set to install LTS version or edge releases. Then the one liner will be to pull the .sh file and execute it. All installation logic will be in the script.
I found “docs/*/config.json” and “version.lua” contain version_number 。
As a newcomer, I am a little confused about "in the doc"。It is not clear that the context of the "one-liner" execute
Please leave this issue aside 😊 and I will be available 2 ~ 3 weeks later, and then moving forward with the whole document program with @navendu-pottekkat.
Current State
We currently hardcore the APISIX version in the blog or doc, which has misled some newcomers when they read an old blog version. This also makes updating the latest APISIX version in the doc harder, because we need to change several places.
Desired State
Let's add a static file containing the version numbers, and provide a simple one-liner command to get the version number in the doc. The one-liner should be very simple so that we can copy & paste it everywhere.
The text was updated successfully, but these errors were encountered: