Skip to content

Commit

Permalink
Fixes to README and easyinstall text (PiSCSI#787)
Browse files Browse the repository at this point in the history
* Update web README to point to the right dir and url

* Notify that an ssl cert is being created.

* Document the de-facto release number strategy of this project.

Co-authored-by: RaSCSI User <[email protected]>
  • Loading branch information
rdmark and RaSCSI User authored Aug 5, 2022
1 parent a523e1f commit 8cd50da
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 3 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ RaSCSI Reloaded is using the <a href="https://datasift.github.io/gitflow/Introdu
- The *master* branch should always reflect the contents of the last stable release
- The *develop* branch should contain the latest tested & approved updates. Pull requests should be used to merge changes into develop.
- The rest of the feature branches are for developing new features
- A tag will be created for each "release". The releases will be named <year>.<month> (for the first release of the month). Hot fixes, if necessary, will be released as <year>.<month>.<release number>. For example, the first release in January 2021 will be release "21.01". If a hot-fix is needed for this release, the first hotfix will be "21.01.1".
- A tag will be created for each "release". The releases will be named <year>.<month>.<release number> where the release number is incremented for each subsequent release tagged in the same calendar month. The first release of the month of January 2021 is called "21.01.01", the second one in the same month "21.01.02 and so on.

Typically, releases will only be planned every few months.

Expand Down
2 changes: 2 additions & 0 deletions easyinstall.sh
Original file line number Diff line number Diff line change
Expand Up @@ -1065,6 +1065,7 @@ function runChoice() {
echo "- Modify user groups and permissions"
echo "- Install binaries to /usr/local/bin"
echo "- Install manpages to /usr/local/man"
echo "- Create a self-signed certificate in /etc/ssl"
sudoCheck
configureTokenAuth
stopOldWebInterface
Expand Down Expand Up @@ -1213,6 +1214,7 @@ function runChoice() {
echo "- Modify and enable Apache2 and Nginx web service"
echo "- Create directories and change permissions"
echo "- Modify user groups and permissions"
echo "- Create a self-signed certificate in /etc/ssl"
sudoCheck
updateRaScsiGit
createCfgDir
Expand Down
4 changes: 2 additions & 2 deletions python/web/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ To create a new localization, it needs to be added to the LANGAUGES constant in
web/settings.py. To localize messages coming from the RaSCSI backend, update also code in
raspberrypi/localizer.cpp in the RaSCSI C++ code.

Once this is done, it is time to localize the Python code. The below steps are derived from the [Flask-Babel documentation](https://flask-babel.tkte.ch/#translating-applications).
Once this is done, it is time to localize the Python code. The below steps are derived from the [Flask-Babel documentation](https://python-babel.github.io/flask-babel/index.html#translating-applications).

First, generate the raw messages.pot file containing extracted strings.

Expand All @@ -68,7 +68,7 @@ $ pybabel extract -F babel.cfg -o messages.pot .
When adding a localization for a new language, initialize the directory structure. Replace 'xx' with the two character code for the language.

```
$ pybabel init -i messages.pot -d translations -l xx
$ pybabel init -i messages.pot -d src/translations -l xx
```

### Update an existing loclization
Expand Down

0 comments on commit 8cd50da

Please sign in to comment.