mattwaler / fastify-starter

A starter for fastify with Twig, Tailwind, and Alpine, and HTMX.

👋🏼 Hello! I'm Matt Waler.

I am a JavaScript-focused developer from Ohio. I am a firm believer that simple, pragmatic, and readable code is far superior to complex abstractions.

🛠 Skills

I specialize in the following tools:

• React
• TailwindCSS
• Next.js
• Craft CMS
• React Native
• Alpine.js
• Eleventy

🎾 Hobbies

If I'm not writing code here, you'll most likely find me:

• Playing Tennis
• Honing my cooking skills
• Losing games on Chess.com
• Lifting weights and then dropping them
• Belting pop music

🌐 Find Me Online

If you still haven't found me, your best bet is to look me up on the following platforms:

• My ever-evolving personal website
• Trying to act professional on linkedin
• Posting to my story on instagram

fastify-starter's Issues

Does autoload inits Fastify or where is it defined?

Hey! First of all, thanks for creating this starter. It has been a great example to get going with fastify.

There's, however, one thing about your project that confuses me. I was trying to set up a server option, and I noticed that your project doesn't require fastify anywhere. In the fastify-autoload examples I have seen around fastify is initialized before the autoload module. e.g.: https://github.com/fastify/fastify-autoload#example

So how does this work exactly? Where exactly is fastify defined in the context of this project, and how can I set up options such as:

const fastify = require('fastify')({
  ignoreTrailingSlash: true
})

I feel like I'm missing something obvious but can't figure it out.

GCP Deploy

Hi,
I'm testing your repo as a port of a an aurliea js frontend calling a fastify bakend. Both projects are deployed on GCP. About half way thru thje port I decided to test to deploy to gcp and if fails. Any ideas on how to deploy your repo to GCP?
Thanks for your great contribution,
John