Netlify domain: Commercial font question (GitHub / Netlify)

Hello Forums

I am this summer coming with my next Folio, hosted on Netlify and deployed to there from GitHub.

Now, I am using one commerical font, loaded locally as woff with Nuxt-Fonts module. Howeverr, since this font resides in /public in my Nuxt project I wonder: what is best practice for preventing sharing it from GitHub.

Is it: push to GitHub, then once build is done, remove the font from GitHub? I

Thankful for advice, Thomas

@thomasjtt Can’t you just use a Private Repository?
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility

Hi

Thanks for reply. I want to share the code. But I will do some research into this and see if I can find any solution down the road that prevents me from being another GitHub pirate friend!

Thomas

It takes less than 30 seconds for anyone to download a font file from dev tools. It’s not worth wasting your efforts to prevent font piracy. The only way is to use the font to render image on the server and serve that instead (this is what’s used by font store websites).

Hi

Yes it does. But that doesn’t mean you should provide the font point blank in a repository. It is a bit like saying, people can do X so who cares about preventing Y when they can get around it anyhow. The discussion on many a blog on this topic is not for nothing. So I do not agree with you.

I am not holding for an answer on this here, and not keying in on this post anymore, will post again if sometthing else is of concern, found out what I can by now and moved on. Might use a private repo for the deploy part only.

.T

Hi

Yes it does. But that doesn’t mean you should provide the font point blank in a repository. It is a bit like saying, people can do X so who cares about preventing Y when they can get around it anyhow. The discussion on many a blog on this topic is not for nothing. So I do not agree with you.

I am not holding for an answer on this here, and not keying in on this post anymore, will post again if sometthing else is of concern, found out what I can by now and moved on.

.T