Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated command line in RELEASING.md #70

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Updated command line in RELEASING.md #70

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c17615
Updated command line in RELEASING.md
blurks Nov 23, 2021
bf5ac8a
added note on updating DOIs
blurks Nov 23, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 13 additions & 6 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,18 @@ The data served by [WALS Online](https://wals.info) is curated in the GitHub
repository [cldf-datasets/wals](https://github.com/cldf-datasets/wals).
Thus, a release of WALS Online is always bound to a release of this repository.

So, assuming `cldf-datasets/wals` has been released on Zenodo, with DOI `<DOI>`
assigned to it, we
The DOIs of different versions of the cldf dataset are hard-coded in
the html of the app. So you have to update these manually when you
publish a new release of the data. Check the output of `grep -Rin "doi" ./wals3/`
to find files that contain DOIs.

To create the database With the cldf-datasets/wals repository located
in `./wals-data`, run

```shell script
clld initdb --cldf ./wals-data/cldf/StructureDataset-metadata.json development.ini
```

- run tests with `pytest .`

- recreate the web application's database running
```shell script
wals-app initdb --doi <DOI> --repos ../../cldf/wals
```
- deploy the app running `fab deploy:production` via `appconfig`.