Mario1159/osic-stacks
1
1
Fork 1
Code Issues 11 Pull Requests Actions Packages Projects 2 Releases Wiki Activity

Compare commits

base: Mario1159:3df8e75927329d0f0b55acf426dc377607bc31f8
Branches Tags
Mario1159:main
Mario1159:support-ubuntu-variants
Mario1159:dev
Mario1159:modified-run-file
Mario1159:fix-gf-drc-repo
Mario1159:cicd
...
compare: Mario1159:a6d185b18d9d136851e69b13abbecdb5bd8fb1fa
Branches Tags
Mario1159:main
Mario1159:support-ubuntu-variants
Mario1159:dev
Mario1159:modified-run-file
Mario1159:fix-gf-drc-repo
Mario1159:cicd

2 Commits
3df8e75927 ... a6d185b18d

Author SHA1 Message Date
Mario1159
a6d185b18d Add screenshot to README 2023-09-21 05:53:26 -03:00
Mario1159
241bb09b1d Fix web build tag and build instructions 2023-09-21 05:50:01 -03:00
3 changed files with 23 additions and 6 deletions
Show Stats Expand all files Collapse all files

BIN
.gitea/screenshot.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 562 KiB

25
README.md
View File

@ -101,17 +101,34 @@ or you can also install packages from the AUR using paru.
## Custom Images
For creating an image with your own pre-installed set of packages for your team you can create your own docker image extending the stacks, just as the stacks extend the base image. For reference check the stacks dockerfiles.
For creating an image with your own pre-installed set of packages for your team you can create your own docker image extending the stacks, just as the stacks extend the base image. For reference check the stacks dockerfiles in the `stack` folder.
The following sections will get you to build and test any of the included stacks or your own custom image.
### Build
A singular stack image can be builded using docker in the following way from the repository root path.
Choose a singular stack image to build using docker for the desktop or the web client and replace the `<stack>` placeholder. Keep in mind that following steps are intended to be run from the repository root path.
#### Desktop build
Build the base image and then the stack image.
```sh
docker build --no-cache -t osicstacks-base-<desktop/web> -f base/<desktop/web>.Dockerfile .
docker build --no-cache --build-arg BASE_IMG=osicstacks-base-<desktop/web> --target <stack>-<desktop/web> -t <tag> -f stacks/<stack>.Dockerfile .
docker build --no-cache -t osicstacks-base-desktop -f base/desktop.Dockerfile .
docker build --no-cache --build-arg BASE_IMG=osicstacks-base-desktop --target <stack>-desktop -t <tag> -f stacks/<stack>.Dockerfile .
```
#### Web build
For the web client build the web client base image the required desktop image as well.
```sh
docker build --no-cache -t osicstacks-base-desktop -f base/desktop.Dockerfile .
docker build --no-cache -t osicstacks-base-web -f base/web.Dockerfile .
docker build --no-cache --build-arg BASE_IMG=osicstacks-base-web --target <stack>-web -t <tag> -f stacks/<stack>.Dockerfile .
```
### Local Run
Images can be tested and runned in the following way.

4
base/web.Dockerfile
View File

@ -1,6 +1,6 @@
# OSIC Stacks - osicstacks-base-webarch
# OSIC Stacks - osicstacks-base-web
# Base image for OSIC Stacks
FROM osicstacks-base-arch
FROM osicstacks-base-desktop
# Update packages
RUN sudo pacman -Syuq --noconfirm