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
{{ message }}
This repository was archived by the owner on May 27, 2022. It is now read-only.
_Cakeshop_ is a set of tools and APIs for working with [Ethereum](https://ethereum.org/)-like ledgers, packaged as a Java web application archive (WAR) that gets you up and running in under 60 seconds.
14
-
15
-
Cakeshop will download the latest version of [quorum](https://github.com/jpmorganchase/quorum) and bootnode from [geth](https://github.com/ethereum/go-ethereum) (to use a different version, see [here](docs/configuration.md#custom-quorum-binaries)). The cakeshop package includes the [tessera](https://github.com/jpmorganchase/tessera) and [constellation](https://github.com/jpmorganchase/constellation) transaction managers, a [Solidity](https://solidity.readthedocs.org/en/latest/)
16
-
compiler, and all dependencies.
9
+
_Cakeshop_ is a set of tools and APIs for working with GoQuorum nodes, packaged as a Java web application archive (WAR) that gets you up and running in under 60 seconds.
17
10
18
-
It provides tools for managing a local blockchain node, setting up clusters,
19
-
exploring the state of the chain, and working with contracts.
11
+
It provides tools for attaching to GoQuorum nodes, exploring the state of the chain, and working with contracts.
20
12
21
13
## Download
22
14
23
-
Binary packages are available for macOS and Linux platforms on the [releases](https://github.com/jpmorganchase/cakeshop/releases) page.
15
+
Binary packages are available on the [Github releases page](https://github.com/ConsenSys/cakeshop/releases).
16
+
17
+
## Configuration
18
+
19
+
Cakeshop is a Spring Boot application, so you may place an `application.properties` file in the working directory to override any default configuration values. For more info, see the [configuration page](docs/configuration.md).
24
20
25
-
## Quickstart
21
+
## Running via GoQuorum Wizard
22
+
23
+
The easiest way to use Cakeshop is to generate a GoQuorum network with [GoQuorum Wizard](https://docs.goquorum.consensys.net/en/stable/HowTo/GetStarted/Wizard/GettingStarted/) and choose to deploy Cakeshop alongside the network.
24
+
25
+
## Running via Spring Boot
26
26
27
27
### Requirements
28
28
29
-
* Java 8+
30
-
* NodeJS (if the nodejs binary on your machine isn't called 'node', see [here](docs/configuration.md#nodejs-binary))
29
+
* Java 11+
30
+
* NodeJS (if the nodejs binary on your machine isn't called 'node', see [here](docs/configuration.md#cakeshop-internals))
31
31
32
-
### Running via Spring Boot
32
+
### Running
33
33
34
34
* Download WAR file
35
35
* Run `java -jar cakeshop.war`
36
36
* Navigate to [http://localhost:8080/](http://localhost:8080/)
37
37
38
38
39
-
###Running via Docker -- NEEDS UPDATE
39
+
## Running via Docker
40
40
41
-
Run via docker and access UI on [http://localhost:8080/](http://localhost:8080/)
41
+
Simple example of running via docker on port 8080:
42
42
43
43
```sh
44
44
docker run -p 8080:8080 quorumengineering/cakeshop
45
45
```
46
46
47
-
You'll probably want to mount a data volume:
47
+
Then access the UI at [http://localhost:8080/](http://localhost:8080/)
48
+
49
+
### Docker Customizations
50
+
You can add some extra flags to the run command to further customize cakeshop.
51
+
52
+
Here is an example where you mount `./data` as a data volume for the container to use:
48
53
49
54
```sh
50
55
mkdir data
51
56
docker run -p 8080:8080 -v "$PWD/data":/opt/cakeshop/data quorumengineering/cakeshop
52
57
```
53
58
54
-
Running under a specific environment
59
+
An example providing an initial nodes.json in the data directory and configuring it to be used:
55
60
56
61
```sh
62
+
# makes sure you have nodes.json at $PWD/data/nodes.json
57
63
docker run -p 8080:8080 -v "$PWD/data":/opt/cakeshop/data \
Note that DAG generation will take time and Cakeshop will not be available until it's complete. If you already have a DAG for epoch 0 in your `$HOME/.ethash` folder, then you can expose that to your container (or just cache it for later):
68
+
## Migrating from Cakeshop v0.11.0
63
69
64
-
```sh
65
-
docker run -p 8080:8080 -v "$PWD/data":/opt/cakeshop/data \
66
-
-v $HOME/.ethash:/opt/cakeshop/.ethash \
67
-
quorumengineering/cakeshop
68
-
```
70
+
The following big changes were made in v0.12.0:
71
+
1. Simplification of config file to better follow Spring Boot standards.
72
+
1. Moved Contract Registry from being stored in a combination of a smart contract and the database to being in the database only.
73
+
1. Elimination of cakeshop's managed node in favor of only attaching to existing nodes.
74
+
1. Simplified DB configuration by using Spring Data.
75
+
76
+
To ensure easy transition, Cakeshop will still look in the locations where v0.11.0 commonly stored the config file. But (1) allows you to now place your config in the folder where you run cakeshop, or specify a different location using standard spring boot flags, for easier customization.
77
+
78
+
Cakeshop had custom logging location logic in the config before this change, which was removed. You may now redirect logs yourself or use Spring's logging config settings.
79
+
80
+
For (2), if you had contracts deployed and stored in the old Contract Registry, you may leave the `contract.registry.addr` line in your config file. Cakeshop will look for that contract address when it connects to the network and add those contracts to the database.
81
+
82
+
For (3), most of the original config values were related to this feature, and can be safely removed. See the [default config file](../cakeshop-api/src/main/resources/config/application.properties) for all the values that are actually used.
83
+
84
+
(4) means that you will need to update the db-related config values to use spring data. So the old `cakeshop.database`, `cakeshop.hibernate`, and `cakeshop.jdbc` settings should change to use `spring.data`, `spring.jpa`, etc. See the [configuration](docs/configuration.md#database) doc for more info.
85
+
86
+
Note: Due to an bug that happens when you update from Hibernate 4 to 5, when auto-updating the database it will try to recreate some column constraints that don't need to be recreated. These will fail and print a stack trace in the logs because they already exist. There are no negative effects from this error, so the best thing to do is to run with `spring.jpa.hibernate.ddl-auto=update` once and then change `update` to `none` on subsequent runs to avoid error logs. In production, it is not recommended to use auto-update to migrate your database at all, but instead run migrations on the database yourself.
69
87
70
88
## Further Reading
71
89
72
-
Further documentation can be found on the [wiki](https://github.com/jpmorganchase/cakeshop/wiki/) and in the [docs](docs/) folder.
90
+
Further documentation can be found [here](https://docs.goquorum.consensys.net/en/stable/Concepts/Cakeshop/).
73
91
74
92
## See Also
75
93
76
94
*[JIF Dashboard](https://github.com/jpmorganchase/jif-dashboard) - The Cakeshop UI was built using the JIF Dashboard framework.
77
95
78
-
*[solc-cakeshop-cli](https://github.com/jpmorganchase/solc-cakeshop-cli) - The solidity compiler used behind the scenes is `solc-cakeshop-cli`, a thin wrapper atop the [solc](https://github.com/ethereum/solc-js) JS binding.
96
+
*[solc-cakeshop-cli](https://github.com/ConsenSys/solc-cakeshop-cli) - The solidity compiler used behind the scenes is `solc-cakeshop-cli`, a thin wrapper atop the [solc](https://github.com/ethereum/solc-js) JS binding.
79
97
80
98
## Contributing
81
99
82
100
Thank you for your interest in contributing to Cakeshop!
83
101
84
-
Cakeshop is built on open source and we invite you to contribute enhancements. Upon review you will be required to complete a Contributor License Agreement (CLA) before we are able to merge. If you have any questions about the contribution process, please feel free to send an email to [quorum_info@jpmorgan.com](mailto:quorum_info@jpmorgan.com).
102
+
Cakeshop is built on open source and we invite you to contribute enhancements. Upon review you will be required to complete a Contributor License Agreement (CLA) before we are able to merge. If you have any questions about the contribution process, please feel free to send an email to [info@goquorum.com](mailto:info@goquorum.com).
85
103
86
104
87
105
## Reporting Security Bugs
88
106
Security is part of our commitment to our users. At Quorum we have a close relationship with the security community, we understand the realm, and encourage security researchers to become part of our mission of building secure reliable software. This section explains how to submit security bugs, and what to expect in return.
89
107
90
-
All security bugs in [Quorum](https://github.com/jpmorganchase/quorum) and its ecosystem ([Tessera](https://github.com/jpmorganchase/tessera), [Constellation](https://github.com/jpmorganchase/constellation), [Cakeshop](https://github.com/jpmorganchase/cakeshop), ..etc) should be reported by email to [[email protected]](mailto:[email protected]). Please use the prefix **[security]** in your subject. This email is delivered to Quorum security team. Your email will be acknowledged, and you'll receive a more detailed response to your email as soon as possible indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement.
108
+
All security bugs in [GoQuorum](https://github.com/ConsenSys/quorum) and its ecosystem ([Tessera](https://github.com/ConsenSys/tessera), [Constellation](https://github.com/ConsenSys/constellation), [Cakeshop](https://github.com/ConsenSys/cakeshop), ..etc) should be reported by email to [[email protected]](mailto:[email protected]). Please use the prefix **[security]** in your subject. This email is delivered to the Quorum security team. Your email will be acknowledged, and you'll receive a more detailed response to your email as soon as possible indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement.
91
109
92
110
If you have not received a reply to your email or you have not heard from the security team please contact any team member through quorum slack security channel. **Please note that Quorum slack channels are public discussion forum**. When escalating to this medium, please do not disclose the details of the issue. Simply state that you're trying to reach a member of the security team.
93
111
@@ -109,9 +127,10 @@ The best way to receive security announcements is to subscribe to the Quorum-ann
109
127
110
128
Comments on This Policy
111
129
If you have any suggestions to improve this policy, please send an email to [email protected] for discussion.
0 commit comments