mirror of
https://github.com/invoke-ai/InvokeAI
synced 2024-08-30 20:32:17 +00:00
0439b51a26
* partially working simple installer * works on linux * fix linux requirements files * read root environment variable in right place * fix cat invokeai.init in test workflows * fix classical cp error in test-invoke-pip.yml * respect --root argument now * untested bat installers added * windows install.bat now working fix logic to find frontend files * rename simple_install to "installer" 1. simple_install => 'installer' 2. source and binary install directories are removed * enable update scripts to update requirements - Also pin requirements to known working commits. - This may be a breaking change; exercise with caution - No functional testing performed yet! * update docs and installation requirements NOTE: This may be a breaking commit! Due to the way the installer works, I have to push to a public branch in order to do full end-to-end testing. - Updated installation docs, removing binary and source installers and substituting the "simple" unified installer. - Pin requirements for the "http:" downloads to known working commits. - Removed as much as possible the invoke-ai forks of others' repos. * fix directory path for installer * correct requirement/environment errors * exclude zip files in .gitignore * possible fix for dockerbuild * ready for torture testing - final Windows bat file tweaks - copy environments-and-requirements to the runtime directory so that the `update.sh` script can run. This is not ideal, since we lose control over the requirements. Better for the update script to pull the proper updated requirements script from the repository. * allow update.sh/update.bat to install arbitrary InvokeAI versions - Can pass the zip file path to any InvokeAI release, branch, commit or tag, and the installer will try to install it. - Updated documentation - Added Linux Python install hints. * use binary installer's :err_exit function * user diffusers 0.10.0 * added logic for CPPFLAGS on mac * improve windows install documentation - added information on a couple of gotchas I experienced during windows installation, including DLL loading errors experienced when Visual Studio C++ Redistributable was not present. * tagged to pull from 2.2.4-rc1 - also fix error of shell window closing immediately if suitable python not found Co-authored-by: mauwii <Mauwii@outlook.de>
35 lines
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
---
|
|
title: Overview
|
|
---
|
|
|
|
We offer several ways to install InvokeAI, each one suited to your
|
|
experience and preferences.
|
|
|
|
1. [Automated Installer](INSTALL_AUTOMATED.md)
|
|
|
|
This is a script that will install all of InvokeAI's essential
|
|
third party libraries and InvokeAI itself. It includes access to a
|
|
"developer console" which will help us debug problems with you and
|
|
give you to access experimental features.
|
|
|
|
2. [Manual Installation](INSTALL_MANUAL.md)
|
|
|
|
In this method you will manually run the commands needed to install
|
|
InvokeAI and its dependencies. We offer two recipes: one suited to
|
|
those who prefer the `conda` tool, and one suited to those who prefer
|
|
`pip` and Python virtual environments. In our hands the pip install
|
|
is faster and more reliable, but your mileage may vary.
|
|
|
|
This method is recommended for users who have previously used `conda`
|
|
or `pip` in the past, developers, and anyone who wishes to remain on
|
|
the cutting edge of future InvokeAI development and is willing to put
|
|
up with occasional glitches and breakage.
|
|
|
|
3. [Docker Installation](INSTALL_DOCKER.md)
|
|
|
|
We also offer a method for creating Docker containers containing
|
|
InvokeAI and its dependencies. This method is recommended for
|
|
individuals with experience with Docker containers and understand
|
|
the pluses and minuses of a container-based install.
|
|
|