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
Update your master branch after the release notes PR ([example](https://github.com/cryptoadvance/specter-desktop/commit/65ff6959d7fd85cba745e4d454b30031839f857f/)) has been merged and then run:
44
+
33
45
```bash
34
46
git tag v1.13.1 && git push upstream v1.13.1
35
47
```
48
+
36
49
## GitLab - releasing stage
37
-
Creating a tag triggers the release process of the GitLab runners.
38
-
There exists a mirror of the GitHub repo on GitLab, but only when a tag is created on GitHub will the release part of the runners execute. You can check the status here:
50
+
51
+
Creating a tag triggers the release process of the GitLab runners.
52
+
There exists a mirror of the GitHub repo on GitLab, but only when a tag is created on GitHub will the release part of the runners execute. You can check the status here:
@@ -50,14 +64,17 @@ The first relevant stage is "releasing". Here, the Windows, Linux and pip releas
50
64
- specter_desktop-v1.13.1-x86_64-linux-gnu.tar.gz
51
65
52
66
The three jobs in more detail:
67
+
53
68
- release_binary_windows: is creating a binary for specterd and for Windows (Windows runner)
54
69
- release_electron_linux_windows: Creates a specterd for Linux, an AppImage for Linux and an executable for Windows (Linux runner).
55
-
- release_pip: Is releasing a pypi package on [pypi](https://pypi.org/project/cryptoadvance.specter/) and creates a tarball of the pip package for the GitHub release page (Linux runner).
70
+
- release_pip: Is releasing a pypi package on [pypi](https://pypi.org/project/cryptoadvance.specter/) and creates a tarball of the pip package for the GitHub release page (Linux runner).
56
71
57
72
For details look at `.gitlab-ci.yml`
58
73
59
74
## MacOS
75
+
60
76
Ideally, directly after the tag is created, start with the MacOS release. This has to be done manually, for now. There is a script for this:
@@ -70,54 +87,37 @@ This script also runs `github.py upload `, so two more binares and the hash and
70
87
- SHA256SUMS-macos.asc
71
88
72
89
## GitLab - post releasing
73
-
Back to GitLab, the final stage is "post releasing".
90
+
91
+
Back to GitLab, the final stage is "post releasing".
74
92
75
93
In this stage, the invididual SHA256-hashes and signatures are combined into two final files:
94
+
76
95
- SHA256SUMS
77
96
- SHA256SUMS.asc
78
97
79
98
Everything, apart from the MacOS files, are pulled from the GitLab environment, the MacOS files from GitHub.
80
99
Don't forget to delete the two MacOS files (`SHA256SUMS-macos` and `SHA256SUMS-macos.asc`) on the GitHub release page in the end.
81
100
82
101
## Trouble shooting
102
+
83
103
If the MacOS signatures are missing, it can happen that the following Exception will be raised:
104
+
84
105
```bash
85
106
File "/builds/cryptoadvance/specter-desktop/utils/github.py", line 295, in download_artifact
86
107
raise Exception(
87
108
Exception: Status-cod04 for url ... )
88
109
```
110
+
89
111
In any case, if the macOS binaries arrive on GitHub too late, you have to manually delete the already created `SHA256SUMS` and `SHA256SUMS.asc`, otherwise the upload to GitHub will fail if you rerun the release signatures job on GitLab - for details see ([this PR](https://github.com/cryptoadvance/specter-desktop/pull/689)). The green arrow in the screenshot is where you rerun the release signatures job on GitLab:
We are running a script here to create a markdown file that can be used for copy and paste. The script uses the latest release on GitHub to create links to the artifacts in the release, so it only makes sense to run it once the previous step has been completed.
95
-
- Checkout this repo: `[email protected]:cryptoadvance/corp-notes.git`
96
-
-`cd download-page`
97
-
- Run `./build.sh`
98
-
99
-
The result `gh_page.md` can be found in the build directory.
100
-
Edit the release on GitHub and paste the md-file there along with the release notes from `release-notes.md`.
101
-
102
-
## Website
103
-
The above script also produces html files for the website (in the same directory). The second item needs to have the release notes on GitHub, otherwise the content for the details button is missing. So, you need to re-run `./build.sh` after the release notes on GitHub are done.
- Hover over "Specter Desktop - Elementor" and choose `Edit with Elementor`
111
-
- Click somewhere on area 1 (see screenshot), then somewhere on area 2, select all, delete, and paste: `download-page_current.html`
112
-
113
-
\
114
-
- Then click `update`
115
-
Note: If you see jinja tags, you probably pasted some templates.
116
-
117
-
Do the same for the "Specter Releases" part, just, in this case, replace with:\
118
-
`download-page_releases.html`
119
-
120
-
\
115
+
## GitHub release page and download page
121
116
122
-
You can then just exit the editing with Elementor.
117
+
This is handled by the script `./utils/generate_downloadpage.sh`. As a prerequisite, you need to clone the `specter-static` repo which contains the specter website. Clone it on the same level than specter-desktop.
118
+
Running that script will:
123
119
120
+
- install the prerequisites (basically markdown, see pyproject.toml)
121
+
- generate the GH-page and the download-page based on the `utils/templates`.
122
+
- Asks whether it should replace/update/initialize the Github Release page for the latest version
123
+
- copies over the new download-pages and asks whether it should commit/push those
Copy file name to clipboardExpand all lines: docs/self-signed-certificates.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,23 @@
1
1
# SSL Certificate
2
+
2
3
## Why a certificate is important
3
4
4
5
Browsers require secure communication with the server to use camera API. Without it we can't use QR code scanning.
5
6
6
-
If you are running a VPS it's easy - you just [issue a new certificate](./reverse-proxy#adding-https) with Letsencrypt.
7
+
If you are running a VPS it's easy - you just [issue a new certificate](./reverse-proxy.md#adding-https) with Letsencrypt.
7
8
8
9
If you are only using the node at home and want to use it from your local network and via camera, you need to run it via SSL.
9
10
10
11
## Easy solution
11
12
12
13
The easiest solution is to simply add `--ssl` to the serve-command and the certificate will get created automatically in the specter-home-folder.
14
+
13
15
```
14
16
python3 -m cryptoadance.specter server --ssl
15
17
```
16
18
17
19
## Manual creation
18
20
19
-
20
21
A second way, which provides more customization, is to run the [`gen-certificate.sh`](gen-certificate.sh) script in this folder with your node's IP address as an argument:
21
22
22
23
```sh
@@ -33,7 +34,7 @@ Provide these files to Specter as arguments:
33
34
python -m cryptoadvance.specter server --cert=./cert.pem --key=./key.pem
34
35
```
35
36
36
-
*Note:* Adding `--tor=your-tor-password` will create a tor hidden service with https.
37
+
_Note:_ Adding `--tor=your-tor-password` will create a tor hidden service with https.
37
38
38
39
### Specter with Nginx
39
40
@@ -53,7 +54,7 @@ The config should look like this:
0 commit comments