How to deploy my web

[congmucc]

Hi, I have a problem that may be the path. I want to deploy my website on github page, but only the homepage can be accessed, but the style is also wrong. my page is https://congmucc.github.io/blog/, my github is https://github.com/congmucc/blog. You can look it.

I read the https://vitepress.dev/guide/deploy#setting-a-public-base-path, and change the base of vite.config.ts to /blog/, but it is fail, if it doesn't have /blog/, it is also fail. How can I get the help.

[brc-dd]

Set base in this file - https://github.com/congmucc/blog/blob/main/.vitepress/config.mts - not vite.config.ts

[congmucc]

Set base in this file - https://github.com/congmucc/blog/blob/main/.vitepress/config.mts - not vite.config.ts

thanks

[congmucc]

Set base in this file - https://github.com/congmucc/blog/blob/main/.vitepress/config.mts - not vite.config.ts

Hi, in my blog, I have another question. https://github.com/congmucc/blog is my blog github. I want to deploy on the cloudflare. but it failed during installation.

this is log

2025-03-12T01:01:01.923728Z	Cloning repository...
2025-03-12T01:01:03.892204Z	From https://github.com/congmucc/blog
2025-03-12T01:01:03.892788Z	 * branch            667ebd34d965be95afc4323a633d54908ba9ccfd -> FETCH_HEAD
2025-03-12T01:01:03.892949Z	
2025-03-12T01:01:04.27938Z	HEAD is now at 667ebd3 fix yarn.lock
2025-03-12T01:01:04.279853Z	
2025-03-12T01:01:04.36163Z	
2025-03-12T01:01:04.362321Z	Using v2 root directory strategy
2025-03-12T01:01:04.396278Z	Success: Finished cloning repository files
2025-03-12T01:01:06.053487Z	Checking for configuration in a Wrangler configuration file (BETA)
2025-03-12T01:01:06.054216Z	
2025-03-12T01:01:07.159306Z	No wrangler.toml file found. Continuing.
2025-03-12T01:01:07.225066Z	Detected the following tools from environment: yarn@3.6.3, nodejs@18.17.1
2025-03-12T01:01:07.225537Z	Installing project dependencies: yarn
2025-03-12T01:01:07.809759Z	➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker 👍
2025-03-12T01:01:07.810069Z	
2025-03-12T01:01:07.85936Z	➤ YN0000: ┌ Resolution step
2025-03-12T01:01:08.977072Z	➤ YN0061: │ glob@npm:7.2.3 is deprecated: Glob versions prior to v9 are no longer supported
2025-03-12T01:01:09.03123Z	➤ YN0061: │ inflight@npm:1.0.6 is deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
2025-03-12T01:01:09.209851Z	➤ YN0061: │ source-map-resolve@npm:0.5.3 is deprecated: See https://github.com/lydell/source-map-resolve#deprecated
2025-03-12T01:01:09.272236Z	➤ YN0061: │ resolve-url@npm:0.2.1 is deprecated: https://github.com/lydell/resolve-url#deprecated
2025-03-12T01:01:09.272961Z	➤ YN0061: │ source-map-url@npm:0.4.1 is deprecated: See https://github.com/lydell/source-map-url#deprecated
2025-03-12T01:01:09.285468Z	➤ YN0061: │ urix@npm:0.1.0 is deprecated: Please see https://github.com/lydell/urix#deprecated
2025-03-12T01:01:10.545226Z	➤ YN0032: │ fsevents@npm:2.3.3: Implicit dependencies on node-gyp are discouraged
2025-03-12T01:01:11.168698Z	➤ YN0002: │ @algolia/autocomplete-core@npm:1.17.7 doesn't provide @algolia/client-search (p371a9), requested by @algolia/autocomplete-shared
2025-03-12T01:01:11.169015Z	➤ YN0002: │ @algolia/autocomplete-core@npm:1.17.7 doesn't provide algoliasearch (pf8667), requested by @algolia/autocomplete-shared
2025-03-12T01:01:11.169209Z	➤ YN0002: │ @algolia/autocomplete-core@npm:1.17.7 doesn't provide search-insights (p75a30), requested by @algolia/autocomplete-plugin-algolia-insights
2025-03-12T01:01:11.169338Z	➤ YN0002: │ @algolia/autocomplete-plugin-algolia-insights@npm:1.17.7 [b5d26] doesn't provide @algolia/client-search (p067e3), requested by @algolia/autocomplete-shared
2025-03-12T01:01:11.169485Z	➤ YN0002: │ @algolia/autocomplete-plugin-algolia-insights@npm:1.17.7 [b5d26] doesn't provide algoliasearch (pd179e), requested by @algolia/autocomplete-shared
2025-03-12T01:01:11.169625Z	➤ YN0002: │ @docsearch/react@npm:3.8.2 [cc094] doesn't provide @algolia/client-search (pcc273), requested by @algolia/autocomplete-preset-algolia
2025-03-12T01:01:11.169757Z	➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
2025-03-12T01:01:11.173693Z	➤ YN0000: └ Completed in 3s 314ms
2025-03-12T01:01:11.20234Z	➤ YN0000: ┌ Post-resolution validation
2025-03-12T01:01:11.202906Z	➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
2025-03-12T01:01:11.203164Z	➤ YN0000: └ Completed
2025-03-12T01:01:11.203312Z	➤ YN0000: Failed with errors in 3s 345ms
2025-03-12T01:01:11.239361Z	Error: Exit with error code: 1
2025-03-12T01:01:11.239649Z	    at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
2025-03-12T01:01:11.239757Z	    at Object.onceWrapper (node:events:652:26)
2025-03-12T01:01:11.23985Z	    at ChildProcess.emit (node:events:537:28)
2025-03-12T01:01:11.239935Z	    at ChildProcess._handle.onexit (node:internal/child_process:291:12)
2025-03-12T01:01:11.247913Z	Failed: build command exited with code: 1
2025-03-12T01:01:12.297524Z	Failed: error occurred while running build command

