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

Jump to bottom

publish exports to S3 #1034

Open
nilsding opened this issue Feb 1, 2023 · 2 comments
Open

publish exports to S3 #1034

nilsding opened this issue Feb 1, 2023 · 2 comments
Assignees
@nilsding
Labels
suggestion Suggestion to add a new feature or improve a current one

Comments

@nilsding
Copy link
Member

nilsding commented Feb 1, 2023

Pitch

right now exports just get written to somewhere in /public.

in order to scale stuff further it would be better to upload exports to a centralised object storage. This also lets us auto-expire exports after a certain period.

Motivation

it’s something that came to my mind while refactoring the exporter stuff which was built for a single-node deployment. With more than one host this is just not enough anymore.
@nilsding nilsding added the suggestion Suggestion to add a new feature or improve a current one label Feb 1, 2023
@nilsding nilsding self-assigned this Feb 1, 2023
@pixeldesu
Copy link
Member

We should be able to use fog-aws for this, which is already installed. And if fog is configured in the justask.yml we can even use all the credentials to initialize it.

@nilsding
Copy link
Member Author

nilsding commented Feb 1, 2023

sure, but I’d like to use a different AWS account for that :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nilsding nilsding

Labels
suggestion Suggestion to add a new feature or improve a current one
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pixeldesu @nilsding