mirror of
https://github.com/chuot/rdio-scanner.git
synced 2026-08-14 17:03:02 -06:00
Fix json comments in markdown
This commit is contained in:
parent
4973a6c282
commit
a0ae91226d
|
|
@ -161,7 +161,7 @@ At this point, you should be able to access to *Rdio Scanner* with a browser; ju
|
|||
|
||||
## Configuration
|
||||
|
||||
Please refer to the file [docs/config.md](./docs/config.md);
|
||||
Please refer to the file [docs/config.md](./docs/config.md).
|
||||
|
||||
## Post install updates
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Since **Rdio Scanner v4.0**, you have to configure your **Rdio Scanner** instance through the file located at `server/config.json`.
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"nodejs": {
|
||||
// Node.js specifics
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ It is possible to limit the access to your **Rdio Scanner** instance by adding a
|
|||
|
||||
The *rdioScanner.access* property can be as simple as a single *password* to an *array of objects*.
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"rdioScanner": {
|
||||
"access": [
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ The *rdioScanner.apiKeys* property can be as simple as a single *key* to an *arr
|
|||
|
||||
If you are already familiar with the *rdioScanner.access* property, it works prety much the same.
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"rdioScanner": {
|
||||
"apiKey": [
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
The *rdioScanner.dirWatch* property an *array* of *dirWatch objects* which describes folders to watch.
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"rdioScanner": {
|
||||
"dirWatch": [
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
Since **Rdio Scanner v4.0**, imported calls can be re-exported to other instances of **Rdio Scanner**. This means that you can build a mesh of **Rdio Scanner** with you and your friends so you could have your dream scanner!
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"rdioScanner": {
|
||||
"downstreams": [
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
## Definition
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"nodejs": {
|
||||
// [optional]
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
## Definitions
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"rdioScanner": {
|
||||
// [optional] Does downloading calls from the *search call panel* is allowed.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
You can define specific
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"sequelize": {
|
||||
// One of *sequelize* dialects
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
Since **Rdio Scanner v4.0**, the only way to configure radio systems is from the file *server/config.json*.
|
||||
|
||||
```json
|
||||
```js
|
||||
{
|
||||
"rdioScanner": {
|
||||
"systems": [
|
||||
|
|
|
|||
Loading…
Reference in a new issue