firefly
Cannot have custom domains on Hobby plan?
Hey, I see that there was a recent update not allowing us to have more than one custom domain for a Hobby plan. Which is fine.
However, it doesn't even allow us to have subdomains.
I am building a small hobby Elixir project that essentially does a redirect using Redis, so domain
urly.ws/abc -> Elixir service (Railway) -> Redirects to google.com
urly.ws -> Elixir service (Railway) -> Redirects to app.urly.ws (Vercel)
app.urly.ws -> Nextjs Frontend (Vercel) <- All good here
www.urly.ws/abc <<<< CANNOT HAVE MORE THAN 1 DOMAIN
www.urly.ws <<<< CANNOT HAVE MORE THAN 1 DOMAIN
And I know this was a recent change, because I did it for a different domain few days ago (0ven.io, but I had to rename it)
47 replies
Automated Test Env generation CI/CD
Hello!
I work as a Frontend Team lead in one medium size crypto related company, and currently we have an issue with our infra being very hard to maintain, and work with. Creation of a dev environment requires a lot of heavy lifting, we user Docker images, with Docker hub, CircleCI for CI/CD, we use Nginx (even for test envs), our DevOps team has created a tool to manage deployments and some AWS configurations, however.
I want for us to move to Railway, at least for Test Envs, for our Frontend apps.
We have monorepos (pnpm workspaces), with React Typescript, with own implementation of Server-side rendering.
Currently the way how to do it I see:
in CircleCI CI/CD after docker build, incase of a feature branch: use railway CI deployment tool to deploy the app
Somehow get the env name?
In CI/CD connect to Slack, and send a message that an env has been created, with some specific url.
Envs should be unique for each feature branch, and should be possible to terminate them on-demand.
PS.
We can freely pay for this, however, I don't see much in documentation for this.
Idea is for developers to be able to test out their feature branches in isolation from each other, afterwards commit to master branch after everything has been verified by QA team.
3 replies