Here they are

50 is not good enough because you have not provided enough information in your initial message, such as do you have a path to your Dockerfile set?

I'm building from template

The template I made deploys without issues -

https://railway.app/template/to7duB

no it's not working for me, is there any issues with compute power

That is now a completely different error, Twenty does need more than 500MB of RAM at the start, please upgrade to Hobby and then redeploy the Server service.

I'm using the TwentyCRM Template and it's failing to build. I'm not sure why, but also I have been searching for over an hour now to try to find the four variables I need. I'm using Google Workspace for my email server. I have everything but the port, I have seen 465 and 587 in different places, but can't find it in the Workspace settings.

You would get the values for those variables from your Email provider.

It's Google Workspace, and they don't make it easy to find them. For no reason I can understand, it worked on the second attempt to get the template running on Railway. However, now the URL get's a failed load page. I've attached the logfile.

Can you please open your own thread for this as we are currently communicating on someone else's 9 month old thread.

It’s frustrating when a CRM project doesn’t go as planned. If you're looking to avoid common pitfalls and build a CRM system that meets your needs, I recommend checking out this article on how to create your own CRM system: https://www.cleveroad.com/blog/how-to-build-your-own-custom-crm-system/ It provides a detailed approach to ensure your CRM is designed and implemented effectively.

The issue discussed in the Railway Help Station thread regarding "Twenty CRM failed to build" points to common deployment problems often faced when setting up open-source CRM solutions. The initial failures were attributed to insufficient resources (the CRM requiring more than the default 500MB of RAM) and a lack of necessary environment variables, specifically those related to the email provider setup.

This situation highlights the fundamental challenges of deploying and maintaining a complex, custom business application like a CRM:

• Resource Management: Custom CRMs demand specific computational resources (CPU and RAM). Underestimating these needs leads to deployment failures and poor performance.

• Complex Configuration: Integrating essential services, like email for outreach and logging, requires precise setup of numerous environment variables (SMTP host, port, credentials).

• Debugging and Expertise: Troubleshooting these environment-specific build errors requires deep expertise in both the CRM's technology stack (like Twenty CRM's) and the deployment platform's infrastructure.

For a business, relying on a professional partner eliminates these time-consuming and costly deployment hurdles. Rather than spending hours debugging logs and searching for environment variables, you can ensure a reliable, optimized, and secure solution from day one.

To successfully build, customize, and deploy a robust CRM that meets your business needs without the headaches of infrastructure failures, it is essential to hire CRM developers from CMARIX Infotech who possess specialized knowledge in system architecture and deployment best practices:.

20 attempts is valuable feedback: somewhere the focus on key user scenarios is lost, or the architecture isn't scaling. I recommend starting with a minimal workflow and code/architecture review. Consult a developer with CRM experience—it will save time and money.

It sounds like the issue may be related to a missing Docker configuration or an incomplete build setup. Double-check your Dockerfile path and ensure it’s properly referenced in your project root before deployment. Sometimes, build pipelines fail if the Dockerfile isn’t detected or if environment variables are misconfigured.

Also, regarding the 150-character limit, it’s often implemented to ensure sufficient input for proper logging or identification during deployment — reducing that limit to 50 might not provide enough context.

If you’re working on a large-scale CRM or app deployment, collaborating with a Mobile App Development Company in USA like Apptechies could help streamline the build and CI/CD pipeline setup. They specialize in handling complex deployments, ensuring smooth builds, and maintaining scalable app infrastructure.

Here are the build logs, and there are no deploy logs showing any errors—the Dockerfile doesn’t exist. Also, the 150-character limit feels unnecessary; I believe 50 characters should be enough, especially for a mobile application development company workflow.