Skip to content

Commit

Permalink
Remove NodeJS from the README as well
Browse files Browse the repository at this point in the history
  • Loading branch information
thijzert committed Jun 8, 2024
1 parent 94db04f commit 0998927
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 8 deletions.
12 changes: 5 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,7 @@ Building
--------
Speeldoos has some compile-time dependencies:

* Go (≥ 1.15, though some older releases wil probably also work)
* NodeJS (≥ 14 - using a LTS release is highly recommended)
* Go (≥ 1.22, though some older releases wil probably also work)

To run, different parts of speeldoos will have different dependencies; install them as needed.
In no particular order, the runtime dependencies include:
Expand All @@ -21,8 +20,8 @@ In no particular order, the runtime dependencies include:

On my machines I installed most of these using one of the following commands:

* `sudo apt-get install flac lame id3v2 mplayer nodejs`
* `sudo pacman -S flac lame id3v2 mplayer nodejs-lts-fermium`
* `sudo apt-get install flac lame id3v2 mplayer`
* `sudo pacman -S flac lame id3v2 mplayer`

However, your mileage may vary.

Expand All @@ -44,12 +43,11 @@ Afterwards (you may need to restart your shell first), use the `sd` (or `speeldo
sd init --composer="Johann Sebastian Bach" 48

### Development build
If you intend to contribute to speeldoos, running a development build is advisable. This build process consists of two parts, which can be run in parallel:
If you intend to contribute to speeldoos, running a development build is advisable:

* `gulp watch`
* `go run build.go --quick --development --watch`

Both these commands will keep running and watch the source tree, recompiling if changes are detected. (the js and css, and the binary, respectively).
This command will keep running and watch the source tree, recompiling if changes are detected.

The build script also accepts a `--run` flag, which immediately runs the newly compiled binary whenever something changes.
To continuously run a web server, one could use:
Expand Down
2 changes: 1 addition & 1 deletion go.mod
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
module github.com/thijzert/speeldoos

go 1.22
go 1.22.3

require (
github.com/anacrolix/torrent v1.56.0
Expand Down

0 comments on commit 0998927

Please sign in to comment.