Currently the file sync is being done to the container folder /usr/src/app, but the image built starts in /src and has the installed npm dependencies.

I tried to solve the issue by reassigning the WORKDIR in the Dockerfile, but apparently the image pushed to docker hub is not built from that Dockerfile

Steps to reproduce:

• Follow the common process to develop with okteto
  • Deploy movies in cloud
  • Clone movies
  • cd into movies/frontend
  • delete command: yarn start from the okteto.yml manifest
  • okteto up

You should see you are standing in /src and your file syncing is not done there.

Proposed Solution:

• Update Dockerfile so that the final image has yarn. Could be using a one stage image
  • Update dockerhub image after that
• Update manifest so that it uses the Dockerfile to build?

I get the following message when clicking the deploy link:

When we deploy this app in cloud, we show https://movies-namespace.user.dev.okteto.net/api which is not a valid endpoint of the api. We should modify this endpoint with some config or accept it in the express api in server.js. The latter would look something like this:

      app.get("/api", (req, res, next) => {
        res.json("api is up and running")
        return;
      });

Or a redirect to /api/healthz

@pchico83 The description doesn't match the image. The service rentals is not there. What should we be changing here to match, the image or the name on the description and folder?

This is the application used for the How to Develop an Application based on Microservices tutorial.

https://okteto.com/docs/tutorials/e2e

Irrespective where I run the deploy, it fails due to missing secret key.

Release "mongodb" does not exist. Installing it now.!
Error: execution error at (mongodb/templates/secrets.yaml:33:24):!
PASSWORDS ERROR: The secret "mongodb" does not contain the key "mongodb-passwords"!error executing command 'Deploy MongoDB':
exit status 1