You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in using Lieu as an internal search engine. The current documentation only describes how one would build Lieu and run lieu host to start the engine, but it does not suggest any specific way of running a system-level service with Lieu (be it via SystemD/Docker/etc). In my opinion, adding a one-command deployment option would make it easier for people to try out Lieu on their machines.
I'd like to add:
an example docker-compose.yml file
documentation about deploying via docker
(still wondering if that makes sense) a small program run as another container specified in docker-compose, which would periodically run lieu precrawl/crawl/ingest
Would you be interested in such a contribution, or do you find providing docker-based deployment documentation as too opinionated for your project?
The text was updated successfully, but these errors were encountered:
@Wint3rmute hey! great username :) happy to hear you'd like to use Lieu! I wouldn't want to maintain the docker-compose.yml file, but how about this:
create a PR that adds a new file to the docs/ section titled "deployment-with-docker.md", for an example see the querying doc. provide either the example docker-compose file inline of that document or as a link to a repo with a deployment that you maintain, and then write the rest of the deployment instructions.
Hello!
I'm interested in using Lieu as an internal search engine. The current documentation only describes how one would build Lieu and run
lieu host
to start the engine, but it does not suggest any specific way of running a system-level service with Lieu (be it via SystemD/Docker/etc). In my opinion, adding a one-command deployment option would make it easier for people to try out Lieu on their machines.I'd like to add:
docker-compose.yml
filedocker-compose
, which would periodically runlieu precrawl/crawl/ingest
Would you be interested in such a contribution, or do you find providing docker-based deployment documentation as too opinionated for your project?
The text was updated successfully, but these errors were encountered: