Skip to content

Commit 205b098

Browse files
docs: Add load instructions
1 parent e69ee1a commit 205b098

File tree

1 file changed

+28
-1
lines changed

1 file changed

+28
-1
lines changed

sphinx/aws/web-portal-docker.md

Lines changed: 28 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ The server structure should look something like this:
146146

147147
## Adding an Instance
148148

149-
Assuming the export made from Specify 6 is named `DataExport.zip` and it is in the current directory:
149+
Assuming the export made from Specify 6 is named `DataExport.zip` and it is in the current directory, you can use `scp` or `sftp` to copy the appropriate files to the web portal server. These were the steps I ran on my local machine to add the appropriate configuration files to the `webportal` SSH host:
150150

151151
```bash
152152
scp ./DataExport.zip webportal:/home/ubuntu/specify_exports/sbmnhiz.zip
@@ -161,3 +161,30 @@ This creates the necessary templates for customizing the fields included in the
161161

162162
## Loading New Data
163163

164+
Once your export has been added to `specify_exports` and all relevant custom settings have been added, you need to restart the `webportal` service for the changes to be applied.
165+
166+
1. Stop the `webportal` service in the `~/webportal-installer` directory
167+
168+
```bash
169+
docker compose down
170+
```
171+
172+
2. Start the `webportal` service again:
173+
174+
```bash
175+
docker compose up -d
176+
```
177+
178+
3. Once the solr service has started successfully (takes around 180 seconds after container starts), you can enter the container:
179+
180+
```bash
181+
docker exec -it webportal /bin/bash
182+
```
183+
184+
4. Once there, run `make load-data` to load data for all Web Portal instances:
185+
186+
```bash
187+
make load-data
188+
```
189+
190+
5. Once the data has loaded, exit the container, then verify the data is present on all

0 commit comments

Comments
 (0)