forked from vdods/FabricWebApp
-
Notifications
You must be signed in to change notification settings - Fork 12
/
Makefile
180 lines (151 loc) · 9.63 KB
/
Makefile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
# PHONY targets have no dependencies and they will be built unconditionally upon request.
.PHONY: generated-artifacts initialization-org0.skraukosaur.com initialization-org1.skraukosaur.com initialization-org2.skraukosaur.com initialization-www.skraukosaur.com initialization inspect-initialized-volumes up up-detached logs-follow down down-full down-chaincode down-chaincode-full show-all-generated-resources rm-www-image rm-state-volumes rm-node-modules rm-chaincode-docker-resources clean
# This is also hardcoded in .env, so if you change it here, you must change it there. Note that
# it must be in all-lowercase, as docker-compose changes it to lowercase anyway.
COMPOSE_PROJECT_NAME := fabricwebapp
GENERATED_ARTIFACTS_VOLUME := $(COMPOSE_PROJECT_NAME)_generated_artifacts__volume
COM_EXAMPLE_ORG0_VOLUMES := $(COMPOSE_PROJECT_NAME)_com_skraukosaur_org0_ca__volume $(COMPOSE_PROJECT_NAME)_com_skraukosaur_org0_peer0__volume $(COMPOSE_PROJECT_NAME)_com_skraukosaur_org0_peer1__volume
COM_EXAMPLE_ORG1_VOLUMES := $(COMPOSE_PROJECT_NAME)_com_skraukosaur_org1_ca__volume $(COMPOSE_PROJECT_NAME)_com_skraukosaur_org1_peer0__volume $(COMPOSE_PROJECT_NAME)_com_skraukosaur_org1_peer1__volume
COM_EXAMPLE_ORG2_VOLUMES := $(COMPOSE_PROJECT_NAME)_com_skraukosaur_org2_ca__volume $(COMPOSE_PROJECT_NAME)_com_skraukosaur_org2_orderer__volume
COM_EXAMPLE_WWW_VOLUMES := $(COMPOSE_PROJECT_NAME)_com_skraukosaur_www__config_volume
# Default make rule
all:
@echo "See README.md for info on make targets."
generated-artifacts:
docker-compose -f docker/generated-artifacts.yaml up crypto_config
docker-compose -f docker/generated-artifacts.yaml up channel_config
# This removes stopped containers, and importantly, the anonymous volume created by the fact that
# the channel_config service uses the image hyperledger/fabric-tools:x86_64-1.0.1, which creates
# an anonymous volume.
docker-compose -f docker/generated-artifacts.yaml rm -v --force
# This command succeeds if and only if the specified volumes exist -- TODO: This doesn't actually check
# what we want, because docker-compose creates all these volumes upon startup, regardless of what happens later.
docker volume inspect $(GENERATED_ARTIFACTS_VOLUME)
down-generated-artifacts:
docker-compose -f docker/generated-artifacts.yaml down
# TODO: Put failsafes in to prevent calling this twice?
initialization-org0.skraukosaur.com:
# This command succeeds if and only if the specified volumes exist
docker volume inspect $(GENERATED_ARTIFACTS_VOLUME)
docker-compose -f docker/initialization.yaml up com_skraukosaur_org0__initialize
# This command succeeds if and only if the specified volumes exist
docker volume inspect $(COM_EXAMPLE_ORG0_VOLUMES)
initialization-org1.skraukosaur.com:
# This command succeeds if and only if the specified volumes exist
docker volume inspect $(GENERATED_ARTIFACTS_VOLUME)
docker-compose -f docker/initialization.yaml up com_skraukosaur_org1__initialize
# This command succeeds if and only if the specified volumes exist
docker volume inspect $(COM_EXAMPLE_ORG1_VOLUMES)
initialization-org2.skraukosaur.com:
# This command succeeds if and only if the specified volumes exist
docker volume inspect $(GENERATED_ARTIFACTS_VOLUME)
docker-compose -f docker/initialization.yaml up com_skraukosaur_org2__initialize
# This command succeeds if and only if the specified volumes exist
docker volume inspect $(COM_EXAMPLE_ORG2_VOLUMES)
initialization-www.skraukosaur.com:
# This command succeeds if and only if the specified volumes exist
docker volume inspect $(GENERATED_ARTIFACTS_VOLUME)
docker-compose -f docker/initialization.yaml up com_skraukosaur_www__initialize
# This command succeeds if and only if the specified volumes exist
docker volume inspect $(COM_EXAMPLE_WWW_VOLUMES)
# Copies necessary materials from generated_artifacts__volume to the volumes for various peers/orderers/etc.
# The -j1 is important here, otherwise docker creates multiple networks named fabricwebapp_default
# due to idiotic design in docker -- https://github.com/moby/moby/issues/18864
initialization:
$(MAKE) -j1 initialization-org0.skraukosaur.com initialization-org1.skraukosaur.com initialization-org2.skraukosaur.com initialization-www.skraukosaur.com
docker-compose -f docker/initialization.yaml down
# Brings down the services defined in docker/initialization.yaml
down-initialization:
docker-compose -f docker/initialization.yaml down
# Note that this only checks for the presence of certain volumes. It doesn't verify that the contents are correct.
inspect-initialized-volumes:
docker volume inspect $(COM_EXAMPLE_ORG0_VOLUMES) $(COM_EXAMPLE_ORG1_VOLUMES) $(COM_EXAMPLE_ORG2_VOLUMES) $(COM_EXAMPLE_WWW_VOLUMES) || echo "must successfully run `make initialization` in order to generate the containers needed for the various services."
# Bring up all services (and necessary volumes, networks, etc)
up: inspect-initialized-volumes
docker-compose up --abort-on-container-exit
# Bring up all services (and necessary volumes, networks, etc) in detached mode
up-detached: inspect-initialized-volumes
docker-compose up -d --abort-on-container-exit
# Follow the output of the logs
logs-follow:
docker-compose logs --follow --tail="all"
# Bring down all services (delete associated containers, networks, but not volumes)
down:
docker-compose down
# Bring down all services and volumes (delete associated containers, networks, AND volumes)
down-full:
docker-compose down -v
# Bring down the chaincode containers
down-chaincode:
docker rm dev-peer0.org0.skraukosaur.com-mycc-v0 \
dev-peer1.org0.skraukosaur.com-mycc-v0 \
dev-peer0.org1.skraukosaur.com-mycc-v0 \
dev-peer1.org1.skraukosaur.com-mycc-v0; \
true
down-chaincode-full: down-chaincode
docker rmi dev-peer0.org0.skraukosaur.com-mycc-v0 \
dev-peer1.org0.skraukosaur.com-mycc-v0 \
dev-peer0.org1.skraukosaur.com-mycc-v0 \
dev-peer1.org1.skraukosaur.com-mycc-v0; \
true
# Shows all non-source resources that this project created that currently still exist.
# The shell "or" with `true` is so we don't receive the error code that find/grep produces when there are no matches.
show-all-generated-resources:
docker network ls | grep $(COMPOSE_PROJECT_NAME)_ || true
@echo ""
docker ps -a | grep skraukosaur.com || true
@echo ""
docker volume ls | grep $(COMPOSE_PROJECT_NAME)_ || true
@echo ""
docker images | grep -E "$(COMPOSE_PROJECT_NAME)|skraukosaur.com" || true
# Build the chaincode using the hyperledger/fabric-ccenv image. This make target would be
# used during chaincode development to quickly find and correct compile errors.
build-chaincode:
docker-compose -f docker/build-chaincode.yaml up
docker-compose -f docker/build-chaincode.yaml down
# Delete the volume created by the build-chaincode target. This will not affect the production environment.
rm-build-chaincode-state:
docker-compose -f docker/build-chaincode.yaml down && docker volume rm fabricwebapp_build_chaincode_volume
# Delete the image in which the www.skraukosaur.com service runs.
rm-www-image:
docker rmi www.skraukosaur.com-env:v0.0
# Delete the "state" volumes -- tmp dir (which contains the webserver's key store) and HFC key/value store in
# home dir This can be done after `make down` to reset things to a "clean state", without needing to recompile go code or
# run `npm install` from scratch. The shell "or" with `true` is so this command never fails.
rm-state-volumes:
docker volume rm \
$(COM_EXAMPLE_ORG0_VOLUMES) \
$(COM_EXAMPLE_ORG1_VOLUMES) \
$(COM_EXAMPLE_ORG2_VOLUMES) \
$(COM_EXAMPLE_WWW_VOLUMES) \
$(COMPOSE_PROJECT_NAME)_com_skraukosaur_www__home_volume \
|| true
# Delete the node_modules dir, in case things get inexplicably screwy and you just feel like you have to nuke something.
# The shell "or" with `true` is so this command never fails.
rm-node-modules:
docker volume rm $(COMPOSE_PROJECT_NAME)_com_skraukosaur_www__node_modules_volume || true
# Delete generated_artifacts__volume. This contains all cryptographic material and some channel config material.
# BE REALLY CAREFUL ABOUT RUNNING THIS ONE, BECAUSE IT CONTAINS YOUR ROOT CA CERTS/KEYS.
rm-generated-artifacts: down-initialization
docker volume rm $(GENERATED_ARTIFACTS_VOLUME) || true
# Delete the containers and images created by the peers that run chaincode. This will be necessary if the chaincode
# is changed, because new docker images will have to be built with the new chaincode. If the chaincode has not changed,
# then this is not necessary. The semicolons are to run the commands sequentially without heeding the exit code. The
# command `true` is called last so that the make rule is always considered to have succeeded.
rm-chaincode-docker-resources:
docker rm dev-peer0.org0.skraukosaur.com-mycc-v0 \
dev-peer1.org0.skraukosaur.com-mycc-v0 \
dev-peer0.org1.skraukosaur.com-mycc-v0 \
dev-peer1.org1.skraukosaur.com-mycc-v0; \
docker images | egrep dev-peer.*skraukosaur.com | awk '{ print $$1 }' | xargs docker rmi -f; \
true
# Deletes all non-source resources that this project created that currently still exist. This should
# reset the project back to a "clean" state. NOTE: USE WITH CAUTION! This will also wipe out
# generated_artifacts__volume which, unless you backed them up somewhere, if you have configured
# generation of intermediate CAs, then it contains the only copies of your root CAs' keys.
rm-all-generated-resources:
$(MAKE) down down-generated-artifacts down-initialization
$(MAKE) rm-www-image rm-state-volumes rm-node-modules rm-generated-artifacts rm-chaincode-docker-resources
$(MAKE) rm-build-chaincode-state rm-chaincode-docker-resources
# Alias for rm-all-generated-resources. NOTE: USE WITH CAUTION!
clean: rm-all-generated-resources