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
This should print something like `Python 3.10.11+`.
22
+
23
+
### Building
24
+
You can build the specific versions by calling the respective make target:
25
+
```bash
26
+
make clean dist-bin/localstack
27
+
# or:
28
+
make clean dist-dir/localstack
29
+
# or both:
30
+
make clean all
31
+
```
32
+
You can find the binary assets in `dist-bin/` and `dist-dir`.
33
+
The single binary has a slower startup time than the binary distribution.
34
+
35
+
## Creating a Release
36
+
In order to create a release, just perform the following tasks:
37
+
- Create a commit which sets a new explicit version for `localstack` in the `requirements.txt`.
38
+
- For example: `localstack==2.1.0`
39
+
- Create a tag for the commit: `v<version>`.
40
+
- For example: `git tag v2.1.0`
41
+
- Push the tag (`git push origin v<version>`)
42
+
- This will trigger the following actions:
43
+
- The tag will trigger the ["Build / Release"](.github/workflows/build.yml) GitHub workflow.
44
+
- It will build the binaries for the different systems and create a GitHub release draft.
45
+
- Publish the GitHub release draft.
46
+
- This will trigger the ["Release Homebrew Tap"](.github/workflows/homebrew.yml) GitHub workflow.
47
+
- It will take the release artifacts and update the Homebrew formula in [localstack/homebrew-tap](https://github.com/localstack/homebrew-tap).
48
+
49
+
### Dev Releases
50
+
If a dev release is created, the tag name has to have the same name as the version of `localstack-core` being used (because this is the output of `localstack --version`).
51
+
Otherwise, the ["Release Homebrew Tap"](.github/workflows/homebrew.yml) GitHub workflow will not be able to find the artifacts.
Copy file name to clipboardExpand all lines: README.md
+10-45Lines changed: 10 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,52 +5,17 @@ This repository contains building instructions for binary builds of the LocalSta
5
5
It does not contain the actual source for the CLI, since the LocalStack CLI is basically just the Python package `localstack` (published on PyPi) with it's install dependencies (and without any extras).
6
6
This is why this repository just contains the build config and pipeline that packages the LocalStack CLI python package into a standalone binary using PyInstaller.
7
7
8
-
## Creating a Release
9
-
In order to create a release, just perform the following tasks:
10
-
- Create a commit which sets a new explicit version for `localstack` in the `requirements.txt`.
11
-
- For example: `localstack==2.1.0`
12
-
- Create a tag for the commit: `v<version>`.
13
-
- For example: `git tag v2.1.0`
14
-
- Push the tag (`git push origin v<version>`)
15
-
- This will trigger the following actions:
16
-
- The tag will trigger the ["Build / Release"](.github/workflows/build.yml) GitHub workflow.
17
-
- It will build the binaries for the different systems and create a GitHub release draft.
18
-
- Publish the GitHub release draft.
19
-
- This will trigger the ["Release Homebrew Tap"](.github/workflows/homebrew.yml) GitHub workflow.
20
-
- It will take the release artifacts and update the Homebrew formula in [localstack/homebrew-tap](https://github.com/localstack/homebrew-tap).
8
+
## Installation
9
+
Please make sure that you have a working [`docker` environment](https://docs.docker.com/get-docker/) on your machine before moving on.
21
10
22
-
### Dev Releases
23
-
If a dev release is created, the tag name has to have the same name as the version of `localstack-core` being used (because this is the output of `localstack --version`).
24
-
Otherwise, the ["Release Homebrew Tap"](.github/workflows/homebrew.yml) GitHub workflow will not be able to find the artifacts.
25
-
26
-
## Manual Build
27
-
### python3-dev
28
-
You need Python developer version libraries in your path to be able to build the distribution.
0 commit comments