Skip to content

Conversation

alexluong
Copy link
Collaborator

Development Setup

$ git clone ... & cd EventKit
$ cp .env.example .env
$ docker compose up

This should work. I already set up live reload with Docker too so when you make changes to the server, it should be reflected during development.

Let me know if you'd like to make the server work without Docker Compose. I think we may need to add some code to read environment variables and that's about it.

Business logic directories

Besides the boilerplate setup code, the meat of the project should probably be in the business logic packages like destination, tenant, event, etc. Currently, I have things pretty flat, everything is inside internal and that's it. If you think it makes sense, I can try to organize the packages a bit so there's a better differentiation between glue code and business logic.

CRUD ops

Please check out destination/handlers.go to see the CRUD operations. I think one potential missing thing is how we want to treat errors. I don't see that in the design document yet, so I'm just returning the status code for now. If we have a certain error format, we can potentially write a helper to transform Go err into that structure.

Postman

Here's the Postman Collections I have for this so far, just in case it helps.

EventKit.postman_collection.json

@alexluong alexluong merged commit 8ded76a into main Aug 22, 2024
@alexluong alexluong deleted the scaffolding branch August 22, 2024 12:02
@alexbouchardd alexbouchardd mentioned this pull request Sep 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants