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

feat: add gitpod setup & change readme #157

Merged
merged 1 commit into from
Feb 29, 2024
Merged

Conversation

anikdhabal
Copy link
Contributor

@anikdhabal anikdhabal commented Feb 28, 2024

fixes #136

Add gitpod setup and write readme documentation.

Copy link

github-actions bot commented Feb 28, 2024

Thank you for following the naming conventions for pull request titles! 🙏

Copy link
Contributor

@dahal dahal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing work on this @anikdhabal, however I am running into this error. I do see you are copying .env.example before the build.

Also, how does DB and SMTP connection really work with gitpod?

CleanShot 2024-02-28 at 22 25 54

@anikdhabal
Copy link
Contributor Author

anikdhabal commented Feb 29, 2024

Hey @dahal, thanks for the review. I noticed that you haven't been updating the .env.example and .gitpod.yml files during setup. You're encountering this error because when you open our repository in Gitpod, it automatically adds certain commands and a .gitpod.yml file and starts automatically. Because as of now we don't have a .gitpod.yml file.

So, could you please update the .env example and .gitpod.yml files? After updating the .gitpod.yml file, you should see a popup to validate the commands. After clicking it, validate our commands and redirect to a different page with the updated code setup.

Also, we receive all emails in Inbucket, which is accessible on port 9000.

Copy link
Contributor

@dahal dahal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @dahal, thanks for the review. I noticed that you haven't been updating the .env.example and .gitpod.yml files during setup. You're encountering this error because when you open our repository in Gitpod, it automatically adds certain commands and a .gitpod.yml file and starts automatically.

So, could you please update the .env example and .gitpod.yml files? After updating the .gitpod.yml file, you should see a popup to validate the commands. After clicking it, validate our commands and redirect to a different page with the updated code setup.

Also, we receive all emails in Inbucket, which is accessible on port 9000.

Oh, thanks for the clarification, I didnot think of that. I initially clicked on the button which links to opencapco/opencap.co 's main and it does not have the updated .gitpod.yml 🤦‍♂️

Testing with your fork/branch worked. 🎉, this is amazing @anikdhabal , keep up the good work 👏👏👏

@dahal dahal merged commit 3f837c6 into captableinc:main Feb 29, 2024
3 of 4 checks passed
@anikdhabal
Copy link
Contributor Author

anikdhabal commented Feb 29, 2024

Hey @dahal, thanks for the review. I noticed that you haven't been updating the .env.example and .gitpod.yml files during setup. You're encountering this error because when you open our repository in Gitpod, it automatically adds certain commands and a .gitpod.yml file and starts automatically.
So, could you please update the .env example and .gitpod.yml files? After updating the .gitpod.yml file, you should see a popup to validate the commands. After clicking it, validate our commands and redirect to a different page with the updated code setup.
Also, we receive all emails in Inbucket, which is accessible on port 9000.

Oh, thanks for the clarification, I didnot think of that. I initially clicked on the button which links to opencapco/opencap.co 's main and it does not have the updated .gitpod.yml 🤦‍♂️

Testing with your fork/branch worked. 🎉, this is amazing @anikdhabal , keep up the good work 👏👏👏

Thank you🙏. I will do best from my side.

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

Successfully merging this pull request may close these issues.

Setup gitpod and write a readme documentation
2 participants