Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copy over server scaffolding #94

Closed
wants to merge 4 commits into from
Closed

Copy over server scaffolding #94

wants to merge 4 commits into from

Conversation

richardhuaaa
Copy link
Contributor

@richardhuaaa richardhuaaa commented Jul 27, 2024

Basically moves over the work from xmtp/xmtp-node-go#397, as well as some utils from the old repo and a clean go dependency list.

  • Sets up basic server
  • Sets up basic API server using generated protos
  • Sets up DB
  • Sets up interface for NodeRegistry

Still need to copy over the CI and docker

@richardhuaaa richardhuaaa changed the base branch from main to rich/protos July 27, 2024 00:16
@@ -1,3 +1,64 @@
module github.com/xmtp/xmtpd

go 1.21.11
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should switch to go 1.22, since we are starting fresh and that's the current stable version

@@ -0,0 +1,116 @@
package main
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's convention in Go packages to put these in a cmd folder. Think we should keep that convention

@neekolas
Copy link
Contributor

Oof. I missed that this PR exists and made an almost identical version.

Think the only real difference is that I left out the DB stuff, since I'd like to take a fresh look at the DB migrations since we don't need Bun anywhere in this repo

Base automatically changed from rich/protos to main July 29, 2024 17:35
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