Closed Cide999 closed 1 year ago
🫣
It's under @spacebarchat/spacebar-api-types
now
It's under
@spacebarchat/spacebar-api-types
now
Can you please let me know when the link will be fixed or how to fix it? I am still getting an error while setting up docker. Thank you. XD
It's under
@spacebarchat/spacebar-api-types
nowCan you please let me know when the link will be fixed or how to fix it? I am still getting an error while setting up docker. Thank you. XD
I forgot about this, are you cloning the repo and building the docker image or just pulling from docker hub?
You should not be getting this error, it was fixed a while ago in the client repo, and its suppose to pull the latest version
It's under
@spacebarchat/spacebar-api-types
nowCan you please let me know when the link will be fixed or how to fix it? I am still getting an error while setting up docker. Thank you. XD
I forgot about this, are you cloning the repo and building the docker image or just pulling from docker hub?
You should not be getting this error, it was fixed a while ago in the client repo, and its suppose to pull the latest version
I cloned the entire code from GitHub, then I wrote an environment variable file in the spacebar-server-client-proxy directory, and finally executed this command: docker-compose --env-file=.env -f docker-compose.prod.yaml up -d Pulling images definitely comes from Docker Hub, so the question is whether the issue lies with the images on Docker Hub? Are you suggesting that we need to manually create a Docker image in order to avoid this error?
It's under
@spacebarchat/spacebar-api-types
nowCan you please let me know when the link will be fixed or how to fix it? I am still getting an error while setting up docker. Thank you. XD
I forgot about this, are you cloning the repo and building the docker image or just pulling from docker hub? You should not be getting this error, it was fixed a while ago in the client repo, and its suppose to pull the latest version
I cloned the entire code from GitHub, then I wrote an environment variable file in the spacebar-server-client-proxy directory, and finally executed this command: docker-compose --env-file=.env -f docker-compose.prod.yaml up -d Pulling images definitely comes from Docker Hub, so the question is whether the issue lies with the images on Docker Hub? Are you suggesting that we need to manually create a Docker image in order to avoid this error?
yes, I was asking if you were building the image or pulling it. I am assuming that the image on docker hub is outdated
I did change something though and it triggered a rebuild, but it seems stuck waiting
I did change something though and it triggered a rebuild, but it seems stuck waiting
I gradually understand what you mean. This error occurred during the build process. In the Docker Compose configuration file on GitHub, spacebar, nginx, and spacebar-client are all built, while only the db database is pulled. I have tried deleting all containers, images, and volumes related to spacebar, then pulling this code from GitHub again and rebuilding it. However, the same error still occurs in the end. Maybe I should consider reinstalling the operating system.XD
I did change something though and it triggered a rebuild, but it seems stuck waiting
I gradually understand what you mean. This error occurred during the build process. In the Docker Compose configuration file on GitHub, spacebar, nginx, and spacebar-client are all built, while only the db database is pulled. I have tried deleting all containers, images, and volumes related to spacebar, then pulling this code from GitHub again and rebuilding it. However, the same error still occurs in the end. Maybe I should consider reinstalling the operating system.XD
just running docker compose will still pull from docker hub. you have to actually build the image first
new build has been pushed to docker hub
I did change something though and it triggered a rebuild, but it seems stuck waiting
I gradually understand what you mean. This error occurred during the build process. In the Docker Compose configuration file on GitHub, spacebar, nginx, and spacebar-client are all built, while only the db database is pulled. I have tried deleting all containers, images, and volumes related to spacebar, then pulling this code from GitHub again and rebuilding it. However, the same error still occurs in the end. Maybe I should consider reinstalling the operating system.XD
just running docker compose will still pull from docker hub. you have to actually build the image first
I know what's causing this bug. The issue lies in the Dockerfile-frontend at https://github.com/Casraw/spacebarchat-client.git. In this project, all the links related to spacebarchat are written as @puyodead1/fosscord-api-types. If you know @Casraw , please inform him to make the necessary changes. Thank you! XD
I did change something though and it triggered a rebuild, but it seems stuck waiting
I gradually understand what you mean. This error occurred during the build process. In the Docker Compose configuration file on GitHub, spacebar, nginx, and spacebar-client are all built, while only the db database is pulled. I have tried deleting all containers, images, and volumes related to spacebar, then pulling this code from GitHub again and rebuilding it. However, the same error still occurs in the end. Maybe I should consider reinstalling the operating system.XD
just running docker compose will still pull from docker hub. you have to actually build the image first
I know what's causing this bug. The issue lies in the Dockerfile-frontend at https://github.com/Casraw/spacebarchat-client.git.
In this project, all the links related to spacebarchat are written as @puyodead1/fosscord-api-types.
If you know @Casraw , please inform him to make the necessary changes.
Thank you! XD
Where is that from though?
I did change something though and it triggered a rebuild, but it seems stuck waiting
I gradually understand what you mean. This error occurred during the build process. In the Docker Compose configuration file on GitHub, spacebar, nginx, and spacebar-client are all built, while only the db database is pulled. I have tried deleting all containers, images, and volumes related to spacebar, then pulling this code from GitHub again and rebuilding it. However, the same error still occurs in the end. Maybe I should consider reinstalling the operating system.XD
just running docker compose will still pull from docker hub. you have to actually build the image first
I know what's causing this bug. The issue lies in the Dockerfile-frontend at https://github.com/Casraw/spacebarchat-client.git. In this project, all the links related to spacebarchat are written as @puyodead1/fosscord-api-types. If you know @Casraw , please inform him to make the necessary changes. Thank you! XD
Where is that from though?
I did change something though and it triggered a rebuild, but it seems stuck waiting
I gradually understand what you mean. This error occurred during the build process. In the Docker Compose configuration file on GitHub, spacebar, nginx, and spacebar-client are all built, while only the db database is pulled. I have tried deleting all containers, images, and volumes related to spacebar, then pulling this code from GitHub again and rebuilding it. However, the same error still occurs in the end. Maybe I should consider reinstalling the operating system.XD
just running docker compose will still pull from docker hub. you have to actually build the image first
I know what's causing this bug. The issue lies in the Dockerfile-frontend at https://github.com/Casraw/spacebarchat-client.git. In this project, all the links related to spacebarchat are written as @puyodead1/fosscord-api-types. If you know @Casraw , please inform him to make the necessary changes. Thank you! XD
Where is that from though?
wtf, ok I didnt know that. I have no clue why thats setup that way either
alr, I fixed it. it uses the official repo now. new docker built puhsed
I'm sorry, but I've found another new bug. XD It seems that the official project does not have a .env file.
I'm sorry, but I've found another new bug. XD It seems that the official project does not have a .env file.
AAA, ok I pushed another fix that should work. the docker container should be updated shortly
I'm sorry, but I've found another new bug. XD It seems that the official project does not have a .env file.
AAA, ok I pushed another fix that should work. the docker container should be updated shortly
It works. Thank you!
👍🏻
Maybe someone deleted this project.