-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IMPLEMENTATION] Local FireCrawl + Local LLM Setup Discussion #2
Comments
Branch Creation: Create a feature branch (e.g., feature/firecrawl-llm-drafting) and isolate your implementation. |
Nice LLM answer. I've seen @ericciarla updating the app everyday so i'll do PR to support local firecrawl and local llm if needed, depends on where the project is going ? |
That sounds awesome! Excited to see it |
Graphic Designing (https://gict.co.in/graphic-design-course/) was a course I absolutely enjoyed. It started with the most basic principles of design and ended on very advanced topics, and, honestly, the hands-on projects helped do the grasping of all concepts. The teachers were really good at what they did and gave individualized guidance and feedback; it was a big difference. Now, I feel quite comfortable working with design software like Photoshop and Illustrator to bring ideas to life. This is really what you need if you are wondering about adding to the creative aspect of your skill set and making a career in design. Highly recommend!- #GraphicDesign #CreativeSkills #GraphicsDesignCourse #LearnDesign #DigitalArt #GraphicDesigning |
Hey!
I've been exploring using local crawling with local FireCrawl as an alternative to the Twitter API.
I'm then using a local LLM (meta-llama-3.1-8b-instruct in LMStudio) to generate drafts.
I've been testing the workflow in my fork here: fork, and it's been pretty smooth.
I think this approach could be beneficial and would love to discuss the possibility of adding this feature to the main repo!
(i've added tests too - i'll do a proper branch if that sounds interesting)
The text was updated successfully, but these errors were encountered: