diff --git a/images/docker-hishtory-server/index.html b/images/docker-hishtory-server/index.html index 3c03889f6d..24908da49b 100644 --- a/images/docker-hishtory-server/index.html +++ b/images/docker-hishtory-server/index.html @@ -1,4 +1,4 @@ - hishtory-server - LinuxServer.io
Skip to content

linuxserver/hishtory-server

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build

hiSHtory is a better shell history. It stores your shell history in context (what directory you ran the command in, whether it succeeded or failed, how long it took, etc). This is all stored locally and end-to-end encrypted for syncing to to all your other computers.

hishtory-server

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/hishtory-server:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Available Tag
x86-64 ✅ amd64-<version tag>
arm64 ✅ arm64v8-<version tag>
armhf ❌

Application Setup

After you have installed hishtory on your machine, add export HISHTORY_SERVER=http://1.2.3.4:8080 (with your server details) to your shellrc. Then run hishtory init (or hishtory init ${SECRET_KEY}) to initialise hishtory against your local server.

See the project readme for more details.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
+ hishtory-server - LinuxServer.io      
 
 
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
   
linuxserver/hishtory-server
 
Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build
 
hiSHtory is a better shell history. It stores your shell history in context (what directory you ran the command in, whether it succeeded or failed, how long it took, etc). This is all stored locally and end-to-end encrypted for syncing to to all your other computers.
 
hishtory-server
 
Supported Architectures
 
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
 
Simply pulling lscr.io/linuxserver/hishtory-server:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
 
The architectures supported by this image are:
 
  
 Architecture Available Tag 
   
 x86-64 ✅ amd64-<version tag> 
 
 arm64 ✅ arm64v8-<version tag> 
 
 armhf ❌  
  
 
Application Setup
 
After you have installed hishtory on your machine, add export HISHTORY_SERVER=http://1.2.3.4:8080 (with your server details) to your shellrc. Then run hishtory init (or hishtory init ${SECRET_KEY}) to initialise hishtory against your local server.
 
See the project readme for more details.
 
Usage
 
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
  
---
 services:
   hishtory-server:
     image: lscr.io/linuxserver/hishtory-server:latest
@@ -45,4 +45,4 @@
   --pull \
   -t lscr.io/linuxserver/hishtory-server:latest .
 
 
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
 
docker run --rm --privileged multiarch/qemu-user-static:register --reset
-
 
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
 
Versions
 
     
  • 31.01.24: - Rebase to Alpine 3.19.
    •  
  • 19.05.23: - Initial Release.
    •  
  
 
  
  
  
 
 
 
      
\ No newline at end of file
+

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 31.01.24: - Rebase to Alpine 3.19.
  • 19.05.23: - Initial Release.
\ No newline at end of file diff --git a/images/docker-znc/index.html b/images/docker-znc/index.html index 97289f242f..e0c89d3f5e 100644 --- a/images/docker-znc/index.html +++ b/images/docker-znc/index.html @@ -1,4 +1,4 @@ - znc - LinuxServer.io
Skip to content

linuxserver/znc

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

Znc is an IRC network bouncer or BNC. It can detach the client from the actual IRC server, and also from selected channels. Multiple clients from different locations can connect to a single ZNC account simultaneously and therefore appear under the same nickname on IRC.

znc

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/znc:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Available Tag
x86-64 ✅ amd64-<version tag>
arm64 ✅ arm64v8-<version tag>
armhf ❌

Application Setup

To log in to the application, browse to http://<hostip>:6501.

  • Default User: admin
  • Default Password: admin change password ASAP.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
+ znc - LinuxServer.io      
 
 
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
   
linuxserver/znc
 
Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI
 
Znc is an IRC network bouncer or BNC. It can detach the client from the actual IRC server, and also from selected channels. Multiple clients from different locations can connect to a single ZNC account simultaneously and therefore appear under the same nickname on IRC.
 
znc
 
Supported Architectures
 
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
 
Simply pulling lscr.io/linuxserver/znc:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
 
The architectures supported by this image are:
 
  
 Architecture Available Tag 
   
 x86-64 ✅ amd64-<version tag> 
 
 arm64 ✅ arm64v8-<version tag> 
 
 armhf ❌  
  
 
Application Setup
 
To log in to the application, browse to http://<hostip>:6501.
 
     
  • Default User: admin
    •  
  • Default Password: admin change password ASAP.
    •  
 
Usage
 
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
  
---
 services:
   znc:
     image: lscr.io/linuxserver/znc:latest
@@ -44,4 +44,4 @@
   --pull \
   -t lscr.io/linuxserver/znc:latest .
 
 
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
 
docker run --rm --privileged multiarch/qemu-user-static:register --reset
-
 
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
 
Versions
 
     
  • 26.03.24: - Switch back to multi-threaded builds and ignore -beta and -alpha tags as well as -rc.
    •  
  • 22.02.24: - Update build system for v1.9.0 (use cmake).
    •  
  • 23.12.23: - Rebase to Alpine 3.19.
    •  
  • 12.07.23: - Rebasing to Alpine 3.18.
    •  
  • 07.07.23: - Deprecate armhf. As announced here
    •  
  • 13.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
    •  
  • 19.01.22: - Rebasing to alpine 3.15.
    •  
  • 01.06.20: - Rebasing to alpine 3.12.
    •  
  • 19.12.19: - Rebasing to alpine 3.11.
    •  
  • 02.11.19: - Add znc-palaver module.
    •  
  • 28.06.19: - Rebasing to alpine 3.10.
    •  
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
    •  
  • 22.02.19: - Rebasing to alpine 3.9.
    •  
  • 31.01.19: - Add pipeline logic and multi arch.
    •  
  • 30.01.19: - Add push and clientbuffer modules.
    •  
  • 17.08.18: - Rebase to alpine 3.8, use buildstage.
    •  
  • 03.01.18: - Deprecate cpu_core routine lack of scaling.
    •  
  • 07.12.17: - Rebase alpine linux 3.7.
    •  
  • 25.10.17: - Remove debug switch from run command.
    •  
  • 26.05.17: - Rebase alpine linux 3.6.
    •  
  • 06.02.17: - Rebase alpine linux 3.5.
    •  
  • 19.01.17: - Add playback module.
    •  
  • 07.01.17: - Add ca-certificates package, resolve sasl issues.
    •  
  • 07.12.16: - Use scanelf to determine runtime dependencies. Fix error with continuation.
    •  
  • 14.10.16: - Add version layer information.
    •  
  • 30.09.16: - Fix umask.
    •  
  • 11.09.16: - Add layer badges to README.
    •  
  • 28.08.16: - Add badges to README.
    •  
  • 20.08.16: - Rebase to alpine linux, move to main repository.
    •  
  • 11.12.15: - Initial Release.
    •  
  
 
  
  
  
 
 
 
      
\ No newline at end of file
+

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 26.03.24: - Switch back to multi-threaded builds and ignore -beta and -alpha tags as well as -rc.
  • 22.02.24: - Update build system for v1.9.0 (use cmake).
  • 23.12.23: - Rebase to Alpine 3.19.
  • 12.07.23: - Rebasing to Alpine 3.18.
  • 07.07.23: - Deprecate armhf. As announced here
  • 13.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
  • 19.01.22: - Rebasing to alpine 3.15.
  • 01.06.20: - Rebasing to alpine 3.12.
  • 19.12.19: - Rebasing to alpine 3.11.
  • 02.11.19: - Add znc-palaver module.
  • 28.06.19: - Rebasing to alpine 3.10.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 22.02.19: - Rebasing to alpine 3.9.
  • 31.01.19: - Add pipeline logic and multi arch.
  • 30.01.19: - Add push and clientbuffer modules.
  • 17.08.18: - Rebase to alpine 3.8, use buildstage.
  • 03.01.18: - Deprecate cpu_core routine lack of scaling.
  • 07.12.17: - Rebase alpine linux 3.7.
  • 25.10.17: - Remove debug switch from run command.
  • 26.05.17: - Rebase alpine linux 3.6.
  • 06.02.17: - Rebase alpine linux 3.5.
  • 19.01.17: - Add playback module.
  • 07.01.17: - Add ca-certificates package, resolve sasl issues.
  • 07.12.16: - Use scanelf to determine runtime dependencies. Fix error with continuation.
  • 14.10.16: - Add version layer information.
  • 30.09.16: - Fix umask.
  • 11.09.16: - Add layer badges to README.
  • 28.08.16: - Add badges to README.
  • 20.08.16: - Rebase to alpine linux, move to main repository.
  • 11.12.15: - Initial Release.
\ No newline at end of file