Docker compose #4731
Open
Docker compose #4731
Conversation
This file contains hidden or 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
| Alternatively, you can also launch Obot with Docker Compose by adding your [custom environment variables](https://docs.obot.ai/configuration/server-configuration) into `docker-compose.yaml` & running: | ||
|
|
||
| ``` | ||
| docker compose up --build |
There was a problem hiding this comment.
This should be docker compose up without --build, correct? you don't mean to build the image from source code?
There was a problem hiding this comment.
🤔Maybe we should have the option of running docker compose for setting up the dev environment as well.
I'll meditate on it a bit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Obot Team 👋
Great project :)
I had some friction setting up & figured a Docker Compose file might enable an even smoother onboarding experience.
I found myself needing to remove my container in order to add new environment variables as I went (& therefore losing my state of users and auth provider credentials).
I like the docker compose method of rebuilding easily with new environment variables.
Further down the line, connecting this docker-compose with a .env file and creating a sample .env.example file could make this onboarding experience even smoother - to verify users don't push up their keys accidentally :)