This repository has been archived by the owner on Oct 16, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Docs structure overhaul as discussed in #179 This PR is meant to replace #179 and #182 What was done: - Created subpages for all major features (models/data/serving/building/deploy) in user-guide for each - Moved there hand-crafted documentation from extension docs in #179 - index pages are from GS - Renamed Extension section into Object Reference - restructured it. was: `<ext type>/<ext name>`, now: `<object group>/<ext name>`. Now multipurpose extensions (eg docker has build & deploy) has two pages - Object Reference is now fully autogenerated - Added builtin implementations there too - Moved details about mlem abcs and mlem objects from UG - Rewritten GS - New User Guide pages - New Object reference index pages written - Use Cases cleaned up TODO: - [x] rewrite GS Deployment - [x] rewrite UG Deployment (+ explain what State is) - [x] update UG Heroku - [x] merge UG K8s @madhur-tandon - [x] update UG Sagemaker - @mike0sv, [there are your TODOs left](https://mlem-ai-new-docs-struct-hy95mv.herokuapp.com/doc/user-guide/deploying/sagemaker) - [x] write UG Docker @madhur-tandon - [x] update CLI reference - [x] update API reference - [x] merge UG export to venvs @madhur-tandon - [x] rewrite Project structure - [x] update UC - remote `.mlem/` dir and `mlem.api.ls` mentions - [x] search and remove all other mentions of `.mlem/` dir and `mlem.api.ls` - [x] search and update all other mentions of `mlem init` - [x] search and update all other mentions of `--conf` or `-c` - [x] fix broken links @madhur-tandon - [x] add `mlem checkenv` to command reference. Why it wasn't generated I wonder?
- Loading branch information
Showing
139 changed files
with
5,925 additions
and
1,507 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.