Update

[iambateman]

just pushed to main: 9ea9922

I'll PR moving forward but I forgot.

Installing Signal

php artisan signal:install

This is set up. It spins up signal.sqlite with an initial table.

If the scrolling effect on that install command is distracting, we can cut it.

Events architecture

I propose the database uses event sourcing to build a big pile of data and then our app will sort it all out.

• Use inspiration from the Verbs package to do "event sourcing lite." There's an events table which captures every analytics event which has ever happened.
• The JS snippet on the frontend pushes all events into the events table.
• We project our tables using that data.

This reduces the risk of breaking changes down the road.

Project

https://github.com/orgs/signalmetrics/projects/1 Trying out a kanban board.

Next up

Here's what makes sense to me...

• me: build big pile of data
  • JS code that fires data through cleaning pipeline and into events
  • handle GDPR requirements around IP addresses, deidentifying users etc.
• you: start cranking out the backend
  • setting up the tables which will get used for display (right now it's just the events table)
  • start building out UI

In my mind, that gives us both a chance to live in our own playground and make a ton of progress. Thoughts? I'm not trying to assign work at all, just trying to figure out the best way to move forward.

[tnylea]

The install command is awesome! Great job.

I'm going to try it out when I get back from the Cruise.

Yeah, I think you're right about the tasks. I'm open to work on anything as well, so feel free to assign me anything. I'm game 🤙

[iambateman]

So great! I hope the cruise has been a blast.

When you get a chance, could you finish stubbing out the core of the views you were working on last week? I'm hoping that it'll be working enough that Tailwind compiles, JS builds, Livewire is running.

Of course, I will jump into the backend too once you've got the environment set up to your liking.