badhouseplants/badhouseplants-net
badhouseplants
/
badhouseplants-net
5
1
Fork 0
Code Issues 7 Pull Requests 1 Packages Projects 2 Releases Activity
This is the source code for my blog that can be found here: https://badhouseplants.net
31 Commits 8 Branches 0 Tags 2.1 GiB
Perl 62.7%
HTML 18.7%
Smarty 16.5%
Dockerfile 1.3%
Makefile 0.8%
Go to file
Nikolai Rodionov 7927ce482c
continuous-integration/drone/push Build is passing Details
fix: format minio path 		2023-03-17 16:14:20 +01:00
archetypes Init Commit 2023-02-17 15:19:49 +01:00
chart Init branch 2023-03-17 15:47:43 +01:00
configs Build static and use nginx instead of the full hugo server (#8) 2023-02-17 14:48:16 +00:00
content Init branch 2023-03-17 15:47:43 +01:00
kube Init branch 2023-03-17 15:47:43 +01:00
layouts feat: use the built-in plugin feature 2023-03-02 15:37:53 +01:00
scripts fix: format minio path 2023-03-17 16:14:20 +01:00
static Init branch 2023-03-17 15:47:43 +01:00
themes Remove an obsolete submodule (#17) 2023-02-22 21:07:48 +00:00
.dockerignore Init branch 2023-03-17 15:47:43 +01:00
.drone.yml build: Use a separate pipeline for helm chart 2023-03-17 15:59:49 +01:00
.gitattributes Init branch 2023-03-17 15:47:43 +01:00
.gitignore Init branch 2023-03-17 15:47:43 +01:00
.gitmodules cleanup: remove extra files and submodule (#14) 2023-02-21 10:13:31 +00:00
.hugo_build.lock Init Commit 2023-02-17 15:19:49 +01:00
Dockerfile Init branch 2023-03-17 15:47:43 +01:00
Makefile Init branch 2023-03-17 15:47:43 +01:00
README.md Init Commit 2023-02-17 15:19:49 +01:00
config.yaml feat: use the built-in plugin feature 2023-03-02 15:37:53 +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