-
Notifications
You must be signed in to change notification settings - Fork 184
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
declarative deployments #1611
Milestone
Comments
Someone also recently shared this with me: https://www.chugsplash.io/ |
i think it would be good to have an hour long jam on this (along with maybe a larger tooling discussion) |
… On Thu, Sep 28, 2023 at 5:15 PM Kevin Ingersoll ***@***.***> wrote:
we should probably do #1006
<#1006> and #1636
<#1636> first
—
Reply to this email directly, view it on GitHub
<#1611 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFBYUKZOZCUNZIQYOB7VP4TX4WPDTANCNFSM6AAAAAA5HZQVDA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This was referenced Oct 4, 2023
This was referenced Oct 5, 2023
done in #1702 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given a mud config, systems, etc. and an optional world address, we should be able to figure out what needs to be deployed (missing tables, updated systems, etc.) and turn our deploy process from imperative to declarative.
The text was updated successfully, but these errors were encountered: