diff --git a/.dockerignore b/.dockerignore new file mode 100644 index 000000000..3466d3150 --- /dev/null +++ b/.dockerignore @@ -0,0 +1,6 @@ +* +!*.py +!requirements.txt +!images/* +!front-end/* +front-end/node_modules/* diff --git a/.github/media/app1-concept.png b/.github/media/app1-concept.png index 6ed338b3f..89d02fb81 100644 Binary files a/.github/media/app1-concept.png and b/.github/media/app1-concept.png differ diff --git a/.github/media/app1-generate.png b/.github/media/app1-generate.png new file mode 100644 index 000000000..233a1dd40 Binary files /dev/null and b/.github/media/app1-generate.png differ diff --git a/.github/media/app1-rag-selector.png b/.github/media/app1-rag-selector.png new file mode 100644 index 000000000..1620a44a9 Binary files /dev/null and b/.github/media/app1-rag-selector.png differ diff --git a/.github/media/app1-ticket.png b/.github/media/app1-ticket.png new file mode 100644 index 000000000..2818be34f Binary files /dev/null and b/.github/media/app1-ticket.png differ diff --git a/.github/media/app2-model.png b/.github/media/app2-model.png index cb81d8838..576eee6ab 100644 Binary files a/.github/media/app2-model.png and b/.github/media/app2-model.png differ diff --git a/.github/media/app2-ui-1.png b/.github/media/app2-ui-1.png new file mode 100644 index 000000000..f29353150 Binary files /dev/null and b/.github/media/app2-ui-1.png differ diff --git a/.github/media/app3-ui.png b/.github/media/app3-ui.png new file mode 100644 index 000000000..1f1dc66e7 Binary files /dev/null and b/.github/media/app3-ui.png differ diff --git a/.github/media/app5-ui.png b/.github/media/app5-ui.png new file mode 100644 index 000000000..23ba0d841 Binary files /dev/null and b/.github/media/app5-ui.png differ diff --git a/.gitignore b/.gitignore index 30bd623c2..93ecc0fff 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,5 @@ .env - +data/ +embedding_model/* +!embedding_model/.ignore +.DS_Store diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 000000000..bd0c2245e --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,250 @@ +# Contributing to Docker + +This page contains information about reporting issues as well as some tips and +guidelines useful to experienced open source contributors. Finally, make sure +you read our [community guidelines](#docker-community-guidelines) before you +start participating. + +## Topics + +* [Reporting Security Issues](#reporting-security-issues) +* [Reporting Issues](#reporting-other-issues) +* [Quick Contribution Tips and Guidelines](#quick-contribution-tips-and-guidelines) +* [Community Guidelines](#docker-community-guidelines) + +## Reporting security issues + +The Docker maintainers take security seriously. If you discover a security +issue, please bring it to their attention right away! + +Please **DO NOT** file a public issue, instead send your report privately to +[security@docker.com](mailto:security@docker.com). + +Security reports are greatly appreciated and we will publicly thank you for it. +We also like to send gifts—if you're into Docker schwag, make sure to let +us know. We currently do not offer a paid security bounty program, but are not +ruling it out in the future. + +## Reporting other issues + +A great way to contribute to the project is to send a detailed report when you +encounter an issue. We always appreciate a well-written, thorough bug report, +and will thank you for it! + +Check that [our issue database](https://github.com/docker/gen-ai-stack/issues) +doesn't already include that problem or suggestion before submitting an issue. +If you find a match, you can use the "subscribe" button to get notified on +updates. Do *not* leave random "+1" or "I have this too" comments, as they +only clutter the discussion, and don't help resolving it. However, if you +have ways to reproduce the issue or have additional information that may help +resolving the issue, please leave a comment. + +When reporting issues, always include: + +* The output of `docker version`. +* The output of `docker info`. + +Also include the steps required to reproduce the problem if possible and +applicable. This information will help us review and fix your issue faster. +When sending lengthy log-files, consider posting them as a gist (https://gist.github.com). +Don't forget to remove sensitive data from your logfiles before posting (you can +replace those parts with "REDACTED"). + +## Quick contribution tips and guidelines + +This section gives the experienced contributor some tips and guidelines. + +### Pull requests are always welcome + +Not sure if that typo is worth a pull request? Found a bug and know how to fix +it? Do it! We will appreciate it. Any significant improvement should be +documented as [a GitHub issue](https://github.com/docker/gen-ai-stack/issues) before +anybody starts working on it. + +We are always thrilled to receive pull requests. We do our best to process them +quickly. If your pull request is not accepted on the first try, +don't get discouraged! Our contributor's guide explains [the review process we +use for simple changes](https://docs.docker.com/opensource/workflow/make-a-contribution/). + +### Talking to other Docker users and contributors + +
Community Slack | ++ The Docker Community has a dedicated Slack chat to discuss features and issues. You can sign-up with this link. + | +
+ You can follow Docker's Twitter feed + to get updates on our products. You can also tweet us questions or just + share blogs or stories. + | +