Channels
announcements
ask-marvin
best-practices-coordination-plane
data-ecosystem
data-tricks-and-tips
events
find-a-prefect-job
geo-bay-area
geo-berlin
geo-boston
geo-chicago
geo-colorado
geo-dc
geo-israel
geo-japan
geo-london
geo-nyc
geo-seattle
geo-texas
gratitude
introductions
marvin-in-the-wild
pacc-clearcover-june-12-2023
pacc-may-31-2023
ppcc-may-16-2023
prefect-ai
prefect-aws
prefect-azure
prefect-cloud
prefect-community
prefect-contributors
prefect-dbt
prefect-docker
prefect-gcp
prefect-getting-started
prefect-integrations
prefect-kubernetes
prefect-recipes
prefect-server
prefect-ui
random
show-us-what-you-got
Title
s
sark
09/14/2020, 3:56 AMalso i am registering my flows from a machine separate to the server and to whatever will run my flows, i hope this is not a anti-pattern
r
Rizky Eko Putra
09/14/2020, 7:45 AMHi @sark, I am also doing like you are doing, may I know how you register flow from another machine?
I got error when register flow, its look like, the client connected to prefect cloud instead prefect core that I deployed seperately
s
sark
09/14/2020, 7:57 AMhi rizky i do
[server]
host = "<http://host>"
port = "4200"
endpoint = "${server.host}:${server.port}"~/.prefect/config.tomlr
Rizky Eko Putra
09/14/2020, 8:09 AMok thanks
eh, @sark, I already success submit a flow to the backend and already display on UI also, with "dev" labels, and then I also already run a Kubernetes agent with the label "dev" too and connected to the same backend. but the flow cannot run, still on pending, any other miss from me?
nvm, its missmatch label