N/A

I am taking about this https://github.com/smogon/pokemon-showdown/blob/master/server/README.md

Team Railway, Could you please consider adding native support for deploying Pokémon Showdown side servers? Ideally, users should be able to simply clone the repository, and the server should be up and running no additional configuration, Dockerfile, or environment tweaks required. This would greatly streamline the deployment process for a widely used open-source project.

Additional Feature Request – File Management UI

It would be extremely helpful if Railway offered a basic file management system for server-based projects.

For example, Pokémon Showdown is a Node.js-based multiplayer server that relies heavily on editable config files such as config/usergroups.csv, formats.json, and various log or plugin files. Right now, making small changes requires redeploying or using SSH and volume workarounds.

A built-in file manager that allows users to browse directories, edit files inline, upload/download assets, and restart the server as needed would make hosting and maintaining side servers much more efficient.

This feature would benefit many backend-focused projects not just Showdown and make Railway more powerful for managing dynamic, file-driven servers.

Thank you for creating a template Kishan!

For any further discussion, consider using the Template Discussion Thread for easy access in the future https://station.railway.com/templates/pokemon-showdown-d67c1f06

ok

the relevant error from the failed deploy:

Starting Container
/app/node_modules/esbuild/lib/main.js:2150
      throw reject;
      ^
Error: The service was stopped
    at /app/node_modules/esbuild/lib/main.js:969:34
…
Error: Command failed: node build
    at build (/app/pokemon-showdown:30:27)
    at Object. (/app/pokemon-showdown:143:2)
    status: 1

To fix this, please update the template as follows:

Remove the node build step entirely

at package.json

"scripts": {
  "start": "node server.js"
}

At Dockerfile:

FROM node:18-alpine
WORKDIR /app
COPY package*.json ./
RUN npm install --production
COPY . .
EXPOSE 8080  # Railway will bind $PORT automatically
CMD ["npm", "start"]

and then server.js (entrypoint):

const PORT = parseInt(process.env.PORT, 10) || 8000;
server.listen(PORT, () => console.log(`Listening on ${PORT}`));

With these changes, Railway will skip the failing build step and start the Pokemon Showdown server directly.

the template is attempting to run a build script (node build) which triggers esbuild and then crashes. Because Showdown doesn’t require a separate build step, I recommend this changes.