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

Remove outdated docs about running scheduler and server with gradle run #2676

Merged
merged 2 commits into from Apr 8, 2021

Conversation

cgardens
Copy link
Contributor

closes #2528

What

  • Removes references in the docs for using gradle :run for running the scheduler and server.
  • I tried to get it so we could use :run again (so that we could easily use the intellij debugger). Unfortunately the fact that the config repository is in a docker volume breaks this. I have left the env variable set up as close as I got it so that we can do this in the future if we ever change our config repository set up.
  • Internally, if you know what you're doing you can run apps in intellij. Otherwise, removed from external docs.

### Connector Specification Caching

The Configuration API caches connector specifications. This is done to avoid needing to run docker everytime one is needed in the UI. Without this caching, the UI crawls. If you update the specification of a connector and you need to clear this cache so the API / UI pick up the change. You have two options: 1. Go to the Admin page in the UI and update the version of the connector. Updating to the same version will for the cache to clear for that connector. 1. Restart the server

```bash
docker-compose --env-file .env.dev -f docker-compose.yaml -f docker-compose.dev.yaml down -v
docker-compose --env-file .env.dev -f docker-compose.yaml -f docker-compose.dev.yaml up
VERSION=dev docker-compose down -v
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we don't need VERSION for down

environment "WORKSPACE_ROOT", env.WORKSPACE_ROOT
environment "WORKSPACE_DOCKER_MOUNT", env.WORKSPACE_DOCKER_MOUNT
environment "LOCAL_DOCKER_MOUNT", env.LOCAL_DOCKER_MOUNT
environment "CONFIG_ROOT", "/tmp/airbyte_config"
Copy link
Contributor

Choose a reason for hiding this comment

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

for my own knowledge - are the airbyte-scheduler and airbyte-server config roots identical because we share information via the volume?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes

@cgardens cgardens force-pushed the cgardens/remove_gradle_apps branch from fc51f71 to ae4cee5 Compare April 5, 2021 20:23
Base automatically changed from cgardens/temporal_client10 to master April 8, 2021 21:37
@cgardens cgardens force-pushed the cgardens/remove_gradle_apps branch from ae4cee5 to ef1c11f Compare April 8, 2021 21:39
@cgardens cgardens merged commit cac6808 into master Apr 8, 2021
@cgardens cgardens deleted the cgardens/remove_gradle_apps branch April 8, 2021 21:39
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.

Developing Locally Docs are out of date
3 participants