Skip to content

Commit

Permalink
Add application.properties file step to INSTALL.md
Browse files Browse the repository at this point in the history
This takes care of a documentation need that we've actually had since
commit de763e6: when `src/main/resources/application.properties`
was renamed to `application.properties.example`, that meant that the
live application's properties file wouldn't be created at install time
without some kind of extra step.  The result was that if you visited
`openhmis/api/v3/healthcheck`, you would see

    Your service is working with version

instead of, e.g. this:

    Your service is working with version 3.1.0

For now, the solution is just to add a manual step in INSTALL.md, but
some day we should automate this as part of the Maven deploy.  (Note
that this problem is separate from the problem of keeping the version
number itself up-to-date, which is discussed in issue #40.)
  • Loading branch information
kfogel committed Jan 31, 2016
1 parent 3104dec commit 96ac954
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions INSTALL.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,14 @@ _Note: you do not need to install anything for this to work. Flyway is automati
$> vi src/main/resources/hibernate.cfg.xml
```

5. Create the `application.properties` file.

```shell
$> cp src/main/resources/application.properties.example src/main/resources/application.properties
```

You shouldn't have to edit anything in that file. (But some day that might change -- see https://github.com/PCNI/OpenHMIS/issues/38 for more information.)

Import sample data (or real data, if you have some):
---------------------------------------------------

Expand Down

0 comments on commit 96ac954

Please sign in to comment.