W
Wasp•3mo ago
ralph

Best wasp way to handle documentation hosting?

wasp version 0.16.3 on WSL
4 Replies
kapa.ai
kapa.ai•3mo ago
Hi @ralph. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the knowledge sources provided, there isn't specific information about documentation hosting within Wasp itself. The knowledge sources mainly cover Wasp installation, deployment of Wasp applications, editor setup, and some common issues with WSL. For deploying a Wasp application (which could include documentation), Wasp supports: 1. Using the Wasp CLI for one-command deployment (currently supporting Fly.io) 2. Manual deployment where you can deploy: - The static client to services like Netlify - The Node.js server to services like Fly.io - The PostgreSQL database to services like Neon If you're specifically looking to host documentation for your Wasp project, you might want to consider standard documentation hosting solutions that work well with React applications, since Wasp generates a React frontend. Since you're using WSL, I should mention that you should ensure your Wasp project files are stored on the Linux filesystem rather than the Windows filesystem to avoid issues with file change detection, as noted in the documentation: Quick Start guide. If you need more specific guidance about documentation hosting within Wasp, I'd recommend asking in the Wasp Discord community where you might get more targeted advice from other Wasp users. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @ralph, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
ralph
ralphOP•3mo ago
@kapa.ai how do I mark this as solved lol
kapa.ai
kapa.ai•3mo ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the knowledge sources, I can see that in Discord support threads, users often mark their issues as "solved" or "resolved" by editing the title of their thread to include "(SOLVED)" or "(Resolved)" at the beginning or end of the title. For example, in several Discord threads: - A user changed their thread title to "Stripe testing issues(401) (SOLVED)" Discord thread - Another user updated their thread to "(Resolved) Prisma Error on Mac" Discord thread If you're asking about marking your question as solved here in this chat interface, there isn't a specific mechanism mentioned in the knowledge sources for that. This isn't a Discord thread where you can edit the title. If you need further assistance with Wasp, you can always reach out to the Wasp community on Discord or via email at [email protected]. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @ralph, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
Carlos
Carlos•3mo ago
Done 🙂

Did you find this page helpful?