search

OpenINF / openinf-jekyll-asset-path-plugin

A liquid tag to output a relative URL for assets based on the Jekyll post or page
MIT License
0 stars 1 forks source link

💎✨ form project into a ruby gem structure & gemify #2

Open OpenINFbot opened 6 months ago

OpenINFbot commented 6 months ago

FROM FAILED CI RUN ⬇️:

Fetching https://github.com/OpenINF/openinf-jekyll-asset-path-plugin Fetching gem metadata from https://rubygems.org/.......... Could not find gem 'jekyll-asset-path' in https://github.com/OpenINF/openinf-jekyll-asset-path-plugin (at main@23491ff). Error: Process completed with exit code 7.

just as i had expected; that one is not a gem yet — diamonds are only made under pressure

Originally posted by @DerekNonGeneric in https://github.com/OpenINF/openinf.github.io/issues/1131#issuecomment-1965074801

Description

A concise recap summarily detailing what all are the changes being made.

List of any relevant issue numbers:

DerekNonGeneric commented 6 months ago

well, i had been wondering about doing this since we will have to also for our Reflection theme too

DerekNonGeneric commented 6 months ago

entrypoint for Gemify guidance seems like:

DerekNonGeneric commented 6 months ago

⚠️⚠️⚠️⚠️⚠️

being at this point w/o a VM (or devcontainer) containing ruby toolchain is sh*t for ruby development (in particular) — DO NOT PROCEED ON HOST OS

⚠️⚠️⚠️⚠️⚠️

@OpenINF/ateamgrimesai has been ruthlessly drilling the devcontainer topic TOO 😅

but what about Ruby Software Development on macOS?

🙅 f*ck no; you're probs SOL

☢️☢️☢️

☢️☢️☢️

repeat: 🙅 f*ck no

🤷‍♂️ i think we may have been saved again by @OpenINF/ateamgemini 🙏🙏

🔗 https://github.com/OpenINF/docker-fisher/issues/53#issuecomment-1965842087