Skip to content

Commit

Permalink
fix(docker): alpine dependencies
Browse files Browse the repository at this point in the history
  • Loading branch information
he3als committed Aug 25, 2024
1 parent 6f93711 commit 9683d74
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
3 changes: 2 additions & 1 deletion Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,8 @@
FROM --platform=$TARGETOS/$TARGETARCH alpine:latest
WORKDIR /app
COPY . ./
RUN curl -fsSL https://bun.sh/install | bash && exec bash \
RUN apk add --no-cache --update curl \
&& curl -fsSL https://bun.sh/install | sh && exec sh \
&& bun i --frozen-lockfile \
&& bun ship

Expand Down
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,8 +136,10 @@ Using [Vagrant](https://www.vagrantup.com) on Linux is incredibly simple. Verify
1. Clone the Pyrodactyl panel repository
2. Run `bun i` to install all required packages
3. Run `bun ship` to build Pyrodactyl. This will cache the results of the build and upload sourcemaps to Sentry. Subsequent builds without code changes will finish in milliseconds.

> [!IMPORTANT]
> In order for `vagrant up` to work, your files must be in the `/var/www/pterodactyl` directory unless manually changed in the `Vagrantfile`!
4. Run `vagrant up`. This will setup wings and the necessary services in order to run Pyrodactyl's databases, services, and app. This process could take up to 15 minutes.
5. Once you receive a message that says "Pyrodactyl is now up and running at localhost:3000", visit that URL in your browser and login with the default credentials provided in your console. **It's important that you use localhost to connect to Pyrodactyl! If you use 127.0.0.1, you will run into CORS issues and other issues that will not be fixed.**

Expand Down

0 comments on commit 9683d74

Please sign in to comment.