How do I get the volume files right in django?

[proven viper]

There is a django project. The screenshots show the following settings. I created a 1 gigabyte volume and specified it as /media - which is what I actually need. But I must have configured it wrong and when I try to navigate to the image path there is an error (screenshot 3). Can you please tell me how to connect volume to django correctly?

[candid stag]

Project ID: 6a37fcf0-b45a-43ea-aec7-9aac046bdf7f

[proven viper]

6a37fcf0-b45a-43ea-aec7-9aac046bdf7f

[proven viper]

The path is correct, but the site can't get the photo

[tawny anchor]

does MEDIA_ROOT tell django where to place the uploaded files?

[proven viper]

Yes, here is a screenshot from setting.py. You can also look at the structure of all the files.

[tawny anchor]

well if you mounted the volume to /media then /media would be your media root

but you have prefixed it with the base dir

[proven viper]

MEDIA_URL = 'media/' - this, as far as I know, goes in the url address to some photo or video, so it can essentially be called whatever you want.

But MEDIA_ROOT = BASE_DIR / 'media' is the name of the folder for images itself.

[tawny anchor]

yeah so whatever BASE_DIR / 'media' evaluates to, would not be the volume mount path

if you want the media root to be the volume, you need /media set as the media root

assuming the mount point is /media

[proven viper]

So, I did as you said. Now let's see if it works.

[tawny anchor]

thats not at all what i said lol

remove BASE_DIR!! BASE_DIR is not the volume mount!!

[proven viper]

so?

[tawny anchor]

yes, you want files to be saved in the volume thats mounted at /media then that is exactly what the path needs to be, i have not touched django but that now looks correct to me

[proven viper]

For some reason it still doesn't find

Is there any way to see what's in volume right now?

[tawny anchor]

theres not

volumes is still beta after all

have you uploaded that file first?

[proven viper]

https://lyceum208.up.railway.app | I created a user for you. username: brody192 ; password: ||1111111111||

[proven viper]

Initially, after a successful launch, I go into the admin panel and want to change the avatar of one of the teachers. But after I updated the avatar, I want to go and see if it is saved and I get this error

[tawny anchor]

do you have the correct config in your urls.py?

[proven viper]

app: teacher -> urls.py

[tawny anchor]

if settings debug

what do you have debug set to

[proven viper]

False

[tawny anchor]

then those extra urlpatterns arent getting added?

[proven viper]

No, they don't.

[tawny anchor]

that could be a problem?

[proven viper]

Honestly, I have no idea.

[tawny anchor]

remove if statement?

[proven viper]

So it doesn't work when in production mode

[tawny anchor]

why would you want it to not work?

[proven viper]

This code is only needed to make static and media files in development mode correctly:

If settings.DEBUG:
    from django.conf.urls.static import static

    urlpatterns += static(
        settings.STATIC_URL, document_root=settings.STATIC_ROOT)
    urlpatterns += static(
        settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)

That is, when DEBUG=True

[tawny anchor]

but is it? what if it is needed in production

[proven viper]

There is no need for this in production

You can basically delete this bit of code

[tawny anchor]

how can you be sure though? it isn't working right now

[proven viper]

Because here there is a check If settings.DEBUG: - works only in development mode. And in production mode it is the host that loads the files

[tawny anchor]

would it hurt to try and remove that check

[proven viper]

No, it won't. Without it, everything will work just as well. But with media we need to figure out why the site can't get photos from there

[tawny anchor]

well are there any error logs in the logs?

[proven viper]

no

[tawny anchor]

just seems like django isn't setup properly to read the files back out of the media volume

[proven viper]

Maybe, but here is my whole settings.py

[tawny anchor]

media root doesn't have a forward slash prefixing it

probably not the core issue but still

[proven viper]

Should I delete the media folder I created?

[tawny anchor]

that wouldn't interfere with anything, since the volume mounts to /media relative to the root of the container

[proven viper]

Is it possible to view the contents of /media with the code. Through the same os.listdir()?

[tawny anchor]

I'm sure there is, but that would be a question for google

[proven viper]

I plugged "Volume" into the following code and this is what I got

After connecting "Volume" to the project, the variable "RAILWAY_VOLUME_MOUNT_PATH" becomes available to output the path. Maybe in django you could use it too?

[tawny anchor]

you can but it would just equal /media

[proven viper]

For some reason in this script, everything worked and brought up the available media files. But django doesn't want to get anything from it at all

[tawny anchor]

have you tried to comment out that if debug thing

[proven viper]

I deleted it completely. I created a separate branch for experiments to run

[tawny anchor]

show me the new code?

[proven viper]

https://github.com/x4zx/lyceum208/tree/test | also, invited you to the repository

[tawny anchor]

what branch are you working in

[proven viper]

As of now, the test branch

[tawny anchor]

I don't see anything in urls.py that lets django know to load files from media root

[proven viper]

You specify the path to the files in the settings. In production mode, you do not need to specify anything in urls.py

[tawny anchor]

okay well you clearly need to specify something extra somewhere, so I don't know why you are so opposed to trying what I have suggested

[proven viper]

I'm not against it, I'm just saying that it doesn't help in production.

[tawny anchor]

says who

[proven viper]

Many other developers. if settings.DEBUG: is used only during development, so that django understands where the files come from. In production, a special server for media files is responsible for this

[tawny anchor]

okay so where's this special server you speak of

[proven viper]

Well, since you have "volume", it turns out that the railway is a special server for storing media files

[tawny anchor]

that sentence does not make any sense

you need to configure django to serve the files from the volume

[proven viper]

I wish I knew how to do it.

[tawny anchor]

so far you've only shown me code that tells django where to save the file, but nothing that tells django where to access the saved files

[neat mango]

Have you tried uploading another file after changing the root to /media? Previously uploaded files wouldn’t be in the volume

[proven viper]

Yeah, but it didn't do anything. The file is still "not found". I tried to run the site locally with DEBUG=False and the error is the same, "file not found".

[proven viper]

Although there is a file in the media folder

[neat mango]

Ya but that’s your localhost, not production. Try changing MEDIA_URL to /media/, MEDIA_ROOT to /media

Brody is right, you want to tell Django how to serve files from the volume where they’re stored. Storage is different from serving

Google for:

• django serve media from path
• django media static url production

[proven viper]

Changed it, but it didn't help

[proven viper]

By the way, with this value, when I change the avatar in the profile, the folder media is created in the root of the drive

[neat mango]

That’s what you want in production. Remove the BASE_DIR