https://dagster.io/ logo
#community-showcase
Title
# community-showcase
f

Fraser Marlow

03/08/2023, 3:18 AM
Our latest blogpost got picked up by Hacker News: Check it out: https://news.ycombinator.com/ The article is
How we deploy faster with warm Docker containers
daggy love 4
c

clay

03/08/2023, 1:45 PM
I saw that and was wondering whether the learnings could be applied easily to self-hosted multi-container docker deployments.
s

Shantanu

03/08/2023, 2:48 PM
By the way anyone looking for direct link to the discussion https://news.ycombinator.com/item?id=35064079
f

Fraser Marlow

03/08/2023, 4:55 PM
The author of the post (Shalabh) is available here on the Dagster Slack, but that Hacker News thread looks pretty active so feel free to ask him questions there.
d

David Merritt

03/08/2023, 4:57 PM
@Shalabh Chaturvedi - how can I turn this on for an existing serverless instance? The article says
Copy code
it is now on by default for all new serverless sign-ups.
but I don't see an option to turn this on explicitly?
s

Shalabh Chaturvedi

03/08/2023, 5:12 PM
Hi @David Merritt - This has been on by default since December 2022 so if you signed up after that it should already be enabled. If you look in you
.github/workflows/deploy.yml
, you will see an
ENABLE_FAST_DEPLOYS
env. You can set it to
'True'
to enable it. You would also need to update your
branch_deployments.yml
in the same directory.
❤️ 2
clay - iiuc you are asking about hybrid deployments. while this is currently not available for hybrid deployments it is something we will consider implementing in the future. is there a specific scenario where you think this is useful? with dagster you can invoke any external subprocess, so you could have a job that executes "download a pex file; run the pex file in a subprocess". however building and uploading the pex file is something you would have to implement.
d

David Merritt

03/08/2023, 5:31 PM
thanks - I'll check that. We signed up before dec 2022
s

Shalabh Chaturvedi

03/08/2023, 5:42 PM
if you have not modified your
yml
files, you can refresh them manually: 1. copy over the files from here 2. replace the
DAGSTER_CLOUD_URL: ${{ secrets.DAGSTER_CLOUD_URL }}
line with a literal value for your url. This is just the url for dagster cloud without a trailing slash, for example
DAGSTER_CLOUD_URL: "<http://my-org-name.dagster.cloud>"
If you have modified your yml files, you would need to port your changes to the new copy.
2 Views