This repository has no description
update readme
author
Ewan Croft
date
(Feb 22, 2025, 9:43 PM UTC)
commit
c8bec3b6
c8bec3b644e6a0a93751a6bf2b856227a1c2efcd
parent
c137ba62
c137ba6244dad162e4c080296e3cccd585237ae7
+21
-4
+21
-4
README.md
+21
-4
README.md
···
10
10
11
11
Before running the script, ensure you have the following:
12
12
13
-
- Python 3.6 or later installed.
13
+
- Python 3.6 or later installed. If using Ubuntu, run `sudo apt update && sudo apt install -y python3 python3-pip python3-dev`
14
14
- The required Python packages (automatically installed if missing):
15
15
- `python-dotenv`
16
16
- `atproto`
···
27
27
cd bluesky-avatar-updater
28
28
```
29
29
30
-
2. **Create a virtual environment and install dependencies:**
30
+
2. **Ensure the required package is installed (if necessary):**
31
+
32
+
Before creating the virtual environment, make sure that the `python3-venv` package is installed (this is necessary on Debian/Ubuntu systems to create virtual environments).
33
+
34
+
```bash
35
+
sudo apt install python3.10-venv # Adjust the version if necessary (e.g., python3.9-venv)
36
+
```
37
+
38
+
3. **Create a virtual environment and install dependencies:**
39
+
40
+
Now, create a new virtual environment and activate it. This isolates the package dependencies for your project.
31
41
32
42
```bash
33
43
python3 -m venv .venv
34
44
source .venv/bin/activate # On Windows use: .venv\Scripts\activate
45
+
```
46
+
47
+
4. **Install dependencies within the virtual environment:**
48
+
49
+
With the virtual environment activated, install the required packages listed in the `requirements.txt` file:
50
+
51
+
```bash
35
52
pip install -r requirements.txt
36
53
```
37
54
38
-
3. **Configure environment variables:**
55
+
5. **Configure environment variables:**
39
56
- Place your `.env` file in the `../assets` directory relative to the script.
40
57
- The `.env` file should contain the following entries:
41
58
···
46
63
DID=your_did
47
64
```
48
65
49
-
4. **Prepare the JSON file:**
66
+
6. **Prepare the JSON file:**
50
67
- Ensure that a `cids.json` file is located in the `../assets` directory. This file should map each hour (in two-digit format) to a corresponding blob CID. Example:
51
68
52
69
```json