badhouseplants/badhouseplants-net-old
Archived
4
0
Fork 0
Code Issues 7 Pull Requests 2 Actions Packages Projects Releases Activity
This is the source code for my blog that can be found here:
This repository has been archived on 2024-10-01. You can view files and clone it, but cannot push or open issues or pull requests.
76 Commits 10 Branches 0 Tags 467 MiB
Perl 62.7%
HTML 18.7%
Smarty 16.5%
Dockerfile 1.3%
Makefile 0.8%
15d60b07fd
Go to file
Nikolai Rodionov 15d60b07fd
refactor: Renambe Dockerfile to Containerfile 
I'm not user docker for building, hence it makes more sense to have a
`Containerfile`
2023-05-10 16:53:17 +02:00
chart build: Refactor the Minio sync logic and separate the helm chart release 2023-03-24 12:51:56 +01:00
configs Build static and use nginx instead of the full hugo server (#8) 2023-02-17 14:48:16 +00:00
kube Use a custom image for building and more scripts 2023-04-25 10:05:52 +02:00
scripts Try doing a wee cleanup 2023-05-08 14:48:02 +02:00
src feat: Start using a better theme 2023-05-10 13:03:19 +02:00
.dockerignore Try doing a wee cleanup 2023-05-08 14:48:02 +02:00
.drone.yml Try doing a wee cleanup 2023-05-08 14:48:02 +02:00
.gitattributes Try doing a wee cleanup 2023-05-08 14:48:02 +02:00
.gitignore Try doing a wee cleanup 2023-05-08 14:48:02 +02:00
.gitmodules feat: Start using a better theme 2023-05-10 13:03:19 +02:00
.hugo_build.lock Init Commit 2023-02-17 15:19:49 +01:00
.spelling Update spellchecker config 2023-05-08 14:51:30 +02:00
Containerfile refactor: Renambe Dockerfile to Containerfile 2023-05-10 16:53:17 +02:00
Makefile content: Update the CV 2023-03-29 21:54:39 +02:00
README.md Init Commit 2023-02-17 15:19:49 +01:00

README.md

Badhouseplants NET

Static content

Storing static content in the repo is painful, because there are massive. That's why for storing them I'm using a S3 bucket that is publicly available for downstream operations