How is the wasp website built?
https://wasp-lang.dev/
1) I wanted to contribute a few docs and would rather see the website before I submit
2) Mostly I wanted to move deployment not to be nested under /advanced, or? Deployment is actually a general topic for everyone.
6 Replies
Hi @Adam. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
The Wasp website is built using Docusaurus, a complete solution for documentation that includes website, docs, and blog functionalities. The website's code is hosted in the
web/ repository of the Wasp project on GitHub. You can contribute to the documentation by creating a separate PR on the wasp-lang/web repository to add or edit docs for it (source (https://github.com/wasp-lang/wasp/issues/287)).
Before you submit your contributions, you can check the CONTRIBUTING.md (https://github.com/wasp-lang/wasp/blob/main/CONTRIBUTING.md) file in the Wasp GitHub repo for all the requirements and instructions. You can also join the Wasp community on Discord (https://discord.gg/rzdnErX) to discuss your ideas and get feedback (source (https://wasp-lang.dev/docs/contributing)).
Regarding your suggestion to move the deployment section out of the /advanced category, it's a valid point. Deployment is indeed a general topic that could be of interest to many users. You can bring this to the attention of the Wasp team by creating an issue in the docs GitHub repo (https://github.com/wasp-lang/wasp) (source (https://wasp-lang.dev/docs/contributing)).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Adam, 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?Hey, thank you for your interest in contributing to our docs 🙂 You can fork the repository and submit PRs: https://github.com/wasp-lang/wasp
The deployment docs are really ready for the next iteration, I agree! I'm writing a plan and an idea on what ot talk about in the deployment docs:
- Understanding the Wasp app building blocks (Node.js, React, Database)
- Understanding the env variables
- Understanding database (migrations, connection string)
- Deployment providers
- CI/CD tips and tricks etc.
I'd love to hear your ideas here as well 🙂 What is missing? What is confusing and what can we improve / add to the existing docs?
GitHub
GitHub - wasp-lang/wasp: The fastest way to develop full-stack web ...
The fastest way to develop full-stack web apps with React & Node.js. - GitHub - wasp-lang/wasp: The fastest way to develop full-stack web apps with React & Node.js.
Hey -- hope your vacation was great!
I see you're using docusaurus, I couldn't get it to build though, just npm run build should have worked though, or?
1. I don't think deployment should be in advanced or? We all hope to deploy one day
2.
:::important Before Deploying
Before deploying, make sure to run the following command to apply any pending database migrations:
:::
3.
:::warning Note Down Database Credentials
When Fly.io creates the database for your app, it will display the DATABASE_URL, username, and password. Make sure to note these down securely, as they will only be shown once.
:::
:::important Set Server Secrets
After deploying, you must set all your server-side environment variables (secrets) using the following command:
Replace the example keys and values with your actual secrets.
:::
4. The github hook could be mentioned
5. For some reason my schema.prisma is not being updated by the github action? I've tried a mix of manual deployment and just tearing down my app, I'm still in development so nothing matters, but it's been confusing of understanding what I should do so my database migration actually migrates.
7. I would be up for a community doc about tips and tricks about fly.io + prisma migrations
I see you're using docusaurus, I couldn't get it to build though, just npm run build should have worked though, or?Yep,
npm install and then npm run start for dev
For some reason my schema.prisma is not being updated by the github action?I'm not sure I follow, what is not working for you? If you change the Prisma file and create a migration, it should be enough. The migration file should be added to Git and when the server app is deployed, it will run that migration against the production database. Unless, something failed - to check that, you look at server logs and see what is going on. For example, if a migration failed, you'll need to check the
_prisma_migrations table to see why and delete one row so Prisma can try again https://ptb.discord.com/channels/686873244791210014/1290309348270280768/1291360159733518409Hey - sorry for the late reply. This is great information, and I didn't know that - I could delete the _prisma_migrations. I assume this also isn't very wasp specific and I should read more of database migrations for Prisma correct?
If you have any other tips like these, that would be great. I think the scariest thing for me is the database migrations!
They shoudl be, they are scary :D!