this is other setting

my repair plan

In this log, I deleted the yarn.lock file so that Cloudflare would work. but github page not works. How can I solve it?
@brc-dd

[brc-dd]

keep the yarn.lock. tell cloudflare to use yarn v1 - https://www.emmanuelgautier.com/blog/cloudflare-page-build-yarn-version

[congmucc]

keep the yarn.lock. tell cloudflare to use yarn v1 - https://www.emmanuelgautier.com/blog/cloudflare-page-build-yarn-version

thanks, it works.

[congmucc]

keep the yarn.lock. tell cloudflare to use yarn v1 - https://www.emmanuelgautier.com/blog/cloudflare-page-build-yarn-version

This is my site https://f55375eb.blog-33o.pages.dev/, Why did its style fail? Can you help me? this is my github repository https://github.com/congmucc/blog

[brc-dd]

It's because of base in config. You don't need base when your site doesn't have. You need it for github pages in this case but not for cloudflare pages. I think you can remove it from here https://github.com/congmucc/blog/blob/b5b9b6460019e932b5dde0ecb3a9ad434bf935d3/.vitepress/config.mts#L10 and change https://github.com/congmucc/blog/blob/b5b9b6460019e932b5dde0ecb3a9ad434bf935d3/.github/workflows/deploy.yml#L49 to yarn build --base='/blog/' so that both your cloudflare pages and github pages work fine.

[congmucc]

It's because of base in config. You don't need base when your site doesn't have. You need it for github pages in this case but not for cloudflare pages. I think you can remove it from here https://github.com/congmucc/blog/blob/b5b9b6460019e932b5dde0ecb3a9ad434bf935d3/.vitepress/config.mts#L10 and change https://github.com/congmucc/blog/blob/b5b9b6460019e932b5dde0ecb3a9ad434bf935d3/.github/workflows/deploy.yml#L49 to yarn build --base='/blog/' so that both your cloudflare pages and github pages work fine.

Thank you very much for your help.