The server is configured with a public base URL of /vite-dev/ - did you mean to visit....

[kingpalethe]

Hi, I have set up a new Rails 7 app using Vite. At first, it worked great, both on local dev and on Heroku, but now I'm blocked on a problem I can't figure out.

On on intermittant basis, I am getting this error when I load a page:

The server is configured with a public base URL of /vite-dev/ - did you mean to visit /vite-dev/admin/...

So, for some reason, rails wants to redirect to /vite-dev/ when I load a page.

It seems lots of other people have similar problems with VITE: https://www.google.com/search?q=The+server+is+configured+with+a+public+base+URL+of+%2Fvite-dev

I am using Docker, so I have followed this example as closely as I can: https://github.com/ElMassimo/vite_rails_docker_example

---

When I look in the logs, sure enough, I see...

vite_1  | 2023-03-06T17:03:55.477Z vite-plugin-ruby:config {
vite_1  |   base: '/vite-dev/',
vite_1  |   build: {
vite_1  |     emptyOutDir: true,
vite_1  |     sourcemap: false,
vite_1  |     assetsDir: 'assets',
vite_1  |     manifest: true,
vite_1  |     outDir: '../../public/vite-dev',
vite_1  |     rollupOptions: { input: [Object], output: [Object] }
vite_1  |   },
vite_1  |   envDir: '/usr/src/app',

So yes, my base is configured to /vite-dev/

---

Here is my vite.config.ts

export default defineConfig({
  plugins: [
   ruby(),
  ],
})

I tried adding base: '/' to this but it makes no difference

---

Here is my config/vite.json file:

{
 "all": {
   "sourceCodeDir": "app/javascript",
   "watchAdditionalPaths": []
 },
 "development": {
   "autoBuild": true,
   "publicOutputDir": "vite-dev",
   "port": 3036
 }
}

I see that the publicOutputDir here is vite-dev, but that's where vite should be "bundling" my JS, right? It should not be related to routing??

---

next, here is my docker compose file:

version: '3.9'

services:
    web:
        tty: true
        logging:
            options:
                max-size: '5k'
        build:
            context: .
            dockerfile: Dockerfile
        ports:
            - "3000:3000"
        volumes:
            - type: bind
              source: .
              target: /usr/src/app
        environment:
            VIRTUAL_HOST: REDACTED.REDACTED.com
            RAILS_SERVE_STATIC_FILES: exists
            RAILS_ENV: development
            VITE_RUBY_HOST: vite

        command: ['delete_pid.sh', 'bin/rails', 's', '-b', '0.0.0.0']
    vite:
        scale: 1
        logging:
            options:
                max-size: '5k'
        build:
            context: .
            dockerfile: Dockerfile
        volumes:
            - type: bind
              source: .
              target: /usr/src/app
        ports:
            - "3036:3036"
        environment:
            VIRTUAL_HOST: REDACTED.REDACTED.com
            DEBUG: '*vite*'
            RAILS_ENV: development
            VITE_RUBY_HOST: 0.0.0.0

        command: >
            sh -c "bin/vite dev"
volumes:
    db_data:

networks:
    default:
        external:
            name: nginx-proxy

Here is my GEMFILE

source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }

ruby '3.2.1'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '7.0.4.2'
gem 'sprockets-rails', :require => 'sprockets/railtie'
# Use sqlite3 as the database for Active Record
gem 'pg'
# Use Puma as the app server
gem 'puma', '6.1.1'


gem "vite_rails", "~> 3.0"

[uzaif313]

@kingpalethe is it happening in both env

[kingpalethe]

Gave up and went back to Shakapacker.

[charIeszhao]

Ran into the same problem and changing my base to / worked for me