-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add support for pushing the database #13
Comments
A task that replaces the remote database with your local database is a great feature! |
That'd be swell |
This seems to be something Good Work really wants judging from who's commented and upvoted so far 😂 |
Don't worry, I'm working on the feature as we speak :) Here's an idea of the steps Swiff will perform:
Hope to have it released soon, I'll let you know. |
Apologies for the delay on this, there's some issues that surfaced after adding this feature so I'm working through those at the moment. Aiming for next release within a week, should be sweet. |
@ben-rogerson No need to apologize. Appreciate your work! Excited! |
Awesome, thanks @ben-rogerson 💓 |
@chasegiunta @chrisrowe Hope you guys had a great easter holiday! Swiff v1.4.0 was just released 🥳 |
This would definitely have to be in conjunction with #4, but it would be useful during initial developments of a site to push a local database to a remote environment (99% of the time, a staging server).
Currently, since multi-environments aren't supported, our staging site is configured in swiff, and we're manually uploading the local database to the staging server to let the client see incremental work.
The text was updated successfully, but these errors were encountered: