saashqdev / saashq

Saas CRM/ERP Starter Kit for Nextjs Prisma and Postgres. An excellent resource for buildnig things in Nextjs.
MIT License
144 stars 37 forks source link

ENV Variables #6

Open dbhurley opened 10 months ago

dbhurley commented 10 months ago
echo "" > .env.local # Clear the .env.local file
          echo DATABASE_URL: ${{ secrets.DATABASE_URL }} >> .env
          echo GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} >> .env.local
          echo GOOGLE_ID: ${{ secrets.GOOGLE_ID }} >> .env.local
          echo GOOGLE_SECRET: ${{ secrets.GOOGLE_SECRET }} >> .env.local
          echo RESEND_API_KEY: ${{ secrets.RESEND_API_KEY }} >> .env.local
          echo DO_ENDPOINT: ${{ secrets.DO_ENDPOINT }} >> .env.local
          echo DO_REGION: ${{ secrets.DO_REGION }} >> .env.local
          echo DO_ACCESS_KEY_ID: ${{ secrets.DO_ACCESS_KEY_ID }} >> .env.local
          echo DO_ACCESS_KEY_SECRET: ${{ secrets.DO_ACCESS_KEY_SECRET }} >> .env.local
          echo DATABASE_URL: ${{ secrets.DATABASE_URL }} >> .env.local
          echo JWT_SECRET: ${{ secrets.JWT_SECRET }} >> .env.local
          echo NEXTAUTH_URL: ${{ secrets.NEXTAUTH_URL }} >> .env.local
          echo NEXT_PUBLIC_APP_NAME: ${{ secrets.NEXT_PUBLIC_APP_NAME }} >> .env.local
          echo NEXT_PUBLIC_APP_V: ${{ secrets.NEXT_PUBLIC_APP_V }} >> .env.local
          echo NEXT_PUBLIC_APP_URL: ${{ secrets.NEXT_PUBLIC_APP_URL }} >> .env.local

Should list all required env variables in the Readme. Should also clarify how to define all these.

Finally, feels like all the DO vars should not be required for Vercel deployment. Nor the Google or Github ones.

The .env.example should maintain all required env variables necessary to successfully run.

saashqdev commented 10 months ago

Thanks for reporting this - I'll take a look at it.

brunomilani commented 2 days ago

I'm getting to know the project and I was able to run it normally here, thank you very much - The only question I have is why even locally, the environment seems heavy, slow to load the pages? I saw that it is also a natural behavior of the original NextCRM code. Have you discovered the reason?

saashqdev commented 2 days ago

Yep, it's a known problem. I've seen everything from clearing the browser cache to changing browsers and everything in between - https://github.com/vercel/next.js/issues/48748#issuecomment-1578374105 Way too much voodoo...

I'm seriously considering building another system based on a different tech stack. Simply, Tailwind/Nodejs/React.