b799250d-dd7b-47bb-be65-0ae878afd304

quick question, if they are temp files, why would they need to be stored in a volume?

we decided do not process files immediately, since what we are doing takes a time, but add them to a queue. Also, if we keep the orifinal file, it helps us to repeat/restart our operation in case something failed

gotcha

what is your current volume's mount point

/app/files

dockerfile or nixpacks deployment?

nixpacks I guess. I added it via control panel

Do you have a Dockerfile in your repo?

NO

what is your current path you are saving files into in code

the current path is the temp folder (I cannot make volumes work and restored temp)

please inform me of the full file path currently in use by your code that saves the temp files

"/tmp/1716569487905/CVENCedricLionelEscher_28091981.pdf"
"/tmp/1716569599042/Ivan Gerasymchuk CV2.pdf"
"/tmp/1716569599042/KARPOLAN's Resume.pdf"

they are already deleted

but you have mounted the volume to /app/tmp

the path above is
fs.mkdirSync(path.join(os.tmpdir(), String(new Date().getTime())), { recursive: true })

when I replace it to /app/files - it did not wotk

I can change the path right now and redeploy, just do not know what path shall I use

You need to mount the volume to the same path you save the files to

you also have now given me 3 different mount points for your volume makeing increasingly hard for me to help you

sorry, I do not understand. I have tried different paths.
tell me please what Mount Path shall I define and then what path shall I use to copy files

Using the Volume
The volume mount point you specify will be available in your service as a directory to which you can read/write. If you mount a volume to /foobar, your application will be able to access it at the absolute path /foobar.
^^^^^^ tried to write to such a folder - did not work

Relative Paths
Nixpacks, the default buildpack used by Railway, puts your application files in an /app folder at the root of the container. If your application writes to a directory at a relative path, and you need to persist that data on the volume, your mount path should include the app path.

For example, if your application writes data to ./data, you should mount the volume to /app/data.

^^^^^^ tried to write to such a folder - did not work either

what do you mean by "such a folder"

in the documentation you have two examples:
/foobar
/app/data

I have tried
/files
/app/files

mount volume to /app/files and save files to /app/files

ok. I am deploying. will try in a few minutes

okay, it seems working now. removing all logging and will try one more time…

sounds good

I think that my mistake was that I had to create the folder /app/files
honestly, I was thinking that railway will do it

if you mount a volume to /app/files an /app/files folder will exist within your container

well, it did not..
I even tries to list files/folders in the code and the folder did not exist

const walk = async (dirPath) =>
    Promise.all(
        await readdir(dirPath, { withFileTypes: true }).then((entries) =>
            entries.map((entry) => {
                const childPath = join(dirPath, entry.name)
                return entry.isDirectory() ? walk(childPath) : childPath
            })
        )
    )

const files = async (req, res, next) => {
    try {
        const result = await walk('/app/files') // '/app'
        res.status(200).json(result)
    } catch (error) {
        console.log(error)
        next(error)

    }
}

I'm sorry but that means you have misconfigured something, if a folder path was not created when mounting a volume that would break everyone's application who use volumes

/app/files would of course be empty though

okay. I am not so experienced with raylway as you are 😉 so I will agree with you.