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

Add spec link #125

Merged
merged 1 commit into from
Nov 21, 2023
Merged

Add spec link #125

merged 1 commit into from
Nov 21, 2023

Conversation

Siegrift
Copy link
Collaborator

Closes #109

Rationale

I wanted to have the high level ideas documented somehere, similarly how it's done with Airseeker. I bookmarked it in Slack and I want to link it in the repo. The services are quite small, but it's the interactions that are important so the document highlights those (e.g. who uses and deploys the services, what calls what, etc...)

The issue also mentions:

Pushing new docker image should be documented as well.

I've created #124 because we are not published yet (apart from my ad-hoc releases which are specific to me).

Consider also moving the configuration to a separate README to avoid nested hastag problems.

I don't want to do because it's not an issue and I'd need to update the spec links (which is additional work).

@Siegrift Siegrift requested a review from andreogle November 21, 2023 08:33
@Siegrift Siegrift self-assigned this Nov 21, 2023
@Siegrift Siegrift requested a review from aquarat November 21, 2023 10:54
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.

Create signed API and Pusher documentation
2 participants