Skip to content

Commit

Permalink
docs: services setup --force is quicker than destroy then setup
Browse files Browse the repository at this point in the history
  • Loading branch information
phette23 committed Aug 8, 2024
1 parent 1712656 commit cd8937a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 3 deletions.
3 changes: 1 addition & 2 deletions notes/code_samples/rebuild
Original file line number Diff line number Diff line change
@@ -1,8 +1,7 @@
#!/usr/bin/env fish
# TODO flag to recreate the venv too?
echo "Rebuilding the Invenio application, this will DESTROY ALL DATA in the database and search engine and load fresh fixtures from the all_data directory"
invenio-cli services destroy
invenio-cli services setup
invenio-cli services setup --force --no-demo-data
echo "The 'Failed to setup services.' warning because 'distutils.errors.DistutilsOptionError: no message catalogs found' error does not seem to affect the app"
read -P 'would you like to run the application in the foreground? (y/N)' answer
if [ $answer = 'y']
Expand Down
2 changes: 1 addition & 1 deletion notes/run.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ If you're running the app locally, the main URLs (for website and REST API) are

## Local Rebuild

To reset the local instance, run `invenio-cli destroy`, then redo the setup steps in [the readme](../readme.md). If we do not destroy the services, the next time we set up we get an error.
To reset the local instance, run `invenio-cli services setup --force --no-demo-data` when performing the steps in [the readme](../readme.md). The `--force` flag destroys the services; if we did not, we would get an error the next time we setup.

## CLI Usage

Expand Down

0 comments on commit cd8937a

Please sign in to comment.