starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-26 06:15:58 +03:00

[GH-ISSUE #518] Correcting Gitpod Configuration: Updating gitpod.yml for Proper Port Exposure and Initialization Commands #133

New issue

Closed

opened 2026-02-26 18:45:30 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 18:45:30 +03:00

Owner

Originally created by @anjy7 on GitHub (Oct 3, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/518

Gitpod isn't configured properly, we need to configure the gitpod.yml file to expose the right ports and run the necessary commands to start the dev env.

Originally created by @anjy7 on GitHub (Oct 3, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/518 Gitpod isn't configured properly, we need to configure the gitpod.yml file to expose the right ports and run the necessary commands to start the dev env. ![image](https://github.com/documenso/documenso/assets/92802904/86f01517-0ec3-486f-bef3-fd22cfe59d8d)

kerem

2026-02-26 18:45:30 +03:00

closed this issue
added the
type: bug

community
labels

kerem commented

2026-02-26 18:45:31 +03:00

Author

Owner

@anjy7 commented on GitHub (Oct 3, 2023):

I'm working on this and will raise a PR soon..

@anjy7 commented on GitHub (Oct 3, 2023): I'm working on this and will raise a PR soon..

kerem commented

2026-02-26 18:45:31 +03:00

Author

Owner

@catalinpit commented on GitHub (Oct 4, 2023):

Thanks @anjy7. Looking forward to the PR.

@catalinpit commented on GitHub (Oct 4, 2023): Thanks @anjy7. Looking forward to the PR.

kerem commented

2026-02-26 18:45:31 +03:00

Author

Owner

@anjy7 commented on GitHub (Oct 5, 2023):

Hey @anikdhabal, I understand that you might be new to this community, but I would appreciate it if you go through the contributing guidelines before making a PR - reason being :

It would avoid redundant work
It wouldn't waste anyone's time

Apart from this, I went through your PR; it looks like there's some error in the DB connection. I have been trying to fix the same issue for a while now; otherwise, I would have raised the PR myself before. I hope you understand. Keeping that aside, I would be glad to work with you to solve that error :) .

@anjy7 commented on GitHub (Oct 5, 2023): Hey @anikdhabal, I understand that you might be new to this community, but I would appreciate it if you go through the contributing guidelines before making a PR - reason being : 1. It would avoid redundant work 2. It wouldn't waste anyone's time Apart from this, I went through your PR; it looks like there's some error in the DB connection. I have been trying to fix the same issue for a while now; otherwise, I would have raised the PR myself before. I hope you understand. Keeping that aside, I would be glad to work with you to solve that error :) .

kerem commented

2026-02-26 18:45:31 +03:00

Author

Owner

@anikdhabal commented on GitHub (Oct 6, 2023):

Hey @anikdhabal, I understand that you might be new to this community, but I would appreciate it if you go through the contributing guidelines before making a PR - reason being :

It would avoid redundant work

It wouldn't waste anyone's time

Apart from this, I went through your PR; it looks like there's some error in the DB connection. I have been trying to fix the same issue for a while now; otherwise, I would have raised the PR myself before. I hope you understand. Keeping that aside, I would be glad to work with you to solve that error :) .

I updated it. Now it's working without any error :).

@anikdhabal commented on GitHub (Oct 6, 2023): > Hey @anikdhabal, I understand that you might be new to this community, but I would appreciate it if you go through the contributing guidelines before making a PR - reason being : > > 1. It would avoid redundant work > 2. It wouldn't waste anyone's time > > Apart from this, I went through your PR; it looks like there's some error in the DB connection. I have been trying to fix the same issue for a while now; otherwise, I would have raised the PR myself before. I hope you understand. Keeping that aside, I would be glad to work with you to solve that error :) . I updated it. Now it's working without any error :).

kerem referenced this issue

2026-02-26 18:48:43 +03:00

[PR #133] [MERGED] Use documenso as container name for local development #740

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#133

No description provided.

Rows
Columns