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
- an electron template which includes `holochain-runner`, meant to reduce boilerplate around building desktop happs. All that's required are the UI and `.happ` files.
- all of the zome logic lives here. Uses `hdk_crud` to define all the Acorn entry types, like outcomes, edges, etc.
15
+
16
+
### Building the frontend
17
+
18
+
There are two build targets:
19
+
20
+
- desktop
21
+
- Weave app
22
+
4
23
### Run Locally and Develop on your Computer
5
24
6
25
_Prerequisites_
@@ -33,6 +52,7 @@ You can run the web process and the electron processes separately, instead of ru
33
52
-`yarn run electron`
34
53
35
54
#### Multi-User Testing
55
+
36
56
run the following commands in separate terminal instances (must have a running instance of acorn for the first user, either by running `yarn run dev` or the below commands without the `2`):
37
57
38
58
-`yarn run web(2,3,4)`
@@ -51,37 +71,38 @@ The packaged executables can be found in `frontend/electron/out`.
51
71
In order to get cross-platform builds, just tag your repository like `v1.0.0-alpha` and push the tag to Github. CI will automatically start running a build, under the "Release" action.
52
72
53
73
> Macos: You will need to have set the following environment variables as repository secrets:
74
+
>
54
75
> - APPLE_CERTIFICATE_BASE64
55
76
> - APPLE_CERTIFICATE_PASS
56
77
> - APPLE_DEV_IDENTITY
57
78
> - APPLE_ID_EMAIL
58
79
> - APPLE_ID_PASSWORD
59
80
> - APPLE_TEAM_ID
60
-
>
81
+
>
61
82
> The first two should be set as equivalents of `MACOS_CERTIFICATE` = `APPLE_CERTIFICATE_BASE64` and `MACOS_CERTIFICATE_PWD` = `APPLE_CERTIFICATE_PASS` as found in the following article, which also provides other instruction regarding this: https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions
62
83
63
-
64
84
### Versioning
65
85
66
-
Each version of the app will either change, or not change, the paths to the user data folders in use by the application.
86
+
Each version of the app will either change, or not change, the paths to the user data folders in use by the application.
67
87
68
88
The user data will be located under `acorn` in the platform specific appData folder, as specified by `appData` here: https://www.electronjs.org/docs/latest/api/app#appgetpathname
69
89
70
-
It is then in a specific sub-folder that relates to one of two types of data:
90
+
It is then in a specific sub-folder that relates to one of two types of data:
91
+
71
92
- source chain and DHT -> `databases-${INTEGRITY_VERSION_NUMBER}`
INTEGRITY_VERSION_NUMBER and KEYSTORE_VERSION_NUMBER are defined in `electron/src/holochain.ts` and can be modified as needed in order to jump to new versions of holochain, or a new app DNA.
75
96
76
-
You can tweak INTEGRITY_VERSION_NUMBER and KEYSTORE_VERSION_NUMBER independently.
97
+
You can tweak INTEGRITY_VERSION_NUMBER and KEYSTORE_VERSION_NUMBER independently.
77
98
78
99
INTEGRITY_VERSION_NUMBER should be incremented when a new DNA is in use, or when a new version of holochain which is not backwards compatible with prior versions is bumped to. In the case of new happ files being used, this occurs when the version number of the happ release in [./scripts/download-happs.sh](./scripts/download-happs.sh) changes. It will cause users to have to go through the migration process.
79
100
80
101
KEYSTORE_VERSION_NUMBER should be incremented if the version of lair-keystore changes, and has a new key format. Or if you otherwise want users to have to switch and generate new keys.
81
102
82
103
## Happ Code
83
104
84
-
The happ code has been separated into its own repository with its own release process. This has been done even though developing new features can sometimes involve the modification of that code, as well as the frontend and desktop wrapper code.
105
+
The happ code has been separated into its own repository with its own release process. This has been done even though developing new features can sometimes involve the modification of that code, as well as the frontend and desktop wrapper code.
85
106
86
107
The repo is here: https://github.com/lightningrodlabs/acorn-happ.
Built with [**Holochain**](https://www.holochain.org/), Acorn ([acorn.software](https://acorn.software)) is an open-source, peer-to-peer project management application. It is designed and built as a scrum-alternative, [Agile Development Pattern](https://en.wikipedia.org/wiki/Agile_software_development) for distributed software development teams.
3
+
Built with [**Holochain**](https://www.holochain.org/), Acorn ([acorn.software](https://acorn.software)) is an open-source, peer-to-peer project management application. It is designed and built as a scrum-alternative, [Agile Development Pattern](https://en.wikipedia.org/wiki/Agile_software_development) for distributed software development teams.
4
4
5
5
Acorn is currently in **Alpha** testing phase.
6
6
7
7
## Things you can do
8
8
9
-
-[**Download & install the latest Acorn release**](https://github.com/lightningrodlabs/acorn/releases/tag/v9.9.0).
9
+
-[**Download & install the latest Acorn release**](https://github.com/lightningrodlabs/acorn/releases/tag/v11.1.0).
10
10
11
11
- Check out the [Acorn Knowledge Base](https://docs.acorn.software) to learn more about Acorn, its methodology and features.
12
12
13
13
- Join the [Acorn alpha testing list](https://forms.gle/Ani18rJhDuAGv9LQ8) to get the latest news about Acorn.
14
14
15
15
- Are you a developer? [Read on](./DEVELOPERS.md).
16
16
17
-
18
17
0 commit comments