Lasa is a stateless proxy that generates a RSS or an Atom feed from a Standard.site publication.
lasa.anhgelus.world
rss
atom
atprotocol
standard-site
atproto
docs(info): deployment
+95
-2
+91
DEPLOYMENT.md
+91
DEPLOYMENT.md
···
1
+
# Deploying Lasa
2
+
3
+
Lasa can be deployed as a standalone binary or inside a container.
4
+
5
+
## Standalone binary
6
+
7
+
Clone the repo with:
8
+
```bash
9
+
git clone -b <tag> https://tangled.org/anhgelus.world/lasa .
10
+
```
11
+
where `<tag>` is the tag that you want to use.
12
+
13
+
We recommend you to install `just` (a command runner).
14
+
Of course, you can manually execute commands.
15
+
If you want to have the man pages installed, ensure that `scdoc` is here too.
16
+
17
+
Then, you can run
18
+
```bash
19
+
just install
20
+
```
21
+
to install the binaries and the man pages in `/usr/local/`.
22
+
If `/usr/local/man/man1` doesn't exist, it tries to create it.
23
+
You can create it before to avoid running the command as root.
24
+
25
+
If you don't have a supported Go version (e.g., the version installed is too old), you can use the environment variable
26
+
`GOTOOLCHAIN` to set it, e.g.,
27
+
```bash
28
+
GOTOOLCHAIN=go1.26.2 just install
29
+
```
30
+
31
+
Then, you can generate the config file with `lasad gen-config` at `/etc/lasad.toml`.
32
+
See `lasad(1)` for more information.
33
+
34
+
## Container
35
+
36
+
The official image is `atcr.io/anhgelus.world/lasa` and is based on Alpine Linux.
37
+
Sadly, to download it, you must be connected to `actr.io`.
38
+
39
+
You can also build the image by yourself by simply cloning the repo and running:
40
+
```bash
41
+
docker build -t lasa .
42
+
```
43
+
44
+
An example `compose.yml` is available in the repo.
45
+
The profile `prod` uses the official image.
46
+
47
+
The config file is stored in `/etc/lasad/config.toml`.
48
+
You can mount it with `-v ./config:/etc/lasad/`.
49
+
The default config file is already generated.
50
+
The exposed port is `8000`.
51
+
52
+
## Configuration
53
+
54
+
The config file only requires two informations: the port and the domain (for security headers).
55
+
```toml
56
+
domain = "lasa.example.org"
57
+
port = 8000
58
+
```
59
+
60
+
You can specify the legal notice with
61
+
```toml
62
+
legal_notice_url = "https://example.org/legal"
63
+
```
64
+
65
+
If you want to log 400 and 404 as warning, uncomment these lines:
66
+
```toml
67
+
# if you want to log HTTP 404 responses
68
+
log_not_found = true
69
+
# if you want to log HTTP 400 responses
70
+
log_bad_request = true
71
+
```
72
+
73
+
### Redis
74
+
75
+
Lasa supports Redis as a cache.
76
+
You can connect it by uncommenting and filling the required information in `cache` section of the config file, e.g.
77
+
```toml
78
+
[cache]
79
+
host = "localhost"
80
+
port = 6379
81
+
db = 0
82
+
duration = 60 # cache duration in minutes
83
+
```
84
+
85
+
If your Redis server requires auth, you can fill these information in `cache.auth` section, e.g.
86
+
```toml
87
+
[cache.auth]
88
+
username = "foo"
89
+
password = "bar"
90
+
client_name = "baz"
91
+
```
+2
README.md
+2
README.md