Which the inconvience for this case "Failed to detect supported framework"?

[cloud66-oss]

Which the inconvience for this case "Failed to detect supported framework"?

[khash]

Can you tell me what's the framework you're looking to use?

[alejandrojapkin]

There seems to be a large number of frameworks (namely, anything that's not flask or your run of the mill microservice python). What was the aim of the project? How do you run the framework detection? If you explain that without sending us to figure your code, perhaps there's a way to make it modular and fit to more purposes.

[fritzfr]

The main issue seems to be the folder strucutre of the project. That's also what is holding me back from deploying using cloud66, because their tools require the root of the repo/project to be where (in case of Node.js) package.json and so on is residing.

[bhogayatakb]

I am facing the same issue with a nodejs project.
Interesting things is : If i use linux build uploaded on
https://github.com/cloud66-oss/starter/releases/download/1.4.3/linux_amd64_1.4.3, it easily works.
But the issue takes place if I create a build from the code using docker-compose up

I did some more debugging and found that the issue is with FileExists function at common/utils.go
os.Stat is not able to recognize that "package.json" is present at particular location.
I wonder if it has to do something with the project root.

---

UPDATE : I guess I found the issue - it is just a silly mistake regarding usage
If we are running this project with docker, we should also copy the "target project" into the docker file system
for testing purpose, I copied my project inside /app/templates and it worked like wonder.

I maybe late to this discussion, but I think this is enough information to close this particular issue.