environment vaiables

[MFJoyBoy]

when deploying on server it is recommended to export environment variables in order to have server properly working, in the link below:
https://github.com/leptos-rs/start-axum?tab=readme-ov-file#executing-a-server-on-a-remote-machine-without-the-toolchain
how about adding variables to .env file and ship it to server? instead of adding variables directly to shell

[gbj]

Have you tried it? Does it work?

[MFJoyBoy]

i tried, but it didn't work

[MFJoyBoy]

my bad, .env is actually working
the problem was directory structure

[MFJoyBoy]

when i use
cargo leptos build --release
the target directory is like this:

target/
├── front
│   ├── CACHEDIR.TAG
│   ├── wasm32-unknown-unknown
│   └── wasm-release
├── release
│   ├── build
│   ├── deps
│   ├── examples
│   └── incremental
├── site
│   ├── (files in public directory)
│   └── pkg
└── tmp
    └── tailwind.css

[MFJoyBoy]

there is some differences of what is describes on below link:
https://github.com/leptos-rs/start-axum?tab=readme-ov-file#executing-a-server-on-a-remote-machine-without-the-toolchain

[MFJoyBoy]

on the server, i put files as:
/var/www/{project_name}/
├── server
│ ├── build
│ ├── deps
│ ├── examples
│ └── incremental
├── site
│ ├── (files in public directory)
│ └── pkg

[MFJoyBoy]

is export environment variables as suggested and run the binary as:
./server/binary
when i go to public address of website, in the client i get the index page, but it can not load other files (public files and wasm) and i get 404 error in browser

[MFJoyBoy]

so site directory should be in the same level of server binary

[MFJoyBoy]

Copy these files to your remote server. The directory structure should be:

{{project-name}}
site/

change to:

Copy these files to your remote server. The directory structure should be:

{{project-name}}
server_binary
site/

might help to avoid misunderstanding (idk maybe it's just me 🤔 ) at the end of this page:
https://github.com/leptos-rs/start-axum?tab=readme-ov-file#executing-a-server-on-a-remote-machine-without-the-toolchain