still need to migrate off of koken ;_;
-
still need to migrate off of koken ;_;
-
still need to migrate off of koken ;_;
idk how to really approach my concert photo portfolio but i think importing shit into Hugo's content/ directory structure is too much of a pain, and managing the assets directly in Hugo is also a pain
i still don't know enough about other cms offerings but a cms probably makes more sense than a static directory structure? i just want the final output to be more or less a static website, so what i really need to figure out is where the images will live or be served from
-
idk how to really approach my concert photo portfolio but i think importing shit into Hugo's content/ directory structure is too much of a pain, and managing the assets directly in Hugo is also a pain
i still don't know enough about other cms offerings but a cms probably makes more sense than a static directory structure? i just want the final output to be more or less a static website, so what i really need to figure out is where the images will live or be served from
@trwnh yeah I found Hugo a pain. Do you know astro?
-
@trwnh yeah I found Hugo a pain. Do you know astro?
@mattesilver no, that's not it -- Hugo is fine, i like Hugo; the painful part is dealing with a bunch of images in the same project. i don't want my git repo to be multiple GBs, so i ostensibly want my actual assets/content separate from the Hugo project.
-
idk how to really approach my concert photo portfolio but i think importing shit into Hugo's content/ directory structure is too much of a pain, and managing the assets directly in Hugo is also a pain
i still don't know enough about other cms offerings but a cms probably makes more sense than a static directory structure? i just want the final output to be more or less a static website, so what i really need to figure out is where the images will live or be served from
to be clear the problem isn't Hugo! the problem is that i have a ton of images and i don't want to have them living inside the Hugo project, i don't want to check in multiple GBs of assets into my git repo... but idk enough about the existing alternative options for managing a ton of photos, idk what's considered "best practice" these days. like, back in 2014 my choice was to set up a LAMP stack and add my photos into Koken, but Koken has been dead for nearly a decade now... what do i do today?
-
to be clear the problem isn't Hugo! the problem is that i have a ton of images and i don't want to have them living inside the Hugo project, i don't want to check in multiple GBs of assets into my git repo... but idk enough about the existing alternative options for managing a ton of photos, idk what's considered "best practice" these days. like, back in 2014 my choice was to set up a LAMP stack and add my photos into Koken, but Koken has been dead for nearly a decade now... what do i do today?
for anyone curious, what i'm doing *right now* is using a docker image bc i don't want to install and configure php5 on a production server with important stuff on it
i'd like to stop doing that if there's something better i could be doing
-
to be clear the problem isn't Hugo! the problem is that i have a ton of images and i don't want to have them living inside the Hugo project, i don't want to check in multiple GBs of assets into my git repo... but idk enough about the existing alternative options for managing a ton of photos, idk what's considered "best practice" these days. like, back in 2014 my choice was to set up a LAMP stack and add my photos into Koken, but Koken has been dead for nearly a decade now... what do i do today?
@trwnh What about some dumb Git solution like git lfs https://git-lfs.com/ ?
EDIT: Or just doing a gitignore on all the photos
-
@trwnh What about some dumb Git solution like git lfs https://git-lfs.com/ ?
EDIT: Or just doing a gitignore on all the photos
@skyfaller i'd like the photos to be managed somewhere other than on my local storage, but not necessarily on the same vps hosting my git forge
lfs doesn't seem like a good idea because it vastly overcomplicates things -- and the work you'd put into it isn't portable to other projects.
i'm like 40% sure i need some kind of cms, but i have little-to-no exposure to what cms options are available to me -- most everything seems to be enterprise and cost hundreds of dollars at least.
-
for anyone curious, what i'm doing *right now* is using a docker image bc i don't want to install and configure php5 on a production server with important stuff on it
i'd like to stop doing that if there's something better i could be doing
on the extremely general end, i could set up object storage and upload the image assets there, then link to them from within the frontmatter? that doesn’t seem very streamlined though, surely there’s something easier to manage