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.

Sign up for GitHub

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

Store cache in S3 storage #27

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+2,936 −107
Open

Store cache in S3 storage #27

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
26a1fcf
Store cache in S3 storage
infomiho May 6, 2024
d060d2a
PR comments
infomiho May 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,9 @@ Copy env.example to .env and fill it with your PostHog API key and Discord bot t

Both are needed to run bot locally, but only PostHog API key is needed to run just analytics locally.

Also, if you want to use the S3 storage to store the cache file, fill in the S3 credentials as well. This is useful if you want to
test the S3 storage locally.
Copy link
Member

Choose a reason for hiding this comment

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

Not only that, but to also not have to wait for long time to fetch all the analytics locally, if you don't have any fetched yet.


### Installation

Run `npm install` for the first time or after any changes in npm deps.
Expand Down
6 changes: 6 additions & 0 deletions env.example
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,8 @@
WASP_POSTHOG_KEY=
DISCORD_BOT_TOKEN=

S3_IS_USED=true
S3_ACCESS_KEY=
Martinsos marked this conversation as resolved.
Show resolved Hide resolved
S3_ACCESS_SECRET=
S3_ENDPOINT=
S3_BUCKET_NAME=
Loading