b5e8cf1d-aabc-407e-b35e-00c7b95d79c2

railway run runs the given command locally, there is no native way to run commands on the deployment.

if you want to check the files then check what files you have in your GitHub repo.

but please also describe the issue you are facing

ah that makes sense

my issue is that im getting this error ReferenceError: CUSTOM_VARIABLES is not defined

which is a common issue when trying to use .env in a local plugin in Strapi:
https://forum.strapi.io/t/use-env-in-local-plugin/992/7

this apparently should fix it but im not sure how to do it in my situation.. here's my github files lis:

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        31-03-2024     17:43                .strapi
d-----        01-04-2024     20:44                admin
d-----        31-03-2024     17:43                database
d-----        31-03-2024     17:33                extensions
d-----        31-03-2024     17:33                public
d-----        31-03-2024     22:12                src
d-----        31-03-2024     17:43                types
-a----        23-01-2024     16:13            249 .editorconfig
-a----        23-01-2024     16:13             32 .eslintignore
-a----        23-01-2024     16:13            541 .eslintrc
-a----        23-01-2024     16:13           1157 .gitignore
-a----        01-04-2024     20:56             58 .strapi-updater.json
-a----        24-01-2024     00:05           3621 favicon.png
-a----        01-04-2024     16:42         721780 package-lock.json
-a----        01-04-2024     16:42           1278 package.json
-a----        30-01-2024     17:42           1867 README.md
-a----        01-04-2024     16:42         443254 yarn.lock

you are experiencing this issue locally right? since .env files do not come into play when on railway

doesn't work locally and on production (same error message)

hmm in that case is there a way to retrieve the env variables on the server?

look at the service variables

they work just fine

i think this might jsut be a strapi issue

no this wouldn't be a strapi nor railway issue, this would be due to some misconfigurations of your project

i might have an idea then

they said i should create a admin.config.js in the root of my project folder

yep you definitely have some kind of misconfigurations going on

think they meant inside the src folder then

take a look at railway's strapi template for the correct folder structure

alright

checking now

lmao

im so blind

so it should be inside the src folder

ok will try to deploy the changes now

well now i get an error saying webpack.DefinePlugin is not a constructor

i debugged the webpack object to check if DefinePlugin exists in it

1224453320425603082

and now i see that everything is inside webpack.default

would it be worth it to just deploy the strapi template and use that? it seems like you may have a few issues going on?

the probject is created from the strapi template x)

but nah all good now

this is the only issue i was facing

i don't get the errors anymore

// this throws error saying webpack.DefinePlugin is not a constructor
new webpack.DefinePlugin(...

// this works
new webpack.default.DefinePlugin(...

thanks for the help!

happy to hear that