feat: AI driven coding and deployment guide#1119
Conversation
gandie
changed the title
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Lars Bergmann <lars@bergmann82.de>
gandie
force-pushed
the
feat/vibecoding-guidance
branch
from
ef69ab8 to
3db6ef4
Compare
| - [ ] Shared the link with a friend — get feedback | ||
| - [ ] Celebrate your first deploy! 🎉 | ||
|
|
||
| ## Zero-conf deployment at mittwald {#zero-conf-deployment-at-mittwald} |
There was a problem hiding this comment.
Maybe rebase this change on top of #1124, so we can already link to that action's documentation?
| ```shellsession | ||
| user@local $ git clone https://github.com/<your-org>/<your-repo>.git | ||
| user@local $ cd <your-repo> | ||
| ``` |
There was a problem hiding this comment.
Indentation, otherwise this will break the markdown list.
|
|
||
| Apps built through AI-driven development are easy to create, and deployment options vary widely. | ||
|
|
||
| Different platforms offer different trade-offs. Vendors like Replit and Lovable prioritize developer speed |
There was a problem hiding this comment.
Just wondering if it might even make sense to have dedicated pages (or sections, at least) for "Deploy from Replit to mittwald" and similar. Possible alone for SEO reasons... 🤔
|
|
||
| If we can export to GitHub, we have good chances to deploy anywhere. | ||
|
|
||
| Most platforms support GitHub as a source for deployment, and having a well-structured |
There was a problem hiding this comment.
Maybe even link to vendor-specific documentation pages, like https://docs.replit.com/references/workspace-tools/git-interface or https://docs.lovable.dev/integrations/github?
|
|
||
| ```shellsession | ||
| user@local $ mw project create --description=<project-name> --update-context | ||
| user@local $ mw experimental deploy |
There was a problem hiding this comment.
Add a note regarding the experimental nature of the mw experimental deploy command?
| Prerequisites: | ||
| - An AI-developed app with a GitHub repository | ||
| - A mittwald hosting account | ||
| - Basic understanding of Git and GitHub | ||
| - mittwald CLI installed and configured |
There was a problem hiding this comment.
Technically, the "GitHub" and "mittwald CLI" requirements are an "either/or" relation, aren't they?
When using the mw experimental deploy command directly, I'm not bound to GitHub or any code hosting solution, and when using the GitHub action, I don't need the mw CLI.
No description provided.