a year ago
Hi there,
Wrestled with my actual ng17 project yesterday and got it deployed but could not load my app (various errors 404 one of them). I tried various steps i seen online including adding the Caddy files, changing the src dir etc. but no joy.
The templates work fine - so thank you. But i just created a new ng17 app using 'ng n [proj-name]', built and served locally ok then tried to deploy to railway and it fails too. I tried with and without the Caddy files.
I'm probably missing something simple but can't seem to get to render any ng app i created.
Could you assist?
Thanks.
ⓘ Deployment information is only viewable by project members and Railway employees.
2 Replies
a year ago
Doesn't matter. I've migrated across my code files to your ng18 template and seem to have it working - the frontend at least. Just curious to know why a blank ng17 project didn't deploy.
Anywho, doesn't matter as i say, i'll crack on. Can close the ticket, i'm sure there'll be others ha!
a year ago
You were not using a web server - https://github.com/railwayapp-templates/angular-starter?tab=readme-ov-file#-why-use-caddy-when-deploying-to-railway
Railway, unlike vercel will not serve files for you, your own app has to do that, and that's where caddy comes into play.
Status changed to Solved brody • over 1 year ago