Skip to content
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

Environment Settup #24

Open
AbrarChowdhury opened this issue Aug 28, 2023 · 4 comments
Open

Environment Settup #24

AbrarChowdhury opened this issue Aug 28, 2023 · 4 comments

Comments

@AbrarChowdhury
Copy link

I update the env.local with details from cloudinary. (cloudname, apikey, and API secret). I am not sure what the folder is supposed to be.

Morever, I keep getting this error:

error Error: Must supply cloud_name

@chronark
Copy link
Owner

This project is not using cloudinary

@ryanmalani
Copy link
Contributor

hey @AbrarChowdhury- I've never personally used cloudinary before (as chronark mentioned this project doesn't use that, vercel has a super easy way to deploy this quickly though; more details here) but I feel like this is helpful to keep in mind:

From Cloudinary's site though:

Tip When your account is created, a cloud_name is randomly generated for your initial product environment. Your cloud name will later be used in the URLs of media you deliver from Cloudinary, so it's a good idea to change your cloud name to a descriptive one for your organization, site or app. We'll walk you through this a little later on this page.

@Boby900
Copy link

Boby900 commented Jun 27, 2024

@AbrarChowdhury you have to use environment variables given in the upstash < redis console. I guess that is what you are asking for

@Avijit-ap
Copy link

Avijit-ap commented Aug 28, 2024

@AbrarChowdhury you have to use environment variables given in the upstash < redis console. I guess that is what you are asking for

I am new to this redis thing, could you please share what kind of setup has been made due to which project details automatic fetching?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants