Skip to content

Commit 4736adb

Browse files
authored
Don't reference the old post.sh script in docs, use the bin/solr post command. (#2675)
the repetition of the word 'solr' looks awkward, but that is how it is!
1 parent 8154d22 commit 4736adb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

solr/solr-ref-guide/modules/deployment-guide/pages/solr-in-docker.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Next load some of the example data that is included in the container:
5353

5454
[source,bash]
5555
----
56-
docker exec -it my_solr post -c gettingstarted example/exampledocs/manufacturers.xml
56+
docker exec -it my_solr solr post -c gettingstarted example/exampledocs/manufacturers.xml
5757
----
5858

5959
In the UI, find the "Core selector" popup menu and select the "gettingstarted" core, then select the "Query" menu item.
@@ -245,15 +245,15 @@ docker run --name my_solr -p 8983:8983 solr solr-precreate books
245245
# get data
246246
mkdir mydata
247247
wget -O mydata/books.csv https://raw.githubusercontent.com/apache/solr/main/solr/example/exampledocs/books.csv
248-
docker run --rm -v "$PWD/mydata:/mydata" --network=host solr post -c books /mydata/books.csv
248+
docker run --rm -v "$PWD/mydata:/mydata" --network=host solr solr post -c books /mydata/books.csv
249249
----
250250

251251
The same works if you use the xref:docker-compose[example docker compose cluster], or you can just start your loading container in the same network:
252252

253253
[source,bash]
254254
----
255255
docker run -e SOLR_HOST=solr1 --network=mycluster_solr solr solr create -c books -p 8983
256-
docker run --rm -v "$PWD/mydata:/mydata" --network=mycluster_solr solr post -c books /mydata/books.csv --host solr1
256+
docker run --rm -v "$PWD/mydata:/mydata" --network=mycluster_solr solr solr post -c books /mydata/books.csv --host solr1
257257
----
258258

259259
Alternatively, you can make the data available on a volume at Solr start time, and then load it from `docker exec` or a custom start script.

0 commit comments

Comments
 (0)