Compare commits

..

No commits in common. "main" and "0.1.0" have entirely different histories.
main ... 0.1.0

4 changed files with 6 additions and 23 deletions

View file

@ -1,7 +1,7 @@
on: on:
push: push:
tags: tags:
- '[0-9]+' - '[0-9]+\.[0-9]+\.[0-9]+'
jobs: jobs:
build: build:
@ -19,7 +19,7 @@ jobs:
uses: docker/build-push-action@v5 uses: docker/build-push-action@v5
with: with:
push: true push: true
tags: forgejo.neshweb.net/ci-docker-images/website-serve:${{ github.ref_name }}, forgejo.neshweb.net/ci-docker-images/website-serve:latest tags: forgejo.neshweb.net/firq/website-serve-docker:${{ github.ref_name }}, forgejo.neshweb.net/firq/website-serve-docker:latest
release: release:
needs: [build] needs: [build]
@ -27,7 +27,7 @@ jobs:
runs-on: docker runs-on: docker
steps: steps:
- name: Release New Version - name: Release New Version
uses: actions/forgejo-release@v2 uses: actions/forgejo-release@v1
with: with:
direction: upload direction: upload
url: https://forgejo.neshweb.net url: https://forgejo.neshweb.net

1
.gitignore vendored
View file

@ -1 +0,0 @@
.vscode/*

View file

@ -1,2 +1,2 @@
FROM node:22-alpine FROM node:lts
RUN npm install --global "@warren-bank/serve@130002.18.6" RUN npm install --global "@warren-bank/serve"

View file

@ -1,17 +1 @@
# website-serve Docker Image # Placeholder
This is a simple `node:22-alpine` based Docker Image with the `serve` fork of `@warren-bank` already preinstalled.
It can be used to serve static files like websites.
## Usage
To use the `serve` process, run the following `CMD` at the end of your own docker image:
```dockerfile
CMD [ "serve", DIRECTORY, "-p", PORT ]
```
Replace the values for `DIRECTORY` and `PORT` accordingly.
It is recommended to include a `serve.json` file inside the `DIRECTORY`. <br/>
The syntax for this can be found [here](https://github.com/warren-bank/node-serve/tree/master/lib/serve-handler)