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

Document a real setup, with a staging and production instance #1753

Open
boxydog opened this issue Aug 27, 2024 · 0 comments
Open

Document a real setup, with a staging and production instance #1753

boxydog opened this issue Aug 27, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@boxydog
Copy link

boxydog commented Aug 27, 2024

Documentation description

I have read https://dlthub.com/docs/general-usage/credentials/setup/#credential-types and https://dlthub.com/docs/general-usage/naming-convention.

I still do not understand how to set up a staging and production instance, each of which has its own state.

I wish to load incrementally, so I need a crontab running every so often (1-3 hours).

So I think I'm going to set the SOURCES__CREDENTIALS and DESTINATION__CREDENTIALS variables to postgres connection strings.

I think I also need some way to save and restore pipeline state, so the incremental state is correct even if the crontab box does not have permanent disk storage. Someone pointed me to an example gist: https://gist.github.com/rudolfix/ee6e16d8671f26ac4b9ffc915ad24b6e

But all this is a lot to figure out, and I don't feel like an actual example staging and production environment that works is well documented.

Are you a dlt user?

Yes, I'm already a dlt user.

@burnash burnash added the documentation Improvements or additions to documentation label Sep 10, 2024
@burnash burnash self-assigned this Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: Todo
Development

No branches or pull requests

2 participants