Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto generated config fails #348

Closed
max-allan-surevine opened this issue Aug 1, 2022 · 2 comments · Fixed by paketo-buildpacks/paketo-website#549
Closed

Auto generated config fails #348

max-allan-surevine opened this issue Aug 1, 2022 · 2 comments · Fixed by paketo-buildpacks/paketo-website#549

Comments

@max-allan-surevine
Copy link

If you try to auto generate the config it does not create valid config.

mkdir foo
cd foo
touch index.html
pack build httpd --builder paketobuildpacks/builder:full --env BP_WEB_SERVER=httpd

Expected Behavior

The container should create a default config that works.

Current Behavior

The container fails to run

docker run -e PORT=8080 httpd
AH00526: Syntax error on line 20 of /workspace/httpd.conf:
DocumentRoot '/workspace/public' is not a directory, or is not readable

Possible Solution

Maybe update the documentation to say your HTML files need to be in ./public

It'd also be handy to point out that you need to specify the port when running the container.

Steps to Reproduce

See above

Motivations

I was trying to get started with a very basic container.

@ryanmoran
Copy link
Member

We should certainly update the documentation to include some details about the assumptions made by the auto-generated configuration. To change the path to serve, did you see the docs for setting BP_WEB_SERVER_ROOT?

@max-allan-surevine
Copy link
Author

Exactly those docs.

Set the BP_WEB_SERVER_ROOT variable to an absolute file path or a file path relative to /workspace

So, if BP_WEB_SERVER_ROOT is unset then the root would be /workspace, not /workspace/public.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants