Chever-John opened a new issue, #300:
URL: https://github.com/apache/apisix-docker/issues/300
# Issue description
## Current situation
Now we have many following commands:
```sh
make build-on-centos : Build apache/apisix:xx-centos image
make build-on-alpine : Build apache/apisix:xx-alpine image
make build-on-alpine-dev : Build apache/apisix:xx-alpine-dev image
make build-on-alpine-local : Build apache/apisix:xx-alpine-local image
make push-on-centos : Push apache/apisix:xx-centos image
make push-on-alpine : Push apache/apisix:xx-alpine image
make push-on-alpine : Push apache/apisix:dev image
make build-on-alpine-cn : Build apache/apisix:xx-alpine image (for
chinese)
make build-all-in-one : Build All in one Docker container for
Apache APISIX
make build-dashboard-all-in-one : Build All in one Docker container for
Apache APISIX-dashboard
make save-centos-tar : tar apache/apisix:xx-centos image
make save-alpine-tar : tar apache/apisix:xx-alpine image
make build-dashboard-centos : Build apache/dashboard:tag image on centos
make build-dashboard-alpine : Build apache/dashboard:tag image on alpine
make push-multiarch-dashbaord : Build and push multiarch
apache/dashboard:tag image
make save-dashboard-centos-tar : tar apache/apisix-dashboard:tag image
make save-dashboard-alpine-tar : tar apache/apisix-dashboard:tag image
make help : Show Makefile rules
```
Although we have many useful commands, the fact is that our README.md file
does not cover them all.
A good documentation organization can facilitate developers to add some
useful content.
I want to finish this task to redesign the structure of the README.md
## Proposal
My tentative plan for the file structure is as follows, I would be grateful
for some advice.
- build
- apisix
- centos
- alpine
- dev
- local
- cn
- dashboard
- centos
- Alpine
- All-in-one
- apisix
- dashboard
- push
- centos
- alpine
- cn
- multiarch-dashboard
- tar
- apisix
- centos
- alpine
- dashboard
- centos
- Alpine
Organize the way docker is deployed in a way. This will help apisix
developers in their daily development.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
