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

Hexo Blog shows Error on Configuration #2

Closed
adamzvolanek opened this issue Aug 1, 2022 · 4 comments
Closed

Hexo Blog shows Error on Configuration #2

adamzvolanek opened this issue Aug 1, 2022 · 4 comments

Comments

@adamzvolanek
Copy link

The Hexo contain I am using is setup with the following container paths and variables:
image

Upon launching to port 8080 I am greeted with a Cannot GET / message in my browser.

I tried searching a few articles citing to add a '/' to the path in index_generator to no avail.

# Home page setting
# path: Root path for your blogs index page. (default = '')
# per_page: Posts displayed per page. (0 = disable pagination)
# order_by: Posts order. (Order by date descending by default)
index_generator:
  path: ''
  per_page: 10
  order_by: -date

Issuing a hexo init seems to work find spitting out a INFO status of:

Start blogging with Hexo!

However port 8080 page status reads the same as above and docker directory remains empty:
image

Hoping to get some guidance or at least attention to the Unraid docker being provided.

@PlanetDyna
Copy link

PlanetDyna commented Nov 13, 2022

I have the same error and would appreciate a solution.

`Starting hexo server on port 8080
INFO Validating config
WARN Deprecated config detected: "external_link" with a Boolean value is deprecated. See https://hexo.io/docs/configuration for more details.
INFO Deleted database.
FATAL {
err: [Error: ENOTDIR: not a directory, rmdir '/blog/public/'] {

errno: -20,
code: 'ENOTDIR',
syscall: 'rmdir',
path: '/blog/public/'`

@fletchto99
Copy link
Owner

Sorry I missed this issue being opened. I'll take a look sometime this coming week and see if I can replicate the issue & get it fixed.

@fletchto99
Copy link
Owner

Actually I spent soem time on this tonight. This should be fixed @PlanetDyna @adamzvolanek

If you have an existing blog it will require some work to migrate as I've updated the container to use the latest hexo version. Essentially you'll need to point the /config volume to a new EMPTY directory and let it init the blog. Once it's done, you can stop the container and then copy over your old configs. I tired to find a better solution but I don't really actively maintain this container anymore so this was the best I could do with the time I had.

I also added this warning to the logs so hopefully its not a shocker to anyone.

@PlanetDyna
Copy link

Glad to see. Its working! Thank you very much for your help and time!

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

No branches or pull requests

3 participants