mystic
Suspicious traffic from a mystery railway app
Hello! My Sentry reported 10k errors just today that look like this:
Invalid HTTP_HOST header: 'liam.up.railway.app'. You may need to add 'liam.up.railway.app' to ALLOWED_HOSTS.
This is not a server / service owned by me. I don't know what it is. But I definitely wasn't prepared to pay for Sentry's 10k errors! I don't really know how to report this, or even what kind of problem this really is, so I posted it here. I don't know if this is a hacking attempt or scanner or an internal service or what. Is there anything I should do? I am a bit worried, to be honest.27 replies
Running Yarn in a Python build
I have a Django+Vue app. Once the Vue bit is built with Yarn, everything is handled with Whitenoise+Django. This works locally, and if I build my Vue stuff before sending it to Railway, it also works. But, I don't want to do this manually every time. I do not check my built files into source control. I would like the Build process to include running
yarn build
My understanding is that Railway is automatically determining that my project is a Python project by the root directory. It is not looking into the frontend directory to see a yarn.lock or package.json in there.
How can I resolve this? In the ideal situation, when the build is triggered with a branch change, yarn build will be run sometime before Django's runserver command. Unfortunately, just putting this as part of, say, the Procfile just gives yarn: command not found.
Some non-ideal solutions would be: Checking my files into source control. Having a separate project for the frontend. Putting dummy files into root to "trick" it into recognizing that it's got a Javascript component. However, if any of these are necessary, I can use those workarounds...
project id: 00e357e0-9d2a-45be-8a64-a58b8ee28694
(What can you see with this? Does this even help?)7 replies