D
Dokploy•10mo ago
romerocode

Build app from dockerfile

Hey guys, I hope your day was great! I've been trying out Dokploy, and it's an amazing tool, congratulations and success to the developers for such a good job. I started using it with astro websites, and then I found myself in the need to publish an application in Angular. I first tried with the default Nixpacks option, uploading the static files, and it worked, but there is a bad but normal behavior, returning 404 when refreshing the website or entering from a specific url. To solve this, I decided to add a Dockerfile to my repository, which brings the nginx configuration necessary to solve the error, connect the repository with Dokploy, and from there, use the Dockerfile build type. I admit that I'm new to Docker. As I understood, this will build the image using the dockerfile, and start the container. And it asks me for 2 fields: Docker File Docker Context Path The first one I understand is the path to the dockerfile within the repository, but I don't understand what the second one is, and I haven't been able to deploy the container from the dockerfile. I'm sorry to bother you with my question, the truth is I've been trying to investigate on my own, but I haven't been able to get it to work. Thanks for reading.
No description
No description
No description
5 Replies
Siumauricio
Siumauricio•10mo ago
Hey the docker context is basically where's the entrypoint in terms of folder you want to run the application, if you are not familiar probably you will not needed it, this is more usefull for monorepos can you share the structure of your project?
romerocode
romerocodeOP•10mo ago
No description
romerocode
romerocodeOP•10mo ago
Here I share the structure of my project
Siumauricio
Siumauricio•10mo ago
in the dockerfile path just set Dockerfile
romerocode
romerocodeOP•10mo ago
Thank you so much 🙌, putting the file name worked for me, I apologize and am sorry, it was a huge mistake and lack of knowledge on my part. I was just using the "/" or "." and putting random stuff in the Docker context path, that was the mistake.

Did you find this page helpful